Most blogs reach for a database and a CMS on day one. For a small team writing occasionally, that's a lot of moving parts to babysit for what is, fundamentally, a folder of text files.
So this blog is exactly that. Every post is a Markdown file in the repo. When I want to publish, I write the file, commit it, and deploy. The running site reads the files from disk and renders them.
Why this works
- Version control for free. Every edit is a git commit. I can see the history of a post, roll one back, or draft in a branch.
- No database to run, back up, or migrate. One less thing that can break at 2am.
- Portable. The posts are just text. If I ever move platforms, they come with me untouched.
The tradeoff
Publishing means a deploy. That's fine here — I deploy through the same pipeline as everything else, and I'm not posting ten times a day.
Simple is a feature. Choose it deliberately, not by accident.
That's the whole idea. More soon.