Developing AEM Components developing-aem-components

AEM components are used to hold, format, and render the content made available on your webpages.

Code Samples code-samples

This page provides the reference documentation (or links to reference documentation) required to develop new components for AEM. See Developing AEM Components - Code Samples for some practical examples.

Structure structure

The basic structure of a component is covered on the page AEM Components - The Basics. That document covers both the touch-enabled and classic UIs. Even if you do not need to use the classic settings in your new component it can help to be aware of them when inheriting from existing components.

Extending Existing Components and Dialogs extending-existing-components-and-dialogs

Depending on the component you want to implement, it might be possible to extend or customize an existing instance, rather than defining and developing the entire structure from scratch.

When extending or customizing an existing component or dialog, you can copy or replicate either the entire structure or the structure required for the dialog before making your changes.

Extending an Existing Component extending-an-existing-component

Extending an existing component can be achieved with Resource Type Hierarchy and the related inheritance mechanisms.

Customizing a Existing Component Dialog customizing-a-existing-component-dialog

It is also possible to override a component dialog using the Sling Resource Merger and defining the property sling:resourceSuperType.

This means you only need to redefine the required differences, as opposed to redefining the entire dialog (using sling:resourceSuperType). This is now recommended method for extending a component dialog

See the Sling Resource Merger for more details.

Defining the Markup defining-the-markup

Your component will be rendered with HTML. Your component needs to define the HTML needed to take the required content and then render it as required, on both the author and publish environments.

Using the HTML Template Language using-the-html-template-language

The HTML Templating Language (HTL), introduced with AEM 6.0, takes the place of JSP (JavaServer Pages) as the preferred and recommended server-side template system for HTML. For web developers who need to build robust enterprise websites, HTL helps to achieve increased security and development efficiency.

Developing the Content Logic developing-the-content-logic

This optional logic selects and/or computes the content to be rendered. It is invoked from HTL expressions with the appropriate Use-API pattern.

The mechanism to separate logic from appearance helps clarify what is called for a given view. It also allows differing logic for different views of the same resource.

Using Java using-java

The HTL Java Use-API enables a HTL file to access helper methods in a custom Java class. This lets you use Java code to implement the logic for selecting and configuring the component content.

Using JavaScript using-javascript

The HTL JavaScript Use-API enables a HTL file to access helper code written in JavaScript. This lets you use JavaScript code to implement the logic for selecting and configuring the component content.

Using Client-Side HTML Libraries using-client-side-html-libraries

Modern websites rely heavily on client-side processing driven by complex JavaScript and CSS code. Organizing and optimizing the serving of this code can be a complicated issue.

To help deal with this issue, AEM provides Client-side Library Folders, which let you store your client-side code in the repository, organize it into categories and define when and how each category of code is to be served to the client. The client-side library system then takes care of producing the correct links in your final web page to load the correct code.

Read Using Client-Side HTML Libraries for more information.

Configuring the Edit Behavior configuring-the-edit-behavior

You can configure the edit behavior of a component including attributes such as actions available for the component, characteristics of the inplace editor, and the listeners related to events on the component. The configuration is common to both the touch-enabled and classic UI, albeit with certain, specific differences.

The edit behavior of a component is configured by adding a cq:editConfig node of type cq:EditConfig below the component node (of type cq:Component) and by adding specific properties and child nodes.

Configuring the Preview Behavior configuring-the-preview-behavior

The WCM Mode cookie is set when switching to Preview mode even when the page is not refreshed.

For components with a rendering that are sensitive to the WCM Mode, they need to be defined to refresh themselves specifically, then rely on the value of the cookie.

Creating and Configuring a Dialog creating-and-configuring-a-dialog

Dialogs are used to allow author to interact with the component. Using a dialog allows authors and/or administrators to edit content, configure the component or define design parameters (using a Design Dialog)

Coral UI and Granite UI coral-ui-and-granite-ui

Coral UI and Granite UI define the modern look and feel of AEM.

