Collections are the content types your design binds to. Create a collection (page, post-type, block, widget, repeater, taxonomy, …), define its typed fields, reorder them, and manage entries.
Where: Left sidebar → CMS → Collections — Open the CMS panel
Key ideas
- Collection kinds: page, post-type, block, widget, repeater, taxonomy, breadcrumbs, listing.
- Fields: Typed fields (text, image, number, select, relationship, …) you drag to reorder.
- Entries: Add and edit the actual content records for the collection.
Steps
- Open the CMS panel and go to Collections.
- Create a collection and pick its kind.
- Add typed fields and reorder them.
- Add entries, then bind elements to the fields.
Collection kind determines behavior
- Page or post type for content entries with routable/publishable roles.
- Block or widget for reusable authored content structures.
- Repeater for ordered rows of the same typed schema.
- Taxonomy for categories/tags and relationships.
- Listing/breadcrumb-related structures for query/navigation output where supported.
Schema and entries are separate
Fields define the reusable shape; entries hold values. Renaming/removing/changing field types can affect bindings and remote content, so inspect usage and stage migrations rather than treating schema edits as cosmetic.
Binding workflow
- Create and name the collection.
- Add stable typed fields and relationships.
- Create representative entries.
- Bind text/media/repeated containers.
- Test empty/long/multiple content.
- Choose remote publish policy.
Ordered content models and delivery-safe bindings
CMS fields now use one ordered definition across tabs and drag reordering. Post types, searchable collections, contextual auto-binding, duplicate-with-mapping, typed media/video, nested menus, class toggles, and conditional visibility are connected through to the delivered runtime.
- Treat visibility as a render condition, not only an editor display style.
- Use explicit submenu link rows and test exported navigation.
- Review auto-connect suggestions when field names or repeated structures are ambiguous.
Tips
- Use stable machine-friendly field names even when the human label may change.
- Model reusable content concepts, not the accidental shape of one mockup.
Troubleshooting
A bound element becomes empty after a schema change
Check whether the field was renamed/removed or changed type, then update the binding and migrate the entry values.