Write. Save.
Done.
Every save in md0 CMS creates an automatic commit in your GitHub repository. No Git commands, no manual push, no deploy button. Your static site generator detects the new commit and rebuilds automatically.
The Full Flow
Step 4 is your deploy platform's own build trigger (Vercel, Netlify, GitHub Actions), not something you configure in md0.
What Happens Behind the Scenes
md0 Calls the GitHub API
When you save, md0 uses the GitHub Contents API to write the updated file. It sends the new content and a commit message. You don't need a Git client, SSH keys, or tokens. md0 handles authentication through your OAuth session.
A Real Commit Lands in Your Repo
The commit appears in your GitHub history like any other push. You can see it in the repository, inspect the diff, or revert it with standard Git tools. No shadow database, no separate content store.
Your Deployment Platform Rebuilds
Vercel, Netlify, Cloudflare Pages, and GitHub Actions all watch for pushes to your branch. When the commit lands, they trigger a build. Your static site generator rebuilds the affected pages and the new content is live within minutes.
Why This Matters
No separate deploy step
Traditional CMS workflows require a separate "publish" step that triggers a deploy. With md0, saving is publishing. The commit is the deploy trigger.
Full audit trail
Every content change is a commit. Git history is your audit log. You know who changed what, when, and can diff any two versions of any file.
Easy rollbacks
Published the wrong content? Revert the commit in GitHub. The next deploy picks up the revert and your site is back to the previous state. No CMS-specific undo feature needed.
Works with existing CI
No changes to your GitHub Actions, Netlify config, or Vercel settings. md0 pushes commits. Your existing deployment pipeline handles the rest.