Good to have this feature.

@TH0MA5  This is a good idea, probably I can try implementing this as PoC.   furthermore , the option can be added to user preference

Hi @snehR  Could you please check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/is-there-a-way-to-to-add-reusable-parts-of-dialog-under/td-p/387249#M83739 if it somehow covers this use case?

Hi @Alexander_Prikhodko  Could you please check if below code fulfill your requirement? if (CQ && CQ.I18n) { CQ.I18n.setLocale("de_DE"); var localizedMessage = CQ.I18n.getMessage("Go"); console.log(localizedMessage) }  

The rollout configsActivate on Blueprint and decativate on Blueprint also allowed you to publish/unpublish live copy as soon as blueprint is published.

Hi @prashantonkar  we had this kind of implementation with another CMS product, where we were loading clientlibs based on component from UI but we used to load those clienlibs(only JS, CSS does not have much impact on performance) as separate request for each/unique component and the reason was - 1....

Hi, Could you please try to give user below rights as well and then check jcr:removeNode jcr:removeChildNodes  

Hi @Alexander_Prikhodko For the second approach, I think you already have a solution that can be implemented without delivering features from Adobe.   As you mentioned, you can simply create a workflow 'Create Version'. with create Version Step and start a workflow from page information.     But fo...

Request for Feature Enhancement (RFE) Summary: Use-case:Allow images for field description e.g. https://aemlab.blogspot.com/2021/05/aem-touch-ui-component-dialog-fielddescription-image.htmlCurrent/Experienced Behavior:Rich Text gets encoded and does not render HTMLImproved/Expected Behavior:Rich Tex...

It is possible to add any type of granite resources in the metadata schema as well for Touch UI. e.g. dropdown, RTE, etc. You are referring to classic UI, which I highly doubted would be extended.