Layout Guide
Layout Guide
Layouts define the shared page frame used across one or many Pages.
If Components are the visible sections inside a page, Layouts are the structural system around them. They help teams keep page families consistent without rebuilding the frame of the page every time.
When To Use a Layout
Use a Layout when multiple Pages should share the same structural experience, such as:
- a standard site layout
- a landing page frame
- a campaign page family
- a documentation or knowledge layout
- a page type with shared side regions, navigation, or support areas
If the structure should stay consistent across several Pages, it usually belongs in a Layout.
When Not To Use a Layout
Do not use a Layout for:
- one-off page messaging
- a single section that belongs inside page content
- minor visual differences that do not justify a new page frame
Those usually belong in Components or directly inside the Page composition workflow.
Recommended Workflow
- Define the page family
- Decide what should stay shared
- Build or choose the Layout
- Assign it to the right Pages
- Review impact before changing a live Layout
What Makes a Good Layout
Strong Layouts usually:
- stay structural rather than message-specific
- support a repeatable page family
- keep shared framing in one place
- avoid carrying one-off campaign or page copy
The clearer the Layout is, the easier it is for Pages to stay consistent.
Common Use Cases
- main company site layout
- landing page layout
- documentation layout
- resource layout
Common Mistakes
- creating too many Layouts with very small differences
- putting one-off campaign content into a shared Layout
- using Layouts to solve section-level problems
- editing a shared Layout without checking all affected Pages
Team Guidance
- keep the number of active Layouts intentional
- design Layouts around page families, not one page
- review downstream impact before structural changes
- use Components for content sections, not structural overload