For WordPress exports you can define custom post types — their name, whether they have an archive, which features they support — and the custom taxonomies that categorize them.
Where: Left sidebar → CMS → Post types — Open the CMS panel
Key ideas
- Post type: Name, has-archive, and the supports list (title, editor, thumbnail, excerpt, author, custom-fields, comments, revisions, page-attributes).
- Taxonomies: Create custom taxonomies scoped to a post type (name + slug) to group its entries.
- Queries: A repeater bound to a post type can override its WP_Query — pagination type, item limits, and the pager element refs.
Steps
- Open CMS → Post types.
- Create a post type and set its supports.
- Add taxonomies to categorize it.
- Bind a repeater to it and tune its query/pagination.
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.