Acquia Source has the following fundamental types of content:
Pages
CMS content
Pages are built using the Experience Builder user interface. They are primarily used to create visual content that is intended to be displayed in a browser. For instance, a typical “Landing Page” should be built as a Page. For instruction on how to create a page, visit Using Experience Builder.
CMS content is intended to be reusable across multiple channels, contexts, and pages. For example, you can create a Press Release CMS content, which can be embedded on a page, accessed through an API, and displayed in a list of Press Releases. It would have a predefined structure such as Title, Byline, Post Date, and Thumbnail Image. For more information on fields, visit Fields.
CMS content enables you to maintain consistency in your content structure, repurpose content for different experiences, and scale your content operations efficiently.
Currently, CMS content can only be displayed on the frontend using Experience Builder’s List component. It can also be accessed through API. In future, Acquia Source will offer an option to create templates for CMS content using Experience Builder, enabling it to be directly accessed by end users.
The following table provides a comparison between pages and CMS content based on different criteria:
| Criteria | Pages | CMS content |
|---|---|---|
Focus | Visual presentation | Reusable content |
Reusability | Low because it is typically unique for every page | High because it can be used in multiple places and accessed through API |
Flexibility | High | Low |
Management | Layout-centric | Data-centric |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Thu Aug 07 2025 14:57:24 GMT+0000 (Coordinated Universal Time)