YOUR CONTENT.
YOUR REPO.
YOUR CMS.
A git-based CMS that reads and writes your markdown files directly in GitHub. No database. No infrastructure. No vendor lock-in.
What is a git-based CMS?
A traditional CMS stores your content in a proprietary database. A git-based CMS stores your content as plain files in a Git repository. Markdown posts, MDX pages, YAML data, all committed alongside your code. The CMS is just a layer that reads and writes those files.
This means your content benefits from everything Git already gives you: full version history, branch-based workflows, pull request reviews, and the ability to roll back any change. No extra tooling required. It is all built into Git.
Git-based CMSes pair naturally with static site generators. Your SSG (Next.js, Hugo, Astro, Jekyll) reads the files from the repo at build time. When you save content in the CMS, it commits to the repo, which triggers a rebuild. The whole pipeline is transparent and auditable.
No Vendor Lock-in
Your content is plain markdown in a Git repo you own. Leave any git-based CMS and keep every file, every commit, every word.
Version History Free
Every content change is a Git commit. Diff any two versions, revert to any previous state, review changes in pull requests.
No Database
No Postgres. No MongoDB. No content database to manage, back up, or pay for. Your repo is the database.
Works with Any SSG
Next.js, Astro, Hugo, Jekyll, Gatsby, Eleventy. If it reads files from a directory, it works with a git-based CMS.
How md0 CMS works
Connect via OAuth
GitHub OAuth login. Select the repository you want to manage. Choose a branch. No API keys to create, no SSH keys to configure, no webhooks to set up.
Define Collections
Map path patterns to content types. content/posts/** becomes a Posts collection. docs/**/*.md becomes a Docs collection. Configure frontmatter schemas per collection.
Edit and Auto-Commit
Write in the visual WYSIWYG editor. Every save creates a commit to your GitHub repository automatically. Your SSG rebuilds. No deploy step needed.
Every save = one Git commit. Your content history is your commit log.
Git-based vs API-based CMS
API-based platforms like Contentful and Sanity make sense for complex data models. For markdown-first sites and static site generators, a git-based CMS is a simpler and cheaper fit. Compare md0 vs Contentful →
Works with your SSG
md0 CMS writes standard markdown to your repository. Any static site generator that reads from files works without modification.
YOUR GIT REPO
IS YOUR CMS.
Connect your GitHub repository and start editing markdown visually. Free for public repos.
No credit card required · 2-minute setup · Free for public repos