Connecting content with relations
A relation is the link between a content type and a vocabulary. It turns separate building blocks into one working system.
You have a Blog post content type and a Categories vocabulary. They are useful on their own — but they really shine when connected. A relation adds a field on Blog post that says "pick a category from this list." That single link powers filtered archives, related content, and listing blocks.
Below is the Blog post and Categories you built in tutorials 3 and 4. Click to add the reference field that connects them — this is what CMS developers call a relation or entity reference.
Try it: connect type and vocabulary
Add a reference field so every Blog post can be assigned a Category.
Blog post
Title · Body text · Featured image · Publish dateCategories
News, Guides, EventsThis adds a "Category" dropdown to the Blog post form. Editors choose from your vocabulary — they cannot invent random labels.
Relations avoid duplication
Without a relation, you might paste category names into every post by hand. With one, the CMS keeps them in sync.
Filters depend on relations
A "News" archive page works because posts reference the News term — not because someone tagged HTML manually.
Add relations as you grow
Team members can link to Departments; products can link to Categories — same pattern, different types.
Tip
You do not need to memorize "entity reference." Think: "this post belongs to that category list."
