Frequently Asked Questions
Can the page and SEO content types be extended?
It is possible to add custom fields to the "Compose: Page" and "Compose: SEO" content types. Asset and reference fields are not supported.
Which locales can be seen and edited in Compose?
When dealing with multiple locales some fields might not appear in the place you expect them to be. Make sure to read Compose localization for more on this.
How many entries are supported in one page?
Compose does not introduce new limits on linking content, so your tier limits apply.
How many levels of nesting are supported and what is recommended?
Compose does not introduce new limits on linking content, so your tier limits apply. However, complex structures can impact performance. Entries deeper than 10 levels are ignored and it's recommended to not nest your entries more than 7 levels deep within a page type.
How can changes to a page's content be detected?
How does the page publishing behaviour work?
Compose relies on the
status field of the page definition to store the aggregated status of the entries belonging to a page. If those are changed outside of Compose, the
status field can be out-of-sync until the next publishing attempt.
In addition, Compose only publishes those entries which have been displayed expanded once in the editor. Once an entry is expanded it is loaded by the app and therefore submitted upon publication.
How to link between pages?
Nested entries with "Compose: Page" content type won't be expandable in Compose page editor, but they work as any other entry reference field. When developing your application you can read their values and generate the links accordingly. Read more about Links.
How can webhooks be configured with Compose?
Do page types count against the content type limit?
Yes, page types are regular content types and are counted as such.