The layout container should be used with policies as much as possible.

If you are on AEM 6.3 - you should be using coral 3 Multi field as discussed here -- Building Experience Manager Components using Granite/Coral Resource Types

Can you post the code you are using.

Also - see this Blog from our Touch UI expert. When you get into customizing the plug-ins - you typically are dealing with JQuery code. Experiencing Adobe Experience Manager - Day CQ: AEM 63 - Touch UI RTE (Rich Text Editor) Color Picker Plugin for InPlace…

Checking with internal team for this use case.

You can just as easily put an Experience fragment that represents a header or footer into an editable template. Then you can lock that in the editable template so an author cannot modify that content. When you create a page based on that template - the header and footer shows up. It does not matter ...

What AEM Version are you using. Are you using editable templates to place headers onto a template?

Also - watch this GEMS session: From Unit Testing to Integration Test of an AEM Application

I am gonig to test to see if i can reproduce you issue.

This type of use case can be easily addressed when you use editable templates. You can lock components in place when using an editable template. However - since you are using AEM 6 - not 6.4 - you are correct - you can hard code them in the template. When you do this... .<div data-sly-resource="${'i...