Author with Core Components
In Adobe Experience Manager, components are the structural elements that constitute the content of the pages being authored. This section covers the Core Components, which provide essential content types to create pages.
The Core Components offer flexible and feature-rich authoring functionality. The We.Retail reference site illustrates how the core components can be used.
To experience the Core Components and see examples of their configuration options as well as HTML and JSON output, visit the Component Library .
Core Components are not immediately available to authors, the development team must first integrate them to your environment . Once integrated, they may be made available and pre-configured via the template editor .
Authoring with Core Components
As an author, you will notice several advantages of the Core Components, including:
- Simple to use and well-integrated with the page editor
- Built around accessibility guidelines
- Built to support responsive layout
Components are available on the Components tab of the side panel of the page editor when editing a page .
Components are grouped according to categories called component groups to easily organize and filter the components. The component group name is displayed with the component in the component browser and it is also possible to filter by group to easily find the right component.
The Core Components are by default part of a hidden group and are not visible within the component browser.
Add the required components to a visible group or customize them for them to be available for authors.
Pre-Configuring Core Components
Configuring Foundation Components was the job of a developer. However with Core Components, a template author can now configure a number of capabilities via the template editor.
For example if an image component should not allow image upload from the file system, or if a text component should only allow certain paragraph formatting, these features can be enabled or disabled with a simple click.
See Creating Page Templates for more information.
Edit and Design Dialogs
Because the Core Components can be pre-configured by template authors to define what options are allowed as part of a template, and then further configured by the page author to define actual page content, each component can have options in two different dialogs.
What it Controls
Options that a page author can modify during normal page editing for the placed components
The content displayed by the component and how it will ultimately appear on the page.
Formatting of content text, rotate an image on a page
Options that a template author can modify when configuring a page template.
What options the page author has available when editing the component
Which text formatting options are available, which image in-place options are available
The styles of most Core Components can be defined using the AEM style system.
- A template author can define which styles are available for a particular component in the Design Dialog of that component.
- The content author can then choose which styles to apply when adding the component and creating content.
For further details see the Style System documentation.
In AEM 6.3, service pack 2 (18.104.22.168) or newer is required to enable the style system feature.
List of Core Components Available
The following is a list of the available Core Components linked to pages describing their edit and design dialog capabilities in detail.
The current version of the Core Components features the following components.
Some versions of individual Core Components may only be compatible with certain versions of AEM.
See the individual help page (linked to in the previous list) for the specific component for compatibility information or reference the Core Components Versions document for more information.
Depending on your instance you may have customized components developed explicitly for your requirements. These may even have the same name as some of the components discussed here. The form core components are not related to AEM Forms.
See the Developing Core Components developer documentation for technical information regarding core components.