A CMS with no database
Content lives in the repository. The client gets a normal editing interface, and every edit is a commit with full history, so a bad change is reverted rather than restored from backup.
Case Study
Static Astro build in EN, ET and ES with automated deploys
Risto Tõldsep built qinutritionist.com as a multi-language static Astro site in English, Estonian and Spanish, with a git-based CMS so the client can edit content directly and GitHub Actions deploying every change automatically.
QiNutritionist serves clients in three languages, English, Estonian and Spanish, and the owner needed to edit content without a developer. A full CMS would be overkill for a site of this size, and hosting one is ongoing cost and ongoing security surface.
Content lives in the repository. The client gets a normal editing interface, and every edit is a commit with full history, so a bad change is reverted rather than restored from backup.
There is no PHP, no database and no plugin surface. For a small business site that removes an entire category of maintenance and an entire category of vulnerability.
GitHub Actions rebuilds and publishes when content changes, so the client never waits on a developer to see an edit go live.
Yes. A git-based CMS gives the client a normal admin interface, but instead of writing to a database it commits to the repository and triggers a rebuild. You get editing without running a server.
Usually, yes, and the bigger saving is maintenance. No database, no plugin updates, no security patching. The tradeoff is that genuinely dynamic features need a different approach.
Get in touch
Drop me a line and I'll get back to you as soon as possible.