Content Collections Explained: The Contenode Data Model

Collections are the core building block of Contenode. Learn how to model any content type — from blog posts to product catalogs — using fields, locales, and relations.

By Contenode Team•November 2, 2026

In Contenode, everything is a collection. A blog is a collection of posts. A team page is a collection of members. A FAQ section is a collection of question-answer pairs. The same flexible system handles all of them.

Defining fields

Each collection has a schema — a list of fields with types like text, textarea, richtext, media, select, and relation. You define the schema once, and every entry in the collection follows it.

Localizable fields

Any field can be marked as localizable. When it is, Contenode stores a separate value per language and returns the correct one based on the ?locale= parameter in the API request.

Relations between collections

A relation field links entries across collections. For example, a blog post can relate to one or more authors from a separate authors collection. The public API resolves these relations automatically when you request depth=1.