The Rich Text Editor (RTE) is a basic building block for inserting textual content into AEM. It forms the basis of various components, including:
Copying nested lists into the RTE does not work as expected. When copying nested lists from Microsoft Word, you will need to manually clean up the lists after pasting the text in the RTE.
Selecting a text-based component with a single tap or click will reveal the component toolbar as with any component.
Tapping/clicking agin or initially selecting the component with a slow double-tap/click will open in-place editing, which has its own toolbar. Here you can edit the content and make basic formatting changes.
This toolbar provides the following options:
This allows you to set Bold, Italic and Underline.
With this you can create bulleted or numbered lists, or set the indentation.
For text-based components, selecting the full screen mode from the toolbar will open the rich text editor and hide the rest of the page content.
Fullscreen mode will show all options of your rich text editor, which can vary depending on the configuration.
Additional rich text editor options include:
Create an anchor in the text that you can later link to/reference.
- Align Text Left
- Cetner Text
- Align Text Right
On a page, you can either include Coral 2 RTE clientlib or the Coral 3 RTE clientlib. By default, Rich Text Editor includes the Coral 3 RTE clientlib.
Custom plugins for Coral 2 RTE should work with Coral 3 RTE as long as they do not depend on RTE internals (for example, classes and so on).
However, if you want to switch to Coral 2 RTE, perform the following steps:
At the node /libs/cq/gui/components/authoring/editors/clientlibs/core, do the following:
- Replace rte.coralui3 with rte.coralui2 for the dependencies property.
- Replace cq.authoring.editor.core.inlineediting.rte.coralui3 with cq.authoring.editor.core.inlineediting.rte.coralui2 for the embed property.
- Replace cq.authoring.rte.coralui3 with cq.authoring.rte.coralui2 for the embed property.
Coral 2 RTE uses handlebars templates for plugin dialogs. Therefore, the Coral 2 RTE clientlib had a dependency on the handlebars clientlib. Coral 3 RTE does not use handlebars templates and , therefore, doesn't have any associated dependency. If your custom plugins use handlebars templates, include the handlebars clientlib in your web page.