Blocks
Manage reusable blocks.
Custom Block Tabs and Accordions
Last updated: 2026-09-14. Published custom blocks keep their existing definition version and saved content.
- Tabs: Each tab displays its own content. Choose the default tab in the block definition. Visitors can switch tabs with the arrow keys and use Home or End to reach the first or last tab.
- Accordions: Each section contains its own collapsible content. Default Open expands the first section initially. Allow Multiple lets several sections stay open; otherwise opening one closes the previous section in that block.
- Preview: Check each tab and accordion section in Live Preview before publishing. Nested and reused custom blocks keep their interaction state independent.
Repeated Content Items
Last updated: 2026-09-14. These controls apply only when the selected custom-block definition explicitly exposes an item collection. Existing definitions keep their original fields.
- Edit a collection: Add an item, fill its fields, and use the arrow controls to change its position. Remove affects only that item. The displayed count shows the definition's item limit.
- Preserve the draft: Item changes stay in the owning editor's draft until its normal save action. Opening the editor does not convert or save existing content. Read-only views disable item changes.
- Handle invalid content: An invalid collection displays an error instead of being silently reset or shortened. Ask the block publisher to review its saved values and compatible definition version.
General builder activation, complete storefront inline editing and localized item workflows are still pending. Do not force an existing definition into item mode; continue using its published fields until a compatible version is available.
Custom Block Version Checks
Last updated: 2026-09-14. Top-level custom blocks are checked before page saves, publication, version restoration and block translation saves.
- Keep the selected version: Each custom block uses its saved definition version. Saving a page does not silently switch to the newest version. A translation must use the same version as its source.
- Resolve a rejected save: Check the block's version and repeated item values. Missing or deleted definitions, active draft versions, duplicate item identities and excessive item counts are rejected before the page is changed.
- Restore carefully: A valid snapshot restores its block values and version pins. If its custom definition is unavailable, ask the block publisher to restore the compatible definition or replace the affected placement explicitly.
General repeatable builder activation and localized item workflows remain staged. These checks do not make every nested block or content-owner workflow feature-complete.
Custom Blocks Inside Page Layouts
Last updated: 2026-09-14. Custom children inside Content Composition, Column Layout and Tabbed Content are checked before page saves and lifecycle changes, including children in inactive tabs.
- Resolve a rejected layout: Check every nested custom block's selected version and repeated item values. A missing version, active draft, invalid item identity or excessive item count prevents the whole save; existing page content is retained.
- Keep compatible versions: Each child uses its own saved version. Page saves and version restoration do not automatically upgrade children to the latest definition.
- Simplify excessive nesting: A root layout supports up to 16 child-placement levels and 500 combined placements and tab groups. Split larger layouts into smaller page sections before saving.
Translation saves check nested item values, but preserving nested versions, item identities and structure across languages remains a separate staged workflow. General repeatable builder activation and other content-owner integrations are not yet complete.
Repeatable Template Limits
Last updated: 2026-09-14. A repeatable item's template permits at most eight primitives, including wrappers and their descendants. A Stack or Card with seven content primitives reaches the limit; eight content primitives inside that wrapper exceed it.
- Check the whole template: Each repeatable group has its own eight-primitive limit and two-level item depth. The complete definition still has a 40-node limit and five-level depth.
- Keep item counts separate: The number of repeated content items is a different limit. Adding item values does not create new definition nodes.
- Resolve rejected versions: Definition saves, publication and historical version restoration enforce the structural limits. Older oversized versions are not trimmed, rewritten or upgraded automatically; a publisher must prepare an explicit corrected version.
Binding authoring and other repeatable workflows remain staged. Passing these server checks does not activate the complete feature.
Resolve a Rejected Builder Edit
Last updated: 2026-09-15. Adding, moving or duplicating a primitive, or loading a preset, checks the resulting definition before changing your draft. A rejected edit displays the structural limit and leaves content, selection, unsaved status and undo/redo history unchanged.
- Count wrappers and children: Each repeatable item template permits eight primitives across two levels. One Stack or Card with seven content primitives reaches the limit. Stack and Card are the supported wrappers; other layouts and nested repeatable groups are not permitted inside the template.
- Check the complete definition: The full tree permits 40 primitives and five levels, including the root. A layout's direct-child capacity also applies to moves and duplicates. Repeated item values do not add definition nodes.
- Repair explicitly: Remove excess primitives or unnecessary wrappers before retrying. Existing definitions still load without automatic trimming or binding conversion; removal and undo/redo remain available. Save a corrected definition version through the owning workflow instead of changing published content or version pins.
These checks cover structure, not the complete repeatable authoring rollout. Explicit binding authoring and the remaining repeatable integrations are still staged.
Open A Form From A Call To Action
- Choose an action: In the block's CTA destination settings, choose Open form in modal instead of Navigate to URL.
- Select a form: Choose a published managed form, such as Contact us. Unpublished forms cannot be selected.
- Save and preview: Save the page draft and test the CTA in the storefront preview. The form opens over the current page and submits without changing its URL.
- Publish: Publish the page to make the CTA available to visitors. Existing navigation CTAs remain unchanged.
- Supported blocks: Hero, text, hero slider/carousel, carousel cards, image grids, brand showcases, resource lists and custom LinkTo destinations support modal forms. CTA banners retain their existing form action.
- Submission tracking: Validation, workflows and lead attribution use the managed form's normal submission pipeline. Published pages using a modal form prevent that form from being deleted.