
: Re: Is Markdown a viable source format for writing ebooks? I've for some time enjoyed using Markdown to handle straightforward text formatting, image presentation and the like, which I use for keeping
Markdown is an excellent shortcut to HTML, especially for non-technical writers and editors. Some publishing services (Leanpub, Gitbook, PenFlip and others) make the most of this.
The drawback with most markdown-based publishing services currently is that they use flavours of markdown that don't support classes (technically, 'attribute definitions' for elements). That is, you can't use classes to distinguish, say, an epigraph from a dedication, or a normal blockquote from a 'box' blockquote. Without classes, you cannot reproduce the typography required for high-quality books more complex than a novel.
For attribute support, the best flavour of markdown to use is probably kramdown. Jekyll, and therefore GitHub Pages, support kramdown by default.
I use Jekyll to create book-ready HTML from markdown for clients, using this workflow we developed for our own book-production work. Used with Sigil for ebook assembly and PrinceXML for PDF output, we're producing book interiors as good as anything we get from InDesign.
Free books android app tbrJar TBR JAR Read Free books online gutenberg
More posts by @Nancy

: Why publish technical books only in hardback form and not in ebook form? Why would a publisher delay publishing a new book in ebook form? E.g.: http://www.cambridge.org/us/academic/subjects/physics/electronics-physicists/art-elect