← prev | next →     Top-level ToC     /faq.html     (printable version)

“Why write another documentation processing program?”

See the rationale page.

“Why use Markdown? Why not LaTeX, reST, moinmoin wiki syntax, etc?”

The main focus of Rippledoc is to be a very easy way to create your docs and make them available, no manual required. From “zero” to “docs” in no time flat. Markdown is, IMO, the easiest of the markup formats to write, to read, and to remember; and pandoc-markdown tastefully adds what’s missing from original Markdown.

“But my favorite language uses {fave markup}!”

Documentation often benefits greatly when others also contribute to it. Good writers may not know your markup format of choice, and may not be interested in taking the time to learn it. But they very likely already know Markdown (or can learn it in 5 minutes).

“But Rippledoc is written in Clojure! My project uses {other-language}!”

Rippledoc is a fairly simple program which happens to be written in Clojure but which could easily be rewritten in any number of other languages.

Under the hood, Rippledoc uses Pandoc to do the heavy lifting. Although Pandoc can translate between various markup formats, Rippledoc is only using it to convert Markdown to HTML. There are many other Markdown implementations that you could use if you wanted to (a bunch are listed at the Markdown wiki and the Markdown Wikipedia page), though they might not have the nice enhancements that Pandoc provides.

“Why use Pandoc under the hood? Why not {my-favorite-markdown-implementation}?”

Because Pandoc:

• supports tables, definition lists, line blocks, footnotes, and $$\LaTeX$$ math
• supports syntax highlighting
• is high-quality and reliable
• is actively maintained
• supports the command-line options that Rippledoc requires
• runs fast
• is easy to install on GNU/Linux

“Bah, I use github; why not just let users read the docs there, since github automatically renders .md files as html?”

Mainly because:

• Pandoc supports a number of very useful extensions which github’s markdown processor does not (see previous FAQ item).
But of course. :)