Catalogs & taxonomies
Model what exists (Catalog) and how people discover it (Taxonomy), then place that discovery model on a Page.
Catalog and Taxonomy are the Data types in Experience. They sit beside pages and navigation — they are not Content, and they are not a User Flow.
| Type | What it is | What it is not |
|---|---|---|
| Catalog | Types, attributes, and optional records (Product, Service, Article…) | Page copy or media requirements |
| Taxonomy | How that catalog is grouped for discovery — groups and attributes | The steps someone takes (that's a User Flow) |
| Content | Copy and media the page needs | A product schema |
| Page | Where a taxonomy is used | The catalog itself |
Catalog
Create one from Create → Data → Catalog. The Schema tab holds types and attributes. The Records tab is an optional grid — add rows by hand or import a CSV. Column headers become attributes when they are not already on the type.
Use a catalog when you need a typed source of items: products with shape and colour, services with duration, articles with topic.
Ask can write onto the open type. When the catalog (and a type such as Glasses) is focused, ask it to populate from a URL or a spec. It should reply with Attribute | Value tables. Use Update Glasses under the reply to add those attributes and a record — you do not have to type each field on the Schema tab. Head the table with another type name to update more than one type in the same reply.
Taxonomy
Create one from Create → Data → Taxonomy. Bind it to a catalog so nodes can pick real attributes rather than free-typed Filter badges. The editor is the same tree family as menus and sitemaps, but the nodes are Group and Attribute.
A group is a named section on a listing or filter surface — Fit, Appearance, Availability. It is not a catalog type and it does not filter anything by itself. Add catalog attributes inside the group (Add inside, or Add attribute from catalog on the selected group). An attribute node is a placement of a field that already exists on the catalog — switching a node to Attribute or picking a field does not add that field to the catalog schema. Edit the Catalog to create new attributes. That tree is what a page uses when you link the taxonomy.
A taxonomy does not replace the main menu or the sitemap. Those say where you go in the site. A taxonomy says how items in a catalog are sliced on a listing or search surface.
Linking from a page
On a page, add a Taxonomy item the same way you add Feature or Content — pick an existing taxonomy or create one. You can also use Link taxonomy in the graph rail. Either path stores a contains relation and a discovery pointer so it is obvious which browse/filter model the page uses.
Legacy Filters
Older projects may still have a Filters navigation (navigation with role filters). Those stay openable. New work should use Catalog + Taxonomy instead — Crux no longer creates Filters entities from Ask, site scan, or URL generation.
Next
Related articles
Documents: Catalogs & taxonomies