A roomier product-marketing recipe for conversion pages, feature launches, and trial funnels.
Disclosures stay compact, accessible, and theme-aware for support or conversion pages.
Yes, through the shared appearance boundary.
Yes. Answers wrap inside the card rhythm without changing the template.
Yes. Count, column, and open-state evidence are emitted by the runtime.
Schemas, manifest metadata, editor fields, accessibility, and i18n remain attached to the block type.
The documentation route renders through native, alias, wrapped, or nonvisual runtime support without generic fallback UI.
Default, media, background, gradient, colorway, dense, and editorial configurations are all visible.
Every Theme Studio recipe has a focused page and an inline preview for this block.
CMS authors can lift structured payload recipes for default, media, operator, and stress contexts.
Default, empty, pending, active, invalid, and disabled states are documented for every cloneable block recipe.
Media replacement, long copy, and awkward content tolerance are represented in the documented defaults.
Smallest useful CMS payload with the block type, stable id, editable props, and recipe-aware appearance.
A brandable payload that includes placeholder media where the block can express imagery, previews, or visual proof.
A dense operator-friendly payload for dashboards, catalogs, forms, and internal review surfaces.
A resilience payload with plausible long CMS copy, longer labels, and dense supporting metadata to prove wrapping and spacing.