The Page Component is an extensible page component designed to work with the template editor and allows page header/footer and structure components to be assembled with the template editor.
The page component forms the basis of all pages designed with the core components as well as editable templates. By using the page component, headers, footers, and the structure of the page can be defined as a template using the other core components.
Version and Compatibility
The current version of the Page Component is v2, which was introduced with release 2.0.0 of the Core Components in January 2018, and is described in this document.
The following table details all supported versions of the component, the AEM versions with which the versions of the component is compatible, and links to documentation for previous versions.
For more information about Core Component versions and releases, see the document Core Components Versions.
To enable redirect at cq:Page level for verison 2 of the page component and AEM 6.3, service pack 2 or later is required. Such redirection was not available in prior releases.
Because the component represents the entire page, settings that would normally be in an edit dialog are found in the Page Properties window.
Because the component represents the entire page, the design dialog is accessed via Page Information -> Page Policy when editing the page template.
In previous versions of AEM, Page Policy was called Page Design.
Using the Page Design window, you can define the client libraries to be loaded as well as the web resources library for the page.
- No CSS will be loaded unless the category is also present in the Client Libraries field.
- Web Resources Client Library The client library category that is used to serve web resources such as favicons.
- To add a new field click or tap the Add button below the fields.
- To remove a field click or tap the trash can icon next to the field to be removed.
- To rearrange the load order, click or tap and drag the handle next to the field to be moved.
For more information about using client-side libraries see Using Client Side Libraries.
The ability to separately define client libraries for the page head was introduced with core components release 2.2.0.
The Page Component supports the AEM Style System.