Publish selected CMS collections and entries through the connected WordPress/CMS workflow, with per-scope actions, bulk operations, status/error feedback, and explicit content, repeater, and layout policies before remote writes.
Where: Left sidebar → CMS → Publish content — Open the CMS panel
Before you start
- Connect and authenticate the destination CMS/WordPress site, then verify collections, fields, entries, bindings, and target scope against staging.
Key ideas
- Content and design publish are distinct: Pushing collection entries is separate from exporting/publishing the website/theme/layout.
- Selective scope: Choose collections/pages and whether content, repeater rows, and layout are changed, preserved, filled, or skipped.
- Plan before write: Review touched/untouched items and heed blind-plan warnings when the live site could not be fully compared.
Steps
- Open CMS → Publish content and choose the connected staging site.
- Select the exact collections/pages/entries in scope.
- Choose content, repeater, and layout policies; enable skip-empty/create-page/front-page/menu options only when intended.
- Run Check what will change and review touched/untouched items plus warnings.
- Publish, inspect per-item synced/error status, then verify the remote site and record a rollback path before any broader update.
Policy examples
- Content: only changed / fill empty / all / off.
- Repeaters: keep extra / replace / only if empty / skip.
- Layout: keep / rebuild.
- Optional: skip empty, create pages, set front page, add to menu.
High-risk choices
Replace repeater rows can remove remote-only rows; rebuild layout can overwrite remote layout work. Use them only when flowmo is the intended source of truth for that scope.
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.
Troubleshooting
The plan is blind or incomplete
Stop before publishing, restore destination read access/connectivity, and rerun the comparison; do not assume untouched remote content will be preserved.