CMS schema
A 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.
Updated
On this page
What it is
Schemas turn loose content into structured data. They decide which fields exist, what kind each is (text, number, image, reference, rich text) and which are required, so editors get the right form and the site gets the shape it expects.
In a headless CMS the schema lives in the CMS or in code; in a git-based CMS it lives in a file in the repo, next to the content.
In Xodia
In Xodia CMS the schema is each collection's collection.json, edited in the Fields tab: plain and rich text, images and galleries, links, numbers, dates, switches, colours, options, files and references, in groups, with required, help text, validation and defaults. Renaming a field moves its value in every item and updates the code that shows it.
For Sanity, Contentful, Storyblok, Prismic and Decap, the Content tab reads the schema from the source and builds each entry's form from it. Your AI's CMS tools check every value against the schema before writing.
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.
- Reference fieldA reference field links a content item to an item in another collection, such as a blog post to its author, so shared details are kept in one place.
- Git-based CMSA 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.