This page provides an overview of Adobe Experience Manager (AEM) components; for example, the components used for page authoring. The following pages provide more detailed information about developing these (and other) components:
- AEM Components - the Basics
- Touch-Optimized UI
- Classic UI
- Internationalizing Components
- Developing Forms
- Using Components as Boilerplates
- Obtaining Page Information in JSON Format
- Exploring Sling
- are modular units which realize specific functionality to present your content on your website.
- are re-usable.
- are developed as self-contained units within one folder of the repository.
- have no hidden configuration files.
- can contain other components.
- can run anywhere within any AEM system. They can also be limited to run under specific components.
- have a standardized user interface.
- have an edit behaviour that can be configured.
- can be made available for either the touch-optimized UI, the classic UI or both.
- use dialogs that are built using sub-elements, these are: Granite UI components for the touch-optimized UI and widgets, implemented with ExtJS, for the classic UI.
- can be developed using HTL (recommended) or JSP.
- can be developed to create customized components that extend the default functionality.
As components are modular, you can:
- develop a new component on your local instance,
- deploy this to your test environment,
- deploy it to your live authoring environment
(where they allow authors and/or administrators to add and configure content)
- and then deploy it to your live publish environment(s)
(here they are used to render content for visitors to your website; certain components, for example for Communities, also accept input from your users).
Each AEM component:
- is a resource type
- is a collection of scripts that completely realize a specific function
- can function in isolation; this means either within AEM or a portal
AEM comes with a variety of out-of-the-box components that provide comprehensive functionality; these include:
- Paragraph System (parsys)
- Layout Container (responsivegrid - touch-optimized UI only)
- Image, with accompanying text
Some components, for example Text, are provided in two versions - JSP and HTL.
The components provided and their usage within the sample websites provided (e.g. Geometrixx, Geometrixx Outdoors) illustrate how to implement and use components. The components are provided with all source code and can be used as is or as starting points for modified or extended components.
To get a list of all the components available in the repository, proceed as follows:
- In CRXDE Lite, select Tools from the toolbar, then Query; the Query tab will be opened.
- As Type, select XPath.
- In the Query input field, enter following string:
- Click Execute. The list is displayed.