FREE
FOR
OSS
md0 CMS is free for public GitHub repositories. Add a visual editor to your open source project's docs, changelog, and blog. Contributors use GitHub OAuth they already have. No separate account needed.
START FREEThe Problem
Open Source Documentation Falls Behind
What Open Source Projects Have
Most open source projects have significant markdown content: a README, a CONTRIBUTING guide, a CHANGELOG, and often an entire docs site built with Docusaurus, Starlight, or MkDocs. Some have a project blog for announcements. All of this lives in the repository as markdown files, the same format that powers the codebase's documentation.
Why It Falls Behind
Open source projects have multiple contributors from different backgrounds. Core maintainers are comfortable with Git. Occasional contributors who want to fix a typo or expand a guide are often not. The "edit this page on GitHub" button helps with small fixes, but writing a full tutorial or updating a multi-page guide through GitHub's web editor is painful. Non-developer contributors (community managers, writers, DevRel) drop off when they hit the raw markdown editing interface.
The Result
Documentation gets updated only when a developer decides to do it. Release notes are written by the same person every time. The changelog falls months behind because nobody wants to edit a raw markdown file under time pressure. Community members who want to help with documentation give up when they realize the barrier is Git proficiency, not writing ability.
What md0 Gives Open Source Projects
A visual editing layer on top of your existing markdown files. No new format, no migration, no config to write.
FREE FOR PUBLIC REPOS
Open source projects are public repositories. md0 is free for public repos. No credit card, no usage limit, no "free tier with restrictions." Public repo means free.
GITHUB OAUTH — NO NEW ACCOUNTS
Contributors sign in to md0 with the GitHub account they already use. No separate CMS account to create or manage. If they have GitHub access to the repo, they can edit in md0.
COMMITS LIKE ANY CONTRIBUTOR
Every md0 save creates a regular GitHub commit. It appears in the repository history alongside all other contributions. Fully auditable. Pull request workflow still works.
WORKS ALONGSIDE EDIT ON GITHUB
md0 and the standard "edit this page" GitHub PR flow are not mutually exclusive. Developers keep using their local setup or GitHub.com. md0 serves contributors who want a richer editor.
Use Cases
Specific Open Source Use Cases
Changelog
Keeping CHANGELOG.md updated is one of the most neglected tasks in open source. With md0, the person doing a release opens the changelog collection in md0, adds a new entry with the version number, date, and release notes, and saves. The commit goes to GitHub. No raw markdown file editing under time pressure. A DevRel or community manager who is not a developer can own this step entirely.
Project Blog and Announcements
Project announcements, version release posts, and community updates fit naturally as markdown blog posts in the repository. Docusaurus includes a built-in blog plugin. Starlight supports blog pages. md0 gives the person writing the announcement (whether that is the maintainer, a DevRel, or a community lead) gets a clean editor instead of a raw markdown file.
Docs Site with Non-Developer Contributors
If your project runs a Docusaurus or Starlight site, md0 connects to the docs directory and shows every file in a collection view. A technical writer or community member who wants to improve the "Getting Started" guide or write a new tutorial can do so through the visual editor. They do not need to know Git. Their save creates a commit the same way any other contribution does.
README and Project Overview
The project README is often the first thing a potential user or contributor reads. Keeping it accurate and up to date matters. md0 can open a single-file collection pointing at README.md, making it easy for any authorized contributor to update the project description, feature list, or installation instructions without touching Git.
Workflow Fit
How md0 Fits the Open Source Workflow
It Does Not Replace Pull Requests
The existing "edit on GitHub" and pull request workflow continues unchanged. Developers who are comfortable with Git keep using it. md0 is an additional path, not a replacement. Both paths write markdown files to the same repository. The source of truth is still Git.
Branch Protection Still Works
If you require pull request reviews before merging to main, md0 respects that. You connect md0 to a staging branch. Contributors write through md0, their changes land on the staging branch, and the pull request goes through your normal review process before merging to main. The visual editor does not bypass your governance.
GitHub Discussions and Issues Are Separate
md0 works on file-based content in your repository. GitHub Discussions, GitHub Issues, and GitHub Wikis are separate systems that md0 does not touch. md0 is for your docs, blog, and changelog files: the markdown content that lives in directories like docs/, blog/, and single files like CHANGELOG.md.
No Impact on the Codebase or License
md0 only writes to markdown files. It does not modify source code, configuration files, or any file that is not part of a collection you define. The project license is unchanged. md0 is a tool that helps manage the documentation and content layer of the repository, not the code layer.
Example Setup
A Typical OSS Repository Structure
your-project/
├── README.md
├── CHANGELOG.md
├── docs/
│ ├── getting-started.md
│ ├── api-reference.md
│ ├── guides/
│ │ ├── installation.md
│ │ └── configuration.md
│ └── examples/
│ └── basic-usage.md
└── blog/
├── 2025-06-01-v3-release.md
└── 2025-04-15-roadmap-update.md
md0 collections:
docs/** Documentation
blog/** Blog posts
CHANGELOG.md Single-file changelogConnect md0 to this repository, define three collections, and any authorized contributor can edit docs, write blog posts, or update the changelog through a visual interface, without a Git client.
Why OSS Use Cases
ALWAYS FREE
Public GitHub repos get md0 free. No credit card. No usage caps. Open source projects should not pay for documentation tooling.
CONTRIBUTOR FRIENDLY
Lowering the barrier to documentation contributions means more contributors can participate. Not every useful contributor knows Git. A visual editor opens the door wider.
STAYS IN GIT
All changes commit to your repository. Full history. No data held by an external CMS database. Your documentation is portable and fully auditable.
NO VENDOR LOCK-IN
Your content is markdown in your own repository. If you stop using md0, every file is still there in exactly the format it was. No export step, no migration project.
FREE FOR PUBLIC REPOS
Connect your open source project in 2 minutes. No credit card required.
START FREE