Email Page Component email-page-component
The Email 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, tailored for creating ÃÛ¶¹ÊÓƵ Campaign content.
Usage usage
The Email Page Component forms the basis of all pages designed with the Email Core Components and editable templates. By using the Email Page Component, headers, footers, and the structure of the page can be defined as a template using the other Email Core Components.
- Using the design dialog, custom client-side libraries can be defined for the page.
- Unlike other components which have an edit dialog accessible directly from the component, because the Email Page Component is the page itself, the edit dialog of the Email Page Component is the page properties window.
Version and Compatibility version-and-compatibility
The current version of the Email Page Component is v1, which was introduced with release X of the Email Core Components in October 2022, 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 Email Core Component versions and releases, see the document Email Core Components Versions
Technical Details technical-details
The latest technical documentation about the Page Component
Further details about developing Core Components can be found in the Core Components developer documentation.
Edit Dialog edit-dialog
Because the component represents the entire page, settings that would normally be in an edit dialog are found in the Page Properties window.
Cloud Services Tab cloud-services
In order for the Email Core Components to be able to retrieve campaign variables and data, the page must be linked to an ÃÛ¶¹ÊÓƵ Campaign configuration.
Under Cloud Service Configuration heading, in the drop-down select Add Configuration.
Under ÃÛ¶¹ÊÓƵ Campaign heading, select the configuration for your integration with ÃÛ¶¹ÊÓƵ Campaign.
See the document Using Email Core Components for more information about setting up the Email Core Components.
Email Tab email-tab
The Email tab defines properties of emails sent via ÃÛ¶¹ÊÓƵ Campaign based on the content of this page such as the email subject and plain text content.
- Subject - The subject of the email sent by ÃÛ¶¹ÊÓƵ Campaign based on this page
- Click the Select ÃÛ¶¹ÊÓƵ Campaign Variable icon to open the Select ÃÛ¶¹ÊÓƵ Campaign Variable dialog to insert dynamic content from ÃÛ¶¹ÊÓƵ Campaign.
- Pre-header
- Click the Select ÃÛ¶¹ÊÓƵ Campaign Variable icon to open the Select ÃÛ¶¹ÊÓƵ Campaign Variable dialog to insert dynamic content from ÃÛ¶¹ÊÓƵ Campaign.
- Plain text - The plain text version of the email sent by ÃÛ¶¹ÊÓƵ Campaign
- Click the Select ÃÛ¶¹ÊÓƵ Campaign Variable icon to open the Select ÃÛ¶¹ÊÓƵ Campaign Variable dialog to insert dynamic content from ÃÛ¶¹ÊÓƵ Campaign.
- Reference Url
Design Dialog design-dialog
Because the component represents the entire page, the design dialog is accessed via Page Information -> Page Policy when editing the page template.
Properties Tab properties-tab
Using the Page Design window, you can define the client libraries to be loaded as well as the web resources library for the page.
-
Client Libraries - This defines the client library categories to load. JavaScript is added at the body end and the CSS is added to the page head.
-
Client Libraries JavaScript Page Head - This defines the JavaScript client library categories to load in the page head.
- Categories defined here that are also present in the Client Libraries field will have JavaScript loaded in the page head instead of at body end.
- No CSS will be loaded unless the category is also present in the Client Libraries field.
-
Load JavaScript Libraries asynchronously - If enabled, the custom JavaScript libraries will be loaded asynchronously.
-
Web Resources Client Library - The client library category that is used to serve web resources such as favicons.
-
Skip to main content element selector - Used as an accessibility feature to skip directly to the main content of the page
Libraries can be configured for both the Client Libraries and Client Libraries JavaScript Page Head fields as follows:
- 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