Repository files navigation

Set of standardized Web Content Management (WCM) components forAdobe Experience Manager (AEM) to speed up development time and reduce maintenance cost of your websites.

• Contributions are welcome, read ourcontributing guide for more information.
• Ideas and questions are discussed on ourpublic mailing list; you can alsosubscribe via email.

• Component Library: A collection of examples to view the components in their various configurations.
• Component Documentation: For developers and authors, with details about each component.
• Get Started:
  • WKND Tutorial: A two-day tutorial for building a new site.
  • Summit Tutorial: A two-hour tutorial for building a new site (from a Lab at US Summit 2019).
  • Gems Webinar: A guided tour of the Core Components (recorded on Dec 2018).

• Production-Ready: 29 robust components that are well tested, widely used, and that perform well.
• Cloud-Ready: Whether onAEM as a Cloud Service, onAdobe Managed Services, or on-premise, they just work.
• Versatile: The components represent generic concepts with which the authors can assemble nearly any layout.
• Configurable: Template-levelcontent policies define which features the page authors are allowed to use or not.
• Trackable: TheAdobe Client Data Layer and Google Data Layer integrations support the tracking of all aspects of the visitor experience.
• Accessible: They complyWCAG 2.1 standard, provide ARIA labels, and support keyboard navigation.
• SEO-Friendly: The HTML output is semantic and provides schema.org microdata annotations.
• WebApp-Ready: Thestreamlined JSON output allows client-side rendering, still with a possibility ofin-context editing.
• Design Kit: AUI kit for Adobe XD allows designers to create wireframes that they can thenstyle as needed.
• Themeable: The components implement theStyle System, and the markup followsBEM CSS conventions.
• Customizable: Several patterns alloweasy customization, from adjusting the HTML to advanced functionality reuse.
• Versioned: Theversioning policy ensures we won't break your site when improving things that might impact you.
• Open Sourced: If something is not as it should,contribute your improvements!

1. Page
2. Navigation
3. Language Navigation
4. Breadcrumb
5. Quick Search
6. Table of Contents

6. Title
7. Text
8. Image
9. Button
10. Teaser
11. List
12. Download
13. PDF Viewer
14. Embed
15. Sharing
16. Progress Bar
17. Separator
18. Experience Fragment
19. Content Fragment
20. Content Fragment List

21. Container
22. Carousel
23. Tabs
24. Accordion

25. Core Form container
26. Form text field
27. Form options field
28. Form hidden field
29. Form button

To learn about the main upcoming components and features, visit theroadmap wiki page.

To include the Core Components in a new project, we strongly advise to use theAEM Project Archetype; this guarantees a starting point that complies to all recommended practices from Adobe.

For existing projects, take example from theAEM Project Archetype by looking at thecore.wcm.components references in the mainpom.xml, inall/pom.xml, and inui.apps/pom.xml. For the rest, make sure to create Proxy Components, to load the client libraries and to allow the components on the template, as instructed inUsing Core Components.

For the requirements from previous Core Component releases, seeHistorical System Requirements.

The Core Components require the use ofeditable templates and do not support Classic UI nor static templates. If needed, check out theAEM Modernization Tools.

Setup your local development environment forAEM as a Cloud Service SDK or forolder versions of AEM.

To compile your own version of the Core Components, you can build and install everything on your running AEM instance by issuing the following command in the top level folder of the project:

mvn clean install -PautoInstallPackage

You can also install individual packages/bundles by issuing the following command in the top-level folder of the project:

mvn clean install -PautoInstallPackage -pl <project_name(s)> -am

With AEM as a Cloud Service SDK, use thecloud profile as follows to deploy the components into/libs instead of/apps:

mvn clean install -PautoInstallPackage,cloud

Note that:

• -pl/-projects option specifies the list of projects that you want to install
• -am/-also-make option specifies the dependencies that should also be built

For detailed informations seeBUILDING.md.

The Core Components leverage both OSGi configurations and Sling context-aware configurations. For a description of defined configurations seeCONFIGS.md

• The provided oEmbed URL Processor configuration for Facebook and Instagram is not working at the moment as a new version of the endpoint was released by Facebook and now an access token needs to be passed in the request. A possible workaround is described in#1225