doctave VS earmark

(For an example of a site generated by the open source Doctave docs site generator, you can take a look at its own docs.)

Doctave Documentation (self-hosted, obviously) Broken links docs Math notation docs

Secondly, you have to think about search. If you use a documentation site generator to turn your Markdown docs into HTML sites, even if the toolchain builds a search index for the site, you will end up with N disconnected sites for N projects. Doctave.com can help with this if you are using our open source documentation site generator.

Finally, do try out Doctave 0.2.0! If you're looking for a batteries-included documentation generator that doesn't require plugins, doesn't pollute your repository with loads of files, and doesn't need a specialized environment to run, Doctave may be a good choice for you. It also comes with Mermaid JS diagram support and dark mode!

Reuse code from our open source documentation generator CLI that is built in Rust

I'm not sure specifically what you're looking for but perhaps consider this: https://github.com/Doctave/doctave The main site: https://www.doctave.com/

We have a backlog of features and tweaks we are working on for Doctave. I’d love to hear your feedback, so if you give Doctave a spin, let me know what you think! You can reach out to me directly on Twitter or open an issue on GitHub.

It turned out that making the most popular Elixir Markdown processor, Earmark (originally written by Dave Thomas) and pulldown-cmark, a Rust Markdown processor, produce the same output was going to be difficult. We also required some customization that was not available in both libraries.

Even if at some point I’ll add proper WYSIWYG, Keila will definitely keep supporting Markdown. I personally find it super convenient and you get a very nice plain-text version for free. Keila uses an Elixir lib, Earmark for Markdown processing and that means we are supporting GitHub-style markdown.