Interactive graph
Git-Based CMS
Table of Contents
A git CMS commits markdown to the repo so clients get buttons while the same push-live build still runs.
Key Concept
- Publish via Git directly when you are the author; clients often will not.
- Git stays source of truth; the CMS is just another commit path.
- Still say no to bad dynamic scope - CMS does not add a database.
- Minimum Effective Dose for solo sites: skip the CMS layer entirely.
Examples
- Church volunteer will not open a terminal - Sveltia on the repo, she edits announcements, Cloudflare rebuilds on save.
- I added Decap for a client who insisted on WordPress-like editing - honest scope: blog posts only, not plugins; still cheaper than hosted WordPress long term.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Minimum Effective Dose | when a solo dev site does not need a CMS layer on top of markdown |
| extends | Client Site Pass-Off | CMS pass-off is a fourth path when Git lesson will not land |
| extends | Free Tier Hosting Stack | Still markdown in git, still Cloudflare build on push |
| extends | Static Site Client Scope | Widens who can edit without redirecting to WordPress |
