How to Write AEM Reusable Touch UI, Granite UI Configuration

Why are we repeating ourselves, writing the same Touch UI (Granite UI Component) configuration again and again as developers? It’s been like the 10th time that we have created a Granite UI Component configuration, an identical block of code. The RTE Granite UI Component should only contain basic format options. Is there a way for developers to write this configuration once, so it can be reused? The answer is yes.

Introducing the DRY way of using RichText Granite UI Component in AEM for Static Templates, which is an article for how developers can write better and reusable code for Touch UI (Granite UI) configuration.

The blog article specifically focuses on the Rich Text Granite UI Component, configuration once, and then reuse it over and over again. The same methodology can be applied to all other Granite UI Component configurations; checkbox, select, color picker, text, etc… This is great because if there is a requirement, for example, to add in a new styles option, you can make the change once, and all other Granite UI Component configurations will pick this change up.

Visit the DRY way of using RichText Granite UI Component in AEM for Static Templates

Hello, I am an enthusiastic Adobe Community Advisor and a seasoned Lead AEM Developer. I am currently serving as an AEM Technical Lead at, bringing over a decade of extensive web engineering experience and more than eight years of practical AEM experience to the table. My goal is to give back to the AEM Full Stack Development community by sharing my wealth of knowledge with others. You can connect with me on LinkedIn.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top