5 ms·
I wrote a short book recently [1] and went through a similar process. Started writing using Markdown & Pandoc but soon realized that Markdown isn't a very good
by antrix 12y ago
I wrote a short book recently [1] and went through a similar process. Started writing using Markdown & Pandoc but soon realized that Markdown isn't a very good fit for longer technical documents. As an example, support for asides aka admonition blocks is nonexistent. I switched to Asciidoc + Asciidoctor and the process was much more productive.
[1] Python for the busy Java Developer. http://antrix.net/py4java http://antrix.net/py4java
- sysk 12y agoHave you tried Gitbook? (https://www.gitbook.io/ https://www.gitbook.io/ https://news.ycombinator.com/item?id=7524956 https://news.ycombinator.com/item?id=7524956)
- steveklabnik 12y ago20% per transaction is just too much.
- antrix 12y agoIf I understand correctly, the gitbook toolchain isn't freely available. Nor does gitbook address any of the limitations of Markdown that prompted me to switch to Asciidoc.