Guides
The decisions behind DocuGate: what we built, why, and what we would do differently.
- Caching markdown from GitHub per commit, not per minute
How DocuGate caches documentation read from GitHub under the commit SHA it came from, why private repositories are never cached, and what that still costs.
- Developers, partners and operations from one repository
How we set up documentation for three audiences from one repository in DocuGate's logistics setup, with a different access rule for each.
- Shipping a docs site without a sidebar config file
How DocuGate builds navigation from the folders, headings and index files already in a repository, and the one optional file for what folders cannot say.
- Why the access check lives on the server, and GitHub is the gate
How DocuGate decides who may read a docs space, why that decision never runs in the browser, and why GitHub answers it for repository access.
- Why we price gated docs by reader, not by space
The value metric behind DocuGate's pricing, gated readers rather than spaces, and the pricing decisions we made and then reversed on the way to it.