Granite UI provides a large range of the basic components (widgets) needed to create your dialog on the authoring environment. When necessary you can extend this selection and create your own widget.

For full details see:

Creating a New Dialog creating-a-new-dialog

Dialogs for the touch-enabled UI:

An example node structure might be:

newComponent (cq:Component)
  cq:dialog (nt:unstructured)
    content
      layout
      items
        column
          items
            file
            description

Customizing a dialog is similar to developing a component as the dialog is itself a component (that is, markup rendered by a component script together with behavior/style provided by a client library).

For examples, see:

Customizing Dialog Fields customizing-dialog-fields

Creating a New Field creating-a-new-field

Widgets for the touch-enabled UI are implemented as Granite UI components.

To create a widget for use in a component dialog box for the touch-enabled UI requires you to create a Granite UI field component.

If you consider your dialog as a simple container for a form element, then you can also see the primary content of your dialog content as form fields. Creating a form field requires you to create a resource type; this is equivalent to creating a component. To help you in that task, Granite UI offers a generic field component to inherit from (using sling:resourceSuperType):

/libs/granite/ui/components/coral/foundation/form/field

More specifically Granite UI provides a range of field components that are suitable for use in dialogs (or, more generally speaking, in forms).

Once you have created your resource type, you can instantiate your field by adding a new node in your dialog, with the property sling:resourceType referring to the resource type you have just introduced.

Creating a Client Library for Style and Behavior creating-a-client-library-for-style-and-behavior

If you want to define styling and behavior for your component, you can create a dedicated client library that defines your custom CSS/LESS and JS.

To have your client library loaded solely for your component dialog (that is, it will not be loaded for another component) you need to set the property extraClientlibs of your dialog to the category name of the client library you have created. This is advisable if your client library is quite large and/or your field is specific to that dialog and will not be needed in other dialogs.

To have your client library loaded for all dialogs, set the category property of your client library to cq.authoring.dialog. This is the category name of the client library that is included by default when rendering all dialogs. You want to do that if you client library is small and/or your field is generic and could be reused in other dialogs.

For an example, see:

Extending (Inheriting from) a Field extending-inheriting-from-a-field

Depending on your requirements, you can either:

Access to Dialog Fields access-to-dialog-fields

You can also use render conditions ( rendercondition) to control who has access to specific tabs/fields in your dialog; for example:

+ mybutton
  - sling:resourceType = granite/ui/components/coral/foundation/button
  + rendercondition
    - sling:resourceType = myapp/components/renderconditions/group
    - groups = ["administrators"]

Handling Field Events handling-field-events

The method of handling events on dialog fields is now done with listeners in a custom client library. This is a change from the older method of having listeners in the content structure.

Listeners in a Custom Client Library listeners-in-a-custom-client-library

To inject logic into your field, you should:

To achieve this you need to know about the underlying widget library with which you want to interact. See the Coral UI documentation to identify to which event you want to react. This is very similar to the process that you had to perform with ExtJS in the past: find the documentation page of a given widget, then check the details of its event API.

For an example, see:

Listeners in the Content Structure listeners-in-the-content-structure

In the classic UI with ExtJS, it was usual to have listeners for a given widget in the content structure. Achieving the same in the touch-enabled UI is different as JS listener code (or any code at all) is no longer defined in the content.

The content structure describes the semantic structure; it should (must) not imply the nature of the underlying widget. By not having JS code in the content structure, you can change the implementation details without having to change the content structure. In other words, you can change the widget library without needing to touch the content structure.

Detecting Availability of the Dialog dialog-ready

If you have a custom JavaScript that needs to be executed only when the dialog is available and ready, you should listen for the dialog-ready event.

This event is triggered whenever the dialog loads (or re-loads) and is ready for use, which means whenever there is a change (create/update) in the DOM of the dialog.

dialog-ready can be used to hook in JavaScript custom code that performs customizations on the fields inside a dialog or similar tasks.

