Skip to content
Home

All changes

Introducing Label groups

  • New

Labels can now be organised into groups that your team defines, and each group can be scoped to the templates where it belongs, so editors only see relevant labels and a label such as Region / Nordics reads the same everywhere.

What your site sees

// The content index resolves every label to a single term:
// grouped labels become "Group/Name", ungrouped ones stay bare.
labels: ["Region/Nordics", "Draft"]

// Filter a list page on one of them
query.whereIn("labels", ["Region/Nordics"])

Only one term is stored per label, so moving an existing label into a group replaces its bare name. Update any filter that still queries the old value. Label fields nested inside chapters and content templates resolve the same way, and so does live preview.

What your site needs

@strifeapp/strife 1.9.2 or later. Grouped labels resolve to Group/Name in the content index from 1.9.0, and label fields nested inside chapters and content templates follow in 1.9.2. The index source ships inside the SDK, so upgrading the package is only half of it. Run strife push afterwards to redeploy your content index, or the old projection stays live and your labels keep resolving the old way.