Introducing PatchCMS
Most content teams live in two worlds. Developers keep the site in a Git repository, where every change is reviewed and deployable. Editors work in a CMS, where content lives in somebody else's database and drifts away from the code that renders it.
PatchCMS removes the second world. Your Markdown files stay in your repository, your site keeps rendering them however it already does, and editors change content directly on the live page. When they hit save, we open a pull request against the Markdown source.
How it works
- Connect GitHub. Install the GitHub App on the repository that powers your site.
- Analyze examples. Point us at a few live articles and we map fields — title, body, description — to the selectors that render them.
- Edit live pages. Editors click, type, and save. Every save becomes a clean pull request.
No migrations, no new hosting, no export lock-in. If you ever stop using PatchCMS, you keep everything: it was always just Markdown in your repo.
Who it's for
Teams that already publish with a static site generator or a custom Markdown pipeline, and want non-technical teammates to edit without learning Git. If your content is .md files and your review process is pull requests, PatchCMS fits in without changing either.
Create an account and connect your first repository in a few minutes.