The catalog is powered by structured JSON records. Each record can carry a number, name, status, taxonomy labels, stats, traits, attributes, related locations, source facts, and image references. The template renders that same record in the catalog grid, the home rail, search results, role pages, element pages, region pages, and the individual detail view.
This means a project team should avoid duplicating catalog copy manually across the site. Add or update the record once, then let the pages consume it. The existing components are intentionally opinionated: cards are visual, detail pages are dense, taxonomy pages are scannable, and related entries are linked by ID.
For a new project, start with ten high-quality records and run the build. Once the pattern is proven, import the rest of the catalog in batches and keep source provenance attached to every factual field.