Use the reorganized CMS workspace to define ordered content fields, bind layouts, manage nested menus, preview media, and make conditional visibility survive export.
Where: Website editor → CMS workspace/sidebar, including Post types, Collections, Menus, Pages, and Publish.
Key ideas
- One ordered field model: Post-type fields use one canonical ordered list. Tabs organize the editing UI without creating competing schemas, and drag ordering controls the content model users and bindings actually see.
- Binding is closer to the canvas: Post types are first-class in the CMS rail, collections are searchable, the contextual binding bar can target the current selection, and duplicate-with-mapping preserves useful relationships. Auto-connect examines the selected structure instead of asking users to manually wire every obvious field.
- Runtime behavior is part of the binding: Menu hierarchy, submenu links, media/video values, layout mapping, class toggles, and conditional visibility are compiled into the delivered page. Visibility is a render decision, not just an editor-only hidden style.
Steps
- Create or open the relevant post type and define the fields in their intended order. Use tabs for organization and drag to correct the canonical order.
- Open a collection or entry, add representative text and media/video values, and confirm the field types before binding a layout.
- Select the page element or repeated structure and use the binding bar or auto-connect flow. Review suggested field-to-element mappings rather than accepting ambiguous names blindly.
- Duplicate a bound layout with mapping when a new template should preserve the same content relationships.
- Build menus and submenus with explicit link rows; preview nested navigation and current-page behavior.
- Configure class toggles or visibility conditions and test entries where the value is true, false, present, and absent.
- Preview and export/publish the site, then verify the delivered runtime with real entries—not only the CMS editor preview.
Current workspace improvements
- Post types are a top-level CMS destination.
- Collections and related pickers are searchable; the floating contextual rail keeps binding near the selected element.
- Field tabs and drag-and-drop work over one ordered field definition.
- Media fields preserve typed image/video previews, including supported WordPress/Elementor content.
- Duplicate with mapping carries bindings into the duplicate instead of leaving a visually identical but disconnected layout.
Delivery-sensitive behavior
- Nested menu/submenu structure and link rows survive export.
- Layout bindings compile against the current canonical field model.
- Class toggles can switch authored presentation from CMS data.
- Conditional visibility determines whether content renders; hiding only in the editor would leak empty or sensitive blocks.
Tips
- Test with one sparse entry and one long entry. Perfect sample content hides missing-value and overflow failures.
- Keep field names semantic and stable; renaming a field after many bindings creates avoidable repair work.
Limitations and important notes
- Auto-connect is a suggested mapping, not a guarantee for ambiguous layouts or repeated generic field names.
- WordPress/Elementor imports can contain structures that need manual normalization before they behave like native fields.
- A working editor preview does not prove the deployed CMS endpoint, permissions, or menu URLs are configured.
Troubleshooting
A duplicated layout shows static sample text.
Use Duplicate with mapping or inspect its bindings; a normal visual duplicate may not carry the intended CMS relationships.
A hidden block still leaves space or appears in export.
Use the CMS visibility binding/render condition rather than only applying an editor style or manual display rule.