DOCS THAT LIVE
IN GIT.
EDITED VISUALLY.
Keep your docs in your repo. Edit them in a visual interface. Every save auto-commits. No manual Git workflow for writers, no separate CMS database for developers.
The Problem
Documentation Has Specific Needs
Nested Structure
Documentation sites are not flat. They have categories, subcategories, sidebar ordering, and cross-links between pages. Docusaurus uses sidebar_position in frontmatter to control order. Starlight (Astro) uses directory-based structure. Nextra reads a _meta.json file. A good CMS for documentation must support these metadata patterns without breaking the generator's expectations.
Multiple Contributors, Different Skill Levels
On most projects, the developers who write API reference docs are comfortable in a text editor. But product managers, support engineers, and technical writers who contribute conceptual guides and tutorials often are not. A docs site that requires Git knowledge creates a bottleneck: only the developers update the documentation, and it quickly falls behind what the product actually does.
Common Documentation Stacks
Most static documentation sites use Docusaurus, Nextra, Starlight, VitePress, or MkDocs. All of these read markdown files from a directory structure in a Git repository. md0 CMS works at the file level, which means it works with any of these tools without modification. You do not need a plugin, an adapter, or a custom integration.
Built for Docs Teams
Documentation is uniquely suited to a Git-based CMS. Docs live next to the code. Changes go through PR review. History is free. md0 adds the visual layer so non-developers can contribute.
DOCS-AS-CODE, VISUALLY
Developers keep their docs in the repo. Technical writers get a visual editor. Both workflows coexist; the source of truth is always Git.
STRUCTURED FRONTMATTER
Define doc metadata as typed fields: title, sidebar_position, sidebar_label, description, tags. md0 renders these as a form, no hand-editing YAML.
VERSION CONTROL BUILT IN
Every doc edit is a commit with an author and timestamp. Roll back a bad change with standard Git. Track who changed what and when, with no separate audit log to maintain.
WORKS WITH YOUR TOOL
md0 does not care what generates your docs. Docusaurus, MkDocs, VitePress, Nextra, Starlight: if it reads markdown from a GitHub repo, md0 works with it.
Honest Assessment
Where md0 Fits and Where It Does Not
Best for: Conceptual Content
md0 is the right tool for "Getting Started" guides, tutorials, conceptual overviews, FAQs, and any section of your documentation that reads like prose. These pages benefit from a visual editor because the writer focuses on explanation, not on remembering markdown syntax for headings, callouts, and tables.
Best for: Non-Developer Contributors
Product managers and support engineers who know the product deeply but not Git can now contribute docs without a developer handholding them. They write in the md0 editor, save, and the change appears in the repository as a regular commit. The existing CI/CD pipeline picks it up and redeploys the docs site automatically.
Less Relevant for: Raw API Reference
Heavily code-annotated API reference pages (where every paragraph contains a code block, a parameter table, and cross-references to other pages) are better written in a code editor with proper language support and syntax highlighting. Developers working on this type of content typically prefer their local setup. md0 does not get in the way of that; both workflows commit to the same repository.
Team Workflow
Multi-Author Docs and Versioning
Pull Request Workflow Still Works
md0 creates commits the same way any contributor does. Your existing GitHub branch protection rules, required reviewers, and CI checks still apply. A writer edits a doc in md0, saves it, and the commit lands in the repository. If you want a review step, require a pull request for the docs branch; md0 commits into that branch and the standard review workflow continues uninterrupted.
Docs Versioning
Docusaurus handles docs versioning through Git branches. md0 connects to a specific branch in your repository. If you maintain separate branches for different version of your docs (for example, docs-v1 anddocs-v2), you connect md0 to whichever branch the editors should be working on. Switching between versions is a branch selection in the md0 settings, no new integration required.
Image and Diagram Uploads
Writers drag images and diagrams directly into the md0 editor. The file uploads to your GitHub repository under a path you define, such as docs/assets/ or static/img/. The markdown file gets an image reference pointing to the stored path. Your docs generator serves the image as a static asset during the build. No external CDN or image hosting service required.
How It Works
Connect Your Docs Repo
Sign in with GitHub, select the repository that contains your docs, and choose the branch. Works with monorepos (docs in a subdirectory) and dedicated docs repositories.
Map Collections to Your Docs Structure
Use glob patterns to define collections that match your documentation layout:
docs/**/*.mdAll documentationdocs/api/**/*.mdAPI referencedocs/guides/**/*.mdGuides and tutorialsblog/**/*.mdRelease notes and announcementsDefine Doc Metadata as Schema Fields
Set up the frontmatter your docs tool expects. Each field gets a type and validation rule.
Write, Review, Publish
Technical writers edit in the visual editor. The save button commits to GitHub. Your docs deployment picks it up and rebuilds. Developers can still contribute via their normal PR workflow; both paths write to the same repo.
Documentation Types
API DOCUMENTATION
Endpoint references, parameter tables, code examples. Keep them version-controlled in Git alongside the code they describe.
PRODUCT DOCS
User guides, feature walkthroughs, how-tos. Writers edit visually while developers maintain the structure.
OPEN SOURCE DOCS
Public repo documentation is free with md0 CMS. Non-technical contributors can improve docs without learning Git.
INTERNAL KNOWLEDGE BASE
Private repos get the same visual editing interface. Team wikis and runbooks in Git, edited in a browser.
BUILD BETTER DOCS
Free for public repos. No changes to your docs generator. Connect in 2 minutes.
START FREE