slate

There is a project called Slate that is inspired by this and is able to generate similar API docs from Markdown. It’s written in Ruby. https://github.com/slatedocs/slate

You might want to look at https://github.com/slatedocs/slate - there is also a Node.js port https://github.com/mermade/reslate and tools (see the slate wiki) to convert from formats such as OpenAPI

I'm planning on migrating all our Postman documentation away to https://github.com/slatedocs/slate if that's what you mean. PS. The reason why we're moving away from Postman is due to some tiny issue[1] that has caused lots of "you need to click here to see everthing" conversations. [1] : https://github.com/postmanlabs/postman-app-support/issues/57...

Here’s a framework that helps generate documentation similar to Stripe’s: https://github.com/slatedocs/slate

It seems it's made with slate -> https://github.com/lord/slate

Three recommendations. For general static website needs, just use Hugo https://gohugo.io/ For API documentation I recommend Slate. Nice three column layout which allows you to include code/curl examples for multiple languages with tabs in column three. Works great, can be dockerized easily. https://github.com/lord/slate Finally, for general user guide documentation, I like legacy Gitbook. Super simple and trivially produces a nice web based ebook from Markdown files. Don't let the deprecated warning put you off, it works just fine and the code is not going anywhere. https://github.com/GitbookIO/gitbook Between the three of them you can have a simple nicely formatted static doc site up very quickly.

Surprised nobody mentioned Slate yet: (probably) not as powerful, but free, open source, self-hosted and fully within your control. https://github.com/lord/slate What would be the main differentiator of DeveloperHub vs something like Slate or Hugo? I can't figure it out from the DH website copy.

It's Slate https://github.com/lord/slate, which could use some updated docs, but it looks good

Our company had this question raised recently. We've spent a day to gather our thoughts on existing documentation products and at the end of the day came up with a decision. We decided to use Slate (https://github.com/lord/slate). It's statically generated from markdown and can be deployed as a GitHub page. Though we placed it on our own NodeJS server as we needed some security around it.

Looks useful. Did you make the API documentation on your own? I used github.com/lord/slate to make a documentation page out of a swagger.yaml file for http://www.coinbots.io. I'm curious how many other coin-related APIs are out there.

I'm writing documentation for a public (REST) API and wonder which layout is preferred by developers. For example, Stripe uses a three-column layout: a navigation pane, a column to describe the API, a column with examples and error codes (see [1]). In contrast, Mailgun uses two columns: a navigation pane and a colum including the API description and examples (see [2]). Both layouts seem popular, and I'd like to better understand what's making you prefer one over the other. I'm talking about reference documentation, assuming there's also a separate user guide. Personally, I find the three column layout harder to read: the example pane often wastes a lot of space and squeezes the actual documentation in the middle. On the other hand, I see more and more sites (and tools [3]) using that layout, so that's probably just me? Thanks for your tho