A developer plans to use the Text component on its pages. However the out of the box Text component does not allow authors to edit HTML source on the component.
How should the developer support HTML source editing?
A.
Edit the OOTB Text component directly to enable sourceedit RTE Plugin
B.
Create a standalone custom Text component and handle HTML source in Sightly
C.
Create a new clientlib to programmatically handle HTML source in authoring
D.
Extend the OOTB Text component and enable the sourceedit RTE plugin
To support HTML source editing in the Text component, the best approach is to extend the out-of-the-box (OOTB) Text component and enable the sourceedit RTE (Rich Text Editor) plugin:
Extend the OOTB Text Component:
Create a custom Text component that inherits from the OOTB Text component.
Enable the sourceedit RTE Plugin:
Modify the component's dialog definition to include the sourceedit plugin in the RTE configuration.
Ensure the plugin is properly configured to allow HTML source editing.
References:
AEM documentation on extending core components.
Guides on configuring the RTE in AEM to enable additional plugins.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit