What do you use for customer-facing documentation in your startup?
I'm curious how early stage founders tend to handle publishing documentation for their users. Do you use hosted solutions (GitBook, Readme, etc), use a static site generator (Jekyll, Hugo, MkDocs, etc.), or even just roll your own setup from scratch?
(Full disclosure, I'm working on a documentation platform, Doctave, but it's currently focused on a technical writer audience. I'm curious how early stage founders are solving this problem.)
I actually built a documentation tool (Engine.so) for exactly this niche.
It lets you convert Notion pages into a fully-featured documentation site for your customers.
I use it for all my ventures, since it makes writing and organization easy within Notion. It might be a good alternative for those teams and hackers that already use Notion a lot and want to keep documentation close.
I use the
high_voltagegem for static pages inside Rails. Lets me have everything inside the same app, so it’s easy to share styling/layout, as well as customize things to whatever I want (e.g. customized info on help pages for logged-in users).Excellent choice! If I were a Rails dev, I would use something like this.
I use Docusaurus, a static site generator mainly for docs. Here's how it looks: Fugu Docs.
Kalyanmatka.center world fastest matka site on google. We Provides best satta matka game and fastest matka result. visit>> https://kalyanmatka.center/
retype.com
I would never use a 3rd-party platform unless it’s open source. Docs are too important.
We use tawk.to which is free and bundles many things together.
Making it ourselves is a waste of resources when we can just pay a stipend (or get it for free).
I wouldn’t purchase just a documentation tool because we’d then need to purchase a customer service tool separately.
Why not bundle them together and save time and costs.