Core Components Introduction
In Adobe Experience Manager, components are the structural elements that constitute the content of the pages being authored. Components have always been a fundamental element of the AEM experience, making page creation simple but powerful for the author and the development of components flexible and extensible for the developer.
Core Components were introduced to provide robust and extensible base components, built on the latest technology and best practices, and adhering to accessibility guidelines and are compliant with the WCAG 2.0 AA standard. Core components make page authoring more flexible and customizable, and extending them to offer custom functionality is simple for the developer.
Try Out the Core Components
If you want to get started straight away trying out the Core Components, head over to the Component Library . The Component Library is an online showcase of the current version of most of the Core Components, allowing you to interact with variations of the components as well as see sample HTML and JSON output.
The We.Retail reference site also illustrates how the core components can be used.
Core Components - Core Features
The Core Components are:
Templates can define how the page authors can use them.
Authors can create most kind of content with them.
Authors can efficiently create and manage content with them.
Usable out-of-the-box! They are robust, well-tested, and perform well.
They comply WCAG 2.0 standard, provide ARIA labels, and support keyboard navigation.
Easy to Style
The components implement the Style System and the markup follows BEM CSS naming.
The HTML output is semantic and provides schema.org microdata annotations.
Their streamlined JSON output can also be used for client-side rendering.
To cover custom needs but without starting from scratch, everything can be extended.
If something is not as it should be, contribute improvements on GitHub (Apache License).
The core components won’t break your site when improving things that might impact you.
Smart reference resoltuion allows certain components to find and render corresponding localized content automatically
The current version of the Core Components features the following components.
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 or in design mode .
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.
When to Use Core Components
As the Core Components are all-new, and offer multiple benefits, it is recommended for new AEM projects to use them. For existing projects, a migration should be part of a larger project effort, for example a rebranding or overall refactoring.
Gems Session Overview
For an introduction to the Core Components, the features they offer, and how they are leveraged in AEM, check out the AEM Gems Session AEM Core Components.
Gems on Adobe Experience Manager is a series of technical deep dives delivered by Adobe experts. This series complements the product documentation and of all the other technical channels, allowing developers to get in touch and go deep on a specific topic.
Developing with the Core Components
The Core Components provide robust and extensible base components that implement several patterns that allow easy customization, from simple styling to advanced functionality reuse. See the Core Components developing documentation for more information.
Get started developing AEM Sites with Core Components by following this step by step tutorial.
Don't forget to start your own AEM project leveraging the AEM Project Archetype with the latest Core Components built in!
Core Components Support
Core Components are an integral part of AEM and supported as is, under the same terms and conditions as if they were delivered as part of the Quickstart.
Like other product features, the general rule of end-of-life is:
- Components are first announced to be deprecated before being removed
- At the earliest they are then removed from the AEM release following the announcement.
This gives customers at least one release cycle to move to the new version of the component, before support ends.
The version of each component clearly states the AEM versions that it supports. When support ceases for a version of AEM, then so does the support of the Core Components for that version of AEM.
For details about the support of component customizations, see the Customizing Core Components page of the relevant Core Components Version.
Foundation Component Support
Since the Foundation Components have served as a basis of so much project development over many versions, they will continue to be supported into the foreseeable future.
However, Adobe's development emphasis has shifted to the Core Components and new features will be added to them, whereas nearly all Foundation Components have been deprecated with AEM 6.5 and only bug fixes will be made to the Foundation Components going forward.