Git-based CMS
A git-based CMS is a content management system that stores content as files in your site's git repository and saves edits as commits, instead of keeping it in a separate database.
Updated
On this page
What it is
A git-based CMS gives writers a form-based editor, but what they write ends up as Markdown, JSON or YAML in the repo. Content and code move together, can be reviewed in the same pull request and need no extra service to host.
Each one describes its collections and fields in a file in the repository, which is also what makes the content editable elsewhere and easy to take with you.
In Xodia
Xodia CMS is a git-based CMS built into Xodia: each collection and its fields live in a collection.json file in its own folder under content, such as content/blog, each item is a Markdown file, and every edit is saved with the rest of your changes and pushed as a commit.
The Content tab also edits Decap CMS collections and plain Markdown folders, and can turn them into Xodia collections. The git-based CMS stack pack tells your AI how Decap stores media and drafts.
Read more
Related terms
- Content collectionsContent collections are groups of entries of the same kind, such as blog posts, projects or team members, that share one set of fields and live as files beside a site's code.
- Headless CMSA headless CMS stores and serves content through an API without deciding how it looks, so any site or app can fetch the content and render it in its own design.
- CMS schemaA CMS schema is the definition of a site's content types and their fields, such as a blog post with a title, a date, an author reference and a body, that every entry must follow.