flowmo’s CMS binds design elements to content. You define collections (page/post-type/block/repeater/taxonomy) with typed fields, then connect element text/images/links to those fields.
Where: Left sidebar → CMS — Open the CMS panel
Key ideas
- Collections: page, post-type, block, widget, repeater, taxonomy, breadcrumbs, listing.
- Connection types: Bind a field to text, image, background, color, link, an attribute, or visibility.
- Project type: Choose Simple, WP Pages, ACF Blocks, or Elementor for how it exports.
Steps
- Open the CMS panel and pick a project type.
- Create a collection and add fields.
- Select an element and bind it to a field via the binding bar.
Collection kinds
- Pages and post types for routable content.
- Blocks/widgets and reusable page parts for structured regions.
- Repeaters/listings for repeated rows.
- Taxonomies and breadcrumbs for classification/navigation.
Binding types
- Text content, image source, background, and color.
- Links and arbitrary attributes.
- Visibility rules.
- Collection/repeater roots that repeat a designed child structure.
Export model
The selected project type—Simple, WordPress Pages, ACF Blocks, or Elementor—changes how the same authored design and collection schema are packaged for WordPress.
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
- Design and bind one representative item before duplicating a repeater.
- Use stable field names early; renaming after content exists can require migration on the remote site.