Configuring content zones in a content template

The template author adds all text blocks, components, and layouts along with the content in this zone type.

Ensures strict structural and content consistency across all pages by using the template.

The template author adds all text blocks, components, and layouts used within this zone.

Provides structured content areas while allowing page editors to customize the actual content.

Template authors typically fill components in these zones with placeholder values or images to provide an empty state for the editor to fill.

These zones are explicitly designated by the template author to allow page editors to manage their content.

Provides flexibility within a templated page, allowing content editors to add unique or optional content while still adhering to the overall template structure.

A zone must be explicitly marked as "page-managed" (or a "user content zone").

If a zone is page-managed, the template author is prevented from adding any content to it, ensuring it is exclusively reserved for the page editor.

If a template is applied to a page that already contains content, all existing content on the page is automatically moved into the designated primary content zone. When you change templates, content that cannot be matched to zones in the new template (based on zone IDs) also moves to the primary zone. Read the Changing a template on a page documentation for more information.

A star icon identifies the primary content zone in the outline.

Turn off specific content types (for example, forbidding layouts or components) so the editor only sees allowed options (like text blocks).

Use the "specified" option to select individual components that page editors are allowed to use, ensuring a tailored and restrictive experience.

Hover over the eye icon to view additional component information (including its set and namespace) for accurate selection.

Smart validation prevents saving unusable zones (for example, banning all content types). The system includes intelligent validation to prevent saving configurations that make the zone unusable (for example, prohibiting saving if all content types are turned off or if required layouts are specified but not selected).

Zone IDs must be unique within a single template.

The string _main is reserved by the system and cannot be used as a zone ID.

When a template changes structure (for example, reordering columns), matching zone IDs ensure that content from the old structure is correctly remapped to the new locations. This matching process allows content to flow across templates during structural modifications or template switches, acting as a safety net for content preservation.

This feature tracks past zone IDs, acting as an alias or fallback mechanism. This guarantees content flows correctly even if template versions do not perfectly match during transitions, accommodating templates that have not been recently updated.

Determine which parts of the template will be locked down and which will be available for editing by content editors.

Design zones that match how content creators actually work.

Provide enough structure for consistency while allowing necessary flexibility for content variation.

Name zones clearly to indicate their purpose (for example, Hero Section instead of Zone 1).

Use similar naming conventions across all templates for easier management.

Consider how zone names appear to page editors when they use the template.

Use template-managed zones for brand-critical content like headers, footers, and navigation.

Use page-managed zones for content that varies between pages.

Use zone rules to prevent inappropriate content types while maintaining necessary flexibility.

Design zone IDs with future template updates in mind.

Maintain clear documentation of what each zone is intended for.

Verify that content flows correctly when templates are modified.

If zone IDs conflict within a template, the system will prevent saving until unique IDs are assigned. Use descriptive, unique names for zone IDs to avoid conflicts.

Ensure zone IDs match between template versions. Use the ID history feature to maintain backward compatibility with previous template versions.

If zone rules are configured incorrectly (for example, all content types disabled), the system validation will prevent saving. Review zone rules to ensure at least one content type is allowed.

This is expected behavior. Page-managed zones are exclusively reserved for page editor content. Empty the zone first if you need to convert it back to template-managed.

Use the zone action menu to access zone rules and modify restrictions. For zone ID issues, rename zones using descriptive, unique identifiers.

Verify that all zone IDs are unique and that ID history is properly configured. Test template updates on a copy before applying to production content.