Content collections
Content 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.
Updated
On this page
What it is
Most sites repeat some content: articles, case studies, people, events. Instead of hard-coding each one into a page, a collection keeps them as entries with the same fields, and the pages read them. Add an entry and every list and page that shows the collection picks it up.
When the entries are files in the repository, such as Markdown with the fields at the top, content and code move together: versioned, reviewed and deployed in one place, with no extra service to host.
In Xodia
Xodia CMS is built on collections in your repository. In the Content tab you create one from blank or a starter, choose its fields, and add items as forms; each collection is a folder in content with a collection.json and one Markdown file per item.
A Collection List shows a collection on any page, and its collection page gives every item an address of its own. Existing Markdown folders and Decap collections can be turned into Xodia collections in one step.
Read more
Related terms
- 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.
- 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.
- Collection pageA collection page is one page design that shows every item of a CMS collection, each at its own address, such as /blog/my-first-post for each post in a blog.