Back to Blog

Why Your Content Should Stay in GitHub

Most CMS tools copy your content into their own database. RepoPress takes a different approach: your files stay in your GitHub repository.

When we built RepoPress, we had a choice: build another CMS with its own database, or build something that works with files already in your repository. We chose the second option.

The problem with most CMS tools

Most content management platforms store your content in their database. That creates a few issues:

  • Your content is locked in - Moving to a different tool means exporting data and hoping the format is compatible.
  • No real version history - You lose the detailed change tracking that Git provides.
  • Separate workflows - Developers work in GitHub, content writers work in the CMS, and the two worlds rarely meet.
  • Migration headaches - Switching platforms means data exports, format conversions, and broken links.

How RepoPress is different

RepoPress reads files directly from your GitHub repository and commits changes back when you publish. Here's what that means in practice:

  • Your content stays in your repo - Standard Markdown and MDX files, right where they've always been.
  • Real version history - Every publish creates a Git commit. You can see who changed what and when.
  • One workflow for everyone - Writers use the visual editor, developers review pull requests. Same repository, same process.
  • Nothing to migrate - Your content is already in the right place. There's nothing to export if you stop using RepoPress.

How it works under the hood

The key idea is simple: your Markdown and MDX files are already structured content. RepoPress adds a visual editing layer on top:

  1. Read - Your files are fetched from GitHub when you open a project.
  2. Edit - You write in the visual Studio editor with a live preview.
  3. Save - Drafts are stored temporarily so you can work without affecting your live site.
  4. Publish - Your content is committed back to your repository.

The draft storage handles the editing workflow (saving progress, version snapshots, review status), but the published content always lives in your Git repository.

The best of both worlds

RepoPress gives you a visual editor that anyone on your team can use, with the ownership and version control that Git provides. No compromise.