Git-Based CMS

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.
• Level 1: You push through Git when you write the site - clients need buttons, like cooking versus a menu with pictures.
• Level 2: Git-based CMS is like a kitchen with a back door for chefs and a counter for customers - Git for authors, buttons for clients who will never touch a terminal.
• Level 3: Because Git stays source of truth, the CMS is just another commit path - not a second database that forks reality.
• Level 4: Use Git publish for solo sites; offer a CMS when the client will never touch a terminal - still say no to bad dynamic scope.
• Level 5: Git stays source of truth; the CMS is just another commit path - Minimum Effective Dose for solo sites is skip the CMS layer entirely.
• 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