Slate API Docs Generator VS pandoc

Https://github.com/slatedocs/slate this ! Big company use it ( stripe etc ). Source: about 1 year ago

The second most common question being "What framework does Stripe use to build their documentation?" and the answer has unfortunately always been "They use a custom setup they built themselves and isn't available." － so then Slate gets brought up as a suitable replacement. Source: about 2 years ago

DocuAPI is a multilingual API documentation theme for Hugo created and maintained by Bjørn Erik Pedersen, the lead maintainer and co-creator of Hugo itself. It’s built on top of the Slate API docs generator, which itself was inspired by Stripe’s and PayPal’s API docs. The JavaScript section of DocuAPI has been rewritten from Jquery to AlpineJS.​​​​​​. - Source: dev.to / about 2 years ago

I've used Slate to document APIs which similarly will produce a local website. You can host that privately or there's built in support to push to github pages if you're hosting it in a github repo. The documentation itself is all written in markdown and managed separate from your API code. Source: about 2 years ago

We used to use Slate - https://github.com/slatedocs/slate for our APIs in my previous job. That was pretty neat. - Source: Hacker News / over 2 years ago

If you really want to stop using Markdown to write with, then the best solution will be to use a proper conversion tool to turn these into word processing documents, such as DOCX or ODT, and then import that into Scrivener. I don't think (without plugins anyway) that Obsidian has any way of making this easier, but a good general purpose tool for this is Pandoc. Source: about 2 years ago