If you maintain a developer tool or API, you know the pain of documentation drift. When the code changes, the docs fall behind. I recently built a documentation site for my open-source tool, api2md, using Thally.
Thally is a product knowledge layer for software teams. It does not just host your docs; it watches your product repositories and updates the docs when the code changes.
Here is why I chose Thally, how I built the site step by step, and the friction I hit along the way.
What Thally Is Doing Right
I have used Docusaurus, Hugo, and Astro Starlight. They are excellent static site generators, but they do not solve the sync problem. Thally stood out for a few reasons:
GitHub-native: Your content stays in Git.…