Acrolinx for AEM supports DITA and XML document formats in both the on-premise version of AEM and AEMaaCS. This includes the DITA document types: concept, reference, task, topic.
The following features are available in Acrolinx for AEM:
|
Feature |
AEM On-Premise |
AEMaaCS |
|---|---|---|
|
Sites - Sidebar |
|
|
|
Sites - Batch Check |
|
|
|
Content Fragments - Sidebar |
|
|
|
Guides - Sidebar |
|
|
|
Guides - Batch Check |
|
|
Acrolinx for AEM can check content in AEM’s Core Components. Acrolinx highlights and replaces text in Core Components as long as the text is visible to the human eye.
If text in a Core Component is in editableProperties, Acrolinx will check the content but can’t highlight or replace it. When an Editable has text and the component supports changes via the granite api, Acrolinx for AEM can highlight and replace.
You can configure which components you want Acrolinx to check in your Content Profile.
By default, Acrolinx checks the following components:
-
Text
-
Title
-
Table
Acrolinx and AEM Custom Components
Acrolinx doesn’t specifically support highlight and replace for AEM custom components. There are two cases where Acrolinx treats AEM components as custom components:
-
A component is outside of AEM’s Core Components list
-
You modify a Core Component property
Acrolinx extracts text from nearly all custom components, but there can be issues with highlight and replace.
Example
Say you change the name of the expandedItems property to something like openItems. In this case, Acrolinx wouldn't recognize openItems and couldn't highlight or replace.
Notice
To avoid issues with highlighting and replacement, be sure to add custom components to your AEM Content Profile. Learn how in the Configure Components section of our AEM admin guide.