Skip to content

Latest commit

 

History

History
38 lines (28 loc) · 4.85 KB

CONFIGS.md

File metadata and controls

38 lines (28 loc) · 4.85 KB

Configurations for AEM WCM Core Components

OSGi Configurations

AEM uses OSGi configurations to drive how its internals work and WCM Core Components leverage the following:

General Configurations:

Configuration Description
ComponentConfigImpl Enables Content Fragment management for Content Fragment component. Reference documentation: https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/content-fragments-config-components-rendering.html
RTEFilterServletFactory Enables usage of RTE (Rich Text Editor) with Text component. Reference documentation: https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/rich-text-editor.html
OEmbedClientImplConfigurationFactory Enables out-of-the-box OEmbed configurations for several services, with Embed component
AdaptiveImageServletMappingConfigurationFactory Enables adaptive image support for Image component
MailServlet Enables email support for user-submitted information in Core Form container
ServiceUserMapperImpl Enables access rights for ClientLibraries and ComponentFiles helpers

author Configurations

Configuration Description
FormParagraphPostProcessor Enables functionality of Core Form container
MobileEmulatorProvider Enables mobile devices emulation in the editor for Page component

Context-Aware configurations

The following context-aware configurations are defined by the AEM WCM Core Components:

Configuration Description
HtmlPageItemsConfig Holds information on items to be included by Page component: scripts, links, meta elements
PdfViewerCaConfig Holds configuration for PDF Viewer component
DataLayerConfig Toggles and configures the Adobe Client Data Layer and Google Data Layer integrations

At the moment, there is no editing UI for context-aware configuration available out-of-the-box. Developers can either:

  • Deploy predefined context-ware configurations via content packages.
  • Change context-aware configurations using SlingPostServlet or CRXDE Lite.
  • Use the wcm.io context-aware configuration editor. An example setup is included with the Core Components Library example content (see adobe#1410)