The RTE Color Picker Plugin for AEM

[#1]

The RTE Color Picker Plugin for AEM

  by @MukeshYadav_ 

Dear AEM Community,

I'd like to share my recently published article of a custom solution for RTE color picker plugin in AEM.

Overview

The RTE does not have OOTB color picker plugin. There are few custom solutions available over the internet, however, they often lead to the following common frustrations:

1. Time to load the dialog.
2. Multiple clicks for simple action.
3. Inconsistency with other Apps.

This blog is having two section.

In Section 1, the plugin is developed by extending the OOTB class CUI.rte.plugins.Plugin, whereas Section 2 is more about the common steps to be followed to add an available plugin to the RTE component toolbar.

You can download and install the package from the link available in blog as I have kept the plugin component inside /apps folder directly from the CRX package manager and jump to the steps mentioned in section 2.

Section 1:- Create a client library for the color picker plugin

Section 2:- Configure the color picker plugin in the RTE component

Feel free to consider customising and optimising this solution so that it suits your needs to streamline the color selection process and enhance content authoring efficiency.

Full Article

Read the full article on https://www.tothenew.com/blog/the-rte-color-picker-plugin-in-aem-a-custom-solution-for-speed-and-con... to find out more, including the complete script, step-by-step implementation guide, and other tips.

Q&A

Please use this thread to ask questions relating to this article

[#2]

Thank you for the post .you did great job

[#3]

interesting, thanks for sharing

[#4]

Interesting from UX perspective. Hope we get to see these plug-in incorporated in OOTB Text component.

[#5]

@MukeshYadav_, this is a great share. The lack of an OOTB color picker in AEM’s RTE has always felt like a small but painful gap for authors. Your approach looks clean and practical. I’m Interested, based on your testing, how have authors responded to it in terms of performance and usability compared to the typical multi-click workarounds? Always interesting to hear real feedback from the content teams.