Field Validation field-validation

Mandatory Field mandatory-field

To mark a given field as mandatory set the following property on the content node of your field:

For an example, see:

/libs/foundation/components/page/cq:dialog/content/items/tabs/items/basic/items/column/items/title/items/title

Field Validation (Granite UI) field-validation-granite-ui

Field validation in Granite UI and the Granite UI Components (equivalent to widgets), is done by using the foundation-validation API. See the foundation-valdiation Granite documentation for details.

For examples, see:

Creating and Configuring a Design Dialog creating-and-configuring-a-design-dialog

The Design dialog is provided when a component has design details that can be edited in Design Mode.

The definition is very similar to that of a dialog used for editing content, with the difference that it is defined as a node:

Creating and Configuring an Inplace Editor creating-and-configuring-an-inplace-editor

An inplace editor allows the user to edit content directly in the paragraph flow, without the need to open a dialog. For example, the standard Text and Title components both have an inplace editor.

An inplace editor is not necessary/meaningful for every component type.

See Extending Page Authoring - Add New Inplace Editor for more information.

Customizing the Component Toolbar customizing-the-component-toolbar

The Component Toolbar gives the user access to a range of actions for the component such as edit, configure, copy, and delete.

See Extending Page Authoring - Add New Action to a Component Toolbar for more information.

Configuring a Component for the References Rail (Borrowed/Lent) configuring-a-component-for-the-references-rail-borrowed-lent

If your new component references content from other pages then you can consider whether you want it to impact the Borrowed Content and Lent Content sections of the References Rail.

Out-of-the-box AEM only checks the Reference component. To add your component you need to configure the OSGi bundle WCM Authoring Content Reference Configuration.

Create a entry in the definition, specifying your component, together with the property to be checked. For example:

/apps/<*your-Project*>/components/reference@parentPath

Enabling and Adding Your Component to the Paragraph System enabling-and-adding-your-component-to-the-paragraph-system

After the component has been developed it needs to be enabled for use in an appropriate paragraph system, so it can be used on the required pages.

This can be done by either:

Configuring a Paragraph System so that Dragging an Asset Creates a Component Instance configuring-a-paragraph-system-so-that-dragging-an-asset-creates-a-component-instance

AEM offers the possibility to configure a paragraph system on your page so that an instance of your new component is automatically created when a user drags an (appropriate) asset onto an instance of that page (instead of always having to drag an empty component to the page).

This behavior, and the required asset-to-component relationship can be configured:

For examples see:

CODE ON GITHUB

You can find the code of this page on GitHub

Using the AEM Brackets Extension using-the-aem-brackets-extension

The AEM Brackets Extension provides a smooth workflow to edit AEM components and client libraries. It is based on the Brackets code editor.

The extension:

Migrating from a Classic Component migrating-from-a-classic-component

When migrating a component that was designed for use with the classic UI to a component that can be used with the touch-enabled UI (either solely or jointly) the following issues should be considered:

Migrating cq:listener Code migrating-cq-listener-code

If you are migrating a project that was designed for the classic UI, then the cq:listener code (and component related clientlibs) might use functions that are specific to the classic UI (such as CQ.wcm.*). For the migration you must update such code using the equivalent objects/functions in the touch-enabled UI.

If your project is being completely migrated to the touch-enabled UI you need to replace such code to use the objects and functions relevant to the touch-enabled UI.

However, if your project must cater for both the classic UI and the touch-enabled UI during the migration period (the usual scenario), then you must implement a switch to differentiate the separate code referencing the appropriate objects.

This switch mechanism can be implemented as:

if (Granite.author) {
    // touch UI
} else {
    // classic UI
}

Documenting Your Component documenting-your-component

As a developer, you want easy access to component documentation so that you can quickly understand:

For this reason, it is easy to make any existing documentation markdown you have available within the component itself.

Place a README.md file in the component structure. This markdown is displayed in the component console.

The supported markdown is the same as that for content fragments.