Not sure if this has changed in AEM 6 compared to CQ / AEM 5.X, but you can determine which components are allowed in design mode. If you want this deployment with your code, you can have a definition in xml design:
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="cq:Page"> <jcr:content jcr:primaryType="nt:unstructured" jcr:title="My Design" sling:resourceType="wcm/core/components/designer"> <mypagecomponent jcr:primaryType="nt:unstructured"> <par jcr:primaryType="nt:unstructured" sling:resourceType="foundation/components/parsys" components="[group:My Group A]"> <section jcr:primaryType="nt:unstructured"/> <myparcontainer jcr:primaryType="nt:unstructured" <par jcr:primaryType="nt:unstructured" sling:resourceType="project/components/myparsys" components="[group:My Group B]"> <section jcr:primaryType="nt:unstructured"/> </par> </myparcontainer> </par> </mypagecomponent> </jcr:content> </jcr:root>
The allowedChildren and allowedParents quite difficult to use and cannot be combined. I refused to use them in CQ / AEM 5.X
source share