GIT CMS
FOR TEAMS
Developers keep Git as the source of truth. Writers get a visual editor. Every save creates a commit. No "who changed this?" — Git knows.
GET STARTEDThe Problem
How Teams Work With Markdown Content
The Split That Slows Teams Down
Most teams building on a static site generator split into two groups: developers who own the codebase and writers who own the content. The developer builds the site structure, the collection schemas, and the deployment pipeline. The writer is responsible for publishing posts, updating copy, and keeping content fresh.
Writers Cannot Use Git. Developers Do Not Want to Hand-Edit Content.
When a writer needs to update a post, they file a ticket. The developer clones the repo, edits a markdown file, commits, and pushes. The writer waits. The developer is interrupted. A change that takes 30 seconds to type takes 30 minutes to ship because two people are involved in what should be a one-person task.
md0 Bridges the Gap Without Breaking the Stack
md0 puts a visual editing interface on top of the existing GitHub repository. Git stays the source of truth. The developer's workflow does not change. The writer logs in with GitHub and gets a clean editor. Every save the writer makes is a real Git commit. No separate database. No content stored outside the repo. No migration if you stop using md0.
Team Workflows md0 Supports
For writers
- Log in with GitHub — no separate account needed
- See only the collections they are meant to edit
- Write in a visual editor, no markdown syntax required
- Set status: draft to save without publishing
- Upload images by dragging into the editor
For developers
- Connect the repo once via GitHub OAuth
- Every writer save is a real Git commit
- Full history, diff, and blame in GitHub
- Schema builder enforces consistent frontmatter
- Pull request reviews work the same as on code
Requirements
What Teams Typically Need
Audit Trail
Every content change is attributed to a GitHub user in the commit history. No "someone changed this but we're not sure who." Git blame answers that question with a username, a timestamp, and the exact diff.
Draft Workflow
Writers save drafts freely without publishing. A status field in the frontmatter controls visibility. When a post is ready, the writer updates the status field and saves. The next build publishes it. No approval queue in a proprietary system.
Image Handling Without File System Access
Writers upload images by dragging them into the editor. md0 commits the image file directly to the GitHub repository under a path the developer configures. The writer never touches the file system or opens a terminal.
Consistent Frontmatter Structure
The developer defines a schema for each collection using the schema builder: which frontmatter fields exist, what type they are, and which are required. Writers fill in a form instead of editing raw YAML. The schema prevents invalid frontmatter from reaching the build.
No Vendor Lock-In
Content lives in markdown files in the team's own GitHub repository. If the team stops using md0, the content remains intact and the site continues building from the same files. No export. No migration. No data hostage.
Audience
Team Sizes That Fit md0
SOLO DEVELOPER WITH NON-TECHNICAL CONTRIBUTORS
You built the site. Your co-founder, marketing hire, or community manager needs to publish content. They cannot open VS Code. Connect md0 and they publish independently without filing a ticket or asking you to make an edit.
SMALL STARTUP TEAMS (2 TO 8 PEOPLE)
Mixed technical and non-technical members. Developers own the codebase; writers own the content calendar. md0 gives each group the interface that matches how they work, with Git as the shared record of truth for both.
OPEN SOURCE PROJECTS WITH EXTERNAL CONTRIBUTORS
Documentation contributors who are not core committers need a way to submit changes. md0 gives them a visual editor on top of your docs directory. Their edits go through the same pull request process as code contributions.
AGENCIES MANAGING CONTENT FOR MULTIPLE CLIENTS
You build the site once and hand the client a CMS. Connect md0 to the client's repository, set up the collection schemas, and give the client access. They update their own content without calling you. Your support load stays low.
SET UP YOUR TEAM
Free for public repos. Connect in 2 minutes. Your repo, your content, your Git history.
START FREE