Use default layouts for consistency and record-level layout choices for intentional exceptions.
CMS Max resolves layouts from each record, the resource-type default map, and the active theme fallback while keeping reusable section slots attached to the layout.
How layout selection works
- A page or supported content record can reference a specific layout.
- Theme Configuration can map default layouts to resource types such as pages, blogs, products, or installed plugin content.
- When a record has no explicit layout, CMS Max resolves the configured default and can fall back to the active theme default.
- A layout controls slots such as header, above content, content, below content, footer, and other template-defined areas.
Change layouts safely
- 01Preview the destination layout. Confirm its slots and assigned sections.
- 02Check dynamic content. Make sure the content slot, required widget, sidebar, and page-title behavior remain correct.
- 03Choose the scope. Update one record or change the resource-type default.
- 04Decide whether to apply the new default to existing records. That operation can update content in the background and should be tested first.
- 05Verify responsive states. Check header, content width, footer, mobile sticky content, and any sidebar.