Hi, can I just ask why you would want to do this?In any case, here is the answer:Removing all editor headersJaideepBrar​'s answer could work but if overlay these files you will be affecting all editors (for AEM Sites pages, but also in the template editor for example). If this is your aim, then the ...

Hi guys, I just posted a tutorial on AEM that guides you through implementing a custom feature and placing it in the AEM top toolbar.You can see the article here: https://medium.com/@theopendle/aem-adding-a-button-to-a-touchui-toolbar-ae1d1dc1c530 Please enjoy and I'm open to any kind of feedback on...

Okay, well I'm happy to hear it's fixed Just one more question: is "l-container" a class you always want to be applied to your component? Because I think the styles associated with it might belong in the default.less file if that's the case.

I've just tested this, also on 6.5 and I can't reproduce your issue :S Just to get this right, you have a default class, slay "redTextClass" for example, which you entered as a default class. You also created a style which adds that same class (called "Red" for example). On publisher the your compon...

Hi @renan_rsy, thanks for the extra info Short answerNo, unfortunately what you want to do is not possible.Long answerIf you observe the node structure of your template policy definitions, you can see how the existing design of template policies makes extending them impossible. In order to illustra...

Hi,I'd like to help you but I'm not sure I understand the problem. What do you mean by:"component policies" - Policies are note defined at the component-level but are assigned to components at the template-level, so I'm a bit confused."App Container" - Is this a Layout Container that accepts only on...