I'm a freelancer and solopreneur, and I run two products: a SaaS for CrossFit competitions, and Kerflow, an open-source tool to find local leads.
Two products, two documentation sites to maintain. On my own.
And every time, I ended up with the same setup.
A Node project, a framework, a build step, a CI pipeline⦠just to show some Markdown.
So I built tidydoc .
A folder of Markdown files, one Docker container, and you are done.
Today, I edit my docs with Claude Code (or by hand), commit, and push to GitHub.
A few seconds later, the site is up to date. No rebuild, no container restart.
A few developers asked me about it.
So today, I will tell you why I built it, and how it works under the hood.
Docs should not need a build pipeline
Let me explain.
You have two main options to ship docs for your product today.
A static site generator. You install Node, add a framework, write a config file, run a build, and deploy the output.
A hosted docs platform.β¦