Customizable Compose content model

Customizable Compose content model allows you to install and use Compose in your existing environment. Below the key characteristics of the customizable Compose content model are described.

Easy to get started with spaces that previously were not compatible with Compose

• Any content type can be used as a page type in Compose without changes.
• No content model migration needed to use Compose.
• No changes to frontend code needed to use Compose.
• No changes to space settings (preview, webhooks, roles) needed to use Compose.

Simplified content model

• Mark your existing content types as page types without structural changes by going through a simple UI configuration.
• Compatible with most common content model patterns for pages.
• Flexible Aggregates-based page types instead of predefined content model conventions.
• No predefined content types or naming conventions for Compose are required.
• Less nesting: All page related fields are in a single entry.
• Unique slugs per page type, rather than being defined across all pages.
• Improved access control for pages: Limit the access by page type to create an extra layer of governance based on which team or use case you provision the Compose app.
• More granular validations for linking to pages: Limit references to specific page types.

Customizable and flexible

• Future-proof: Set up to support more extensibility and integrations with the flexible Compose content model, compared to the legacy content model.
• Fully customizable page editor layout - no predefined “Content” and “Page settings” tabs.
• Compose can also be used for other use cases than web sites, such as newsletters, mobile apps, product pages.
• For new spaces: Installed page type and SEO content type is a recommendation and starting point but not a requirement to use Compose.

Functional changes in Compose

• SEO metadata: The predefined SEO content type is no longer required. Existing functionality to automatically create and name SEO entries has been removed if you use the customizable content model.
• Page editor: The required “Content” and “Page settings” tabs have been removed in favor of customizable tabs that can be changed after the initial setup.
• Linked entries can be created and edited in any tab if you use the customizable content model. With the legacy content model this was only possible in the “Content” tab.
• Page components: The “Composition relationship” validation setting is replaced by “Page component” setting for reference fields.
• Creating a page type: Because creating page types is now less involved, Compose does not offer you the capability to create them anymore. If you need a new page type, model the content type in the web app and select it as a page type in Compose afterwards.