This is too biased for me IMHO. I do agree with some points, documentation IS amazing, and you are very likely under-documenting things. But documentation is not cheap to create, and specially it's not cheap to maintain. I've worked in multiple companies where the problem was too much documentation, and of course everyone was afraid to update or ghasps remove any piece of old documentation in case it... - Source: Hacker News / 12 months ago

Https://github.com/slatedocs/slate this ! Big company use it ( stripe etc ). Source: over 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