PatchCMS
Git-backed content. No database lock-in.

Your Markdown site, editable in place.

Connect a GitHub repo, drop in one script, and let your team edit real pages by clicking Edit. Every change ships as a clean pull request against your Markdown source.

No credit card required · Your content never leaves GitHub

yourblog.com/writing-well

Essays

B I H

On writing clearly

Editing
Saved as a pull request

Works with the tools your content already lives in

GitHub Markdown Astro Next.js Hugo Jekyll Eleventy

How it works

From repo to editable site in minutes

No migration, no re-platforming. PatchCMS layers editing on top of the Markdown site you already have.

01

Connect GitHub

Install the GitHub App on the repositories that power your sites. Read and write, scoped to just those repos.

02

Analyze examples

Point us at a few live article URLs. We map each field to a stable selector automatically — no manual config.

03

Embed one script

Add a single async <script> tag. It stays invisible to normal visitors and mounts in an isolated Shadow DOM.

04

Edit & open a PR

Editors change content in place. Saves become commits on a branch; submitting opens a pull request for review.

Edit in context

Edit the real page, not a copy of it

Your team edits content exactly where readers see it — same fonts, same layout, same spacing. What you change is what ships. No context-switching to a separate admin, no “does this look right in production?”

  • Click Edit on any live page to start
  • Autosave keeps drafts safe as you type
  • Only mapped fields are editable — layout stays protected
Draft saved
B i U

On writing clearly

Open Update “On writing clearly”

content/essays/writing-well.md

1 ---
- title: On writing
+ title: On writing clearly
3 ---
Checks passed 1 file changed · +1 −1
Git is the source of truth

Every edit is a clean commit

PatchCMS never invents a hidden content store. Edits become surgical, frontmatter-preserving changes to your Markdown files — reviewable in a pull request, versioned in Git, revertible like any other code.

  • Byte-for-byte Markdown preservation — no reformatting noise
  • Full history, blame, and rollback stay in GitHub
  • Review and merge with your existing branch protections

Built for teams

Everything you need, nothing you'll fight

Roles & permissions

Invite editors and reviewers per site. A central access resolver decides who can edit what — no orphaned admin logins.

Isolated & safe

The editor mounts in a Shadow DOM, keeps its token in memory only, and never reads rendered HTML back as Markdown.

Automatic field mapping

Give us a couple of example URLs and discovery maps titles, bodies, and metadata to stable selectors for you.

Autosave & conflict-safe

Drafts autosave to Redis and atomic saves detect conflicts, so two editors never silently clobber each other.

Audit trail

An append-only event log records who changed what and when — for security reviews and peace of mind.

No lock-in, ever

Turn PatchCMS off and your site keeps working. It’s just Markdown in your repo — exactly as it was.

One line to install

Paste this once. That’s the whole integration.

index.html
<script async src="https://cdn.patchcms.com/editor/v1.js"
        data-site="site_PUBLIC_ID"></script>

Invisible to visitors. It only wakes up when an authorized editor signs in.

Give your team a CMS. Keep your Markdown.

Set up your first site in minutes. Your content stays in Git the whole time.