Content Tree: Any component which uses core/wcm/components/image/v3/image as super type always displays as a root item in the content Tree

Hi @dennisatdept 

Please check if helps https://medium.com/@arunpatidar26/cq-iscontainer-property-in-aem-94e5318e04fa 

Hi @dennisatdept,

The issue seems becuase of:

1. Missing cq:parentPath association

If a component renders outside the container’s DOM scope, or lacks certain metadata, AEM doesn't attach it correctly in the editor tree.

2. Image v3 uses data-cmp-is=image and is DOM-self-contained

Core Image V3 component uses its own isolated HTML output with no explicit support for slotting within parent containers' data-path blocks unless you explicitly manage layouting.

It doesn’t automatically inherit a cq:parentPath unless wrapped inside a container component with correct structure.

To resolve your issue try this:

1. Wrap v3/image in a container

Create a proxy component or wrapper (eg. GridImageItemComponent) like this:

<sly data-sly-resource="${'image' @ resourceType='core/wcm/components/image/v3/image'}"/>

But more importantly, in your wrapper component’s cq:editConfig.xml, include:

<jcr:root
    xmlns:cq="http://www.day.com/jcr/cq/1.0"
    jcr:primaryType="cq:EditConfig">
    <cq:dialogMode>floating</cq:dialogMode>
    <cq:layout>
        <cq:dropTargets jcr:primaryType="nt:unstructured"/>
    </cq:layout>
</jcr:root>

This hints to the editor that the image is part of the layout and belongs within the hierarchy.

OR

2. Use cq:isContainer="true"

In your wrapper component’s cq:editConfig.xml or cq:component, add:

<jcr:root
    jcr:primaryType="cq:Component"
    cq:isContainer="{Boolean}true"
    componentGroup="Your Group"/>

This helps AEM understand that your component acts as a container in the Content Tree.

@dennisatdept Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!