Quote:
Originally Posted by phillipgessert
What's the workflow here? Someone is prepping files for you? Because the best tool for that might be something different than e.g. some standalone software you'd like to recommend to someone building an ebook end-to-end with no coding experience.
Someone operating totally independently will almost certainly wind up using something in the Vellum / Atticus / Kindle Create slate of tools, regardless of what more ebook-savvy folks may think of the output. Someone helping you create something more bespoke will probably be better served stopping short of an actual EPUB, instead focusing on giving you an exceptionally clean and well-structured Word file that you hike over the finish line yourself. And in that scenario they’re developing a more transferable skill, which is a decent carrot in lieu of pay.
|
No matter how good or not the code is, Kindle Create is crap and needs to go away forever. It has a major flaw. It outputs Mobi. And you could lose features use want to use because Mobi doesn't support them.
Vellum also needs to go away forever because it creates the some of the worst code ever. Sure it's valid, but if you need to make changes to the ePub, it's may not be easy especially if the person doing the changes is not knowledgeable enough in HTML/CSS.
I'm guessing Atticus could also be bad given it's lumped in with to other awful programs.
The best solution is to make sure you create the Word Document properly using styles and only styles. Never highlight and click a button on the toolbar.