A type declares the fields its listings carry — a film has a director and a certificate, a property has bedrooms and a price. The fields are typed, so the site knows what it is rendering.
Talk to us about your catalogue →A type declares the custom fields its listings carry. Text, numbers, dates, choices and more, each behaving as its kind should.
Most of a real catalogue page is tables, not single values — a film’s cast is a dozen rows, its crew twenty. Repeating groups are how those are held.
Give several fields the same section name and they render together under one heading, with jump links at the top of the page.
A gallery per listing, each image with its caption, which becomes the figure caption on the page.
A collection produces a grid of cards and a page per item, both from markup the site owns.
Only published listings appear. The release date orders the grid and shows on the card.
A demonstration installation, with invented data.
Every catalogue tool can hold a title and a photograph. Where they fall down is the cast list, the specification table, the opening times — the repeating rows that make up most of a real page.
Repeating groups hold those as data rather than as a blob of pasted HTML, which means they can be sorted, filtered and restyled later without re-entering them.
A collection carries its own wrapper and item markup, so a catalogue looks like the site it is part of rather than like a plugin. Publishing a listing to the public site needs Publishing rights; day-to-day editing does not.
One engine, any catalogue.
Films, properties, products, people, projects. The tool does not care what they are, only what fields they carry. Get in touch →
