6 ms·

Thanks for all your hard work. But why did you choose Asciido and asccidoctor? I think Markdown together with Pandoc is capable of generatring all kinds of for

• 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 ago
    Have 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 ago
      20% per transaction is just too much.
    • antrix 12y ago
      If 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.
• kevin_thibedeau 12y ago
  Pandoc is a powerful tool but it has some serious limitations. Nothing more sophisticated than it's own flavor of Markdown is supported. "Simple" things like internal references to anything other than headings are impossible. I had to abandon it after realizing how restricted its ReST parser is compared to the official Docutils.