Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add warning about using existing tag names for taxonomies #1403

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add warning about using existing tag names for taxonomies #1403

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions content/collections/docs/taxonomies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,11 @@ Each entry in a taxonomy is often called a **term**.
Watch how to set up your first Taxonomy
:::

> [!CAUTION]
> Avoid giving your taxonomy a name that is already used for a Statamic system [tag](tags).
> Using an existing tag name will create complications when you come to reference your taxonomy and its terms in views.
> For example, if you call your taxonomy 'Section', that will conflict with the system tag {{ section }} in your templates.

## Collections

Each collection defines which taxonomies are part of its content model in their blueprint. Thus, taxonomies and their terms are connected to entries _through_ the collection in a strict relationship. Once you attach a taxonomy to a collection, the fields, variables, and routes are added automatically.
Expand Down