ORGANIZE BY
CONTENT TYPE
A collection is a named group of markdown files defined by a glob path pattern. One repo can have multiple collections — blog posts, documentation, and portfolio projects all managed separately, each with their own schema.
START FREEHow Collections Work
GLOB PATH PATTERNS
Define which files belong to a collection using glob patterns. content/posts/**/*.md matches all markdown files under posts/, including subdirectories.
INDEPENDENT SCHEMAS
Each collection gets its own frontmatter schema. Your blog post schema (title, date, tags) differs from your docs schema (title, sidebar_position, draft). Manage them independently.
FILE NAMING PATTERNS
Configure how new files are named when created: slug.md, YYYY-MM-DD-slug.md, or custom patterns. md0 generates the filename automatically.
Example Multi-Collection Setup
content/posts/**/*.mddocs/**/*.mdcontent/projects/**/*.mdpages/**/*.mdEach collection appears as its own section in the md0 CMS sidebar. Switching collections changes both the file list and the active schema.
Collection Features
CREATE NEW FILES
Create a new post inside any collection from the UI. md0 generates the filename, applies the schema defaults, and opens the editor ready to write.
BROWSE EXISTING CONTENT
See all files matching the collection pattern in a browsable list. Click to open and edit. md0 reads directly from your GitHub repo — no sync step.
WORKS WITH YOUR STRUCTURE
Collections match your existing folder structure. No need to reorganize your repo. Define the pattern to match what you already have — md0 adapts to your project, not the other way around.
MULTIPLE COLLECTIONS, ONE REPO
There is no limit on collections per connected repository. A mono-repo with blog, docs, and marketing pages can be organized into three separate collections, each managed through a distinct interface.
ORGANIZE YOUR CONTENT
Define collections for your existing folder structure. Free for public repos.
START FREE