←  All terms
R
CMS & Content

Reference Field

A reference field links one CMS item to another record without duplicating its content.

A reference field creates a structured relationship between CMS items so related content can be reused without duplication. This makes it easier to model connections between different content types, maintain consistency, and update information centrally. The concept is closely related to CMS Collection and Taxonomy.

Read more

CMS Collection

Taxonomy

Content Modeling

Internal Linking

FAQ

Reference Field

What mistakes commonly occur with reference fields?
Typical problems are overly nested relationships, duplicate items with slightly different names, and references to items that are deleted later. The result is empty sections in templates or inconsistent filters. A clean content model with clear naming rules and documented relationships prevents most of this.
When does a reference field beat a plain text field?
As soon as the same information appears in several places, such as authors, categories, or locations. A change to the linked item then takes effect everywhere. For one-off values with no reuse, a text field is simpler. The effort of extra collections only pays off when maintenance or reporting benefits from it.
How does a reference field differ from a multi-reference field?
A reference field points to exactly one item, while a multi-reference field points to several. A blog post typically has one author but multiple topics. The choice follows the data logic: if an item has exactly one counterpart, a single reference is enough. Several associations call for a multi-reference, which makes templates and lists more complex.