In a sense NO. Policies can be reused on another template. In AEM we basically inherited the /apps part. When you configure the v2 component policy it will create another node based on your project structure.  

Hello @culver-king , In AEM Core component implementation, when you reorder an Accordion Item, it will automatically move its entire container. You don't need to manually reorder it each time after sorting from the author dialog.   Correct me if I misunderstood your problem.  

Hello @Keerthi0555 , This should be an issue of parsys policy. Maybe your policy is allowed for only the v1 component. To make sure in your component jcr:title="Button (v1)" and jcr:title="Button (v2)" rename it for now and check the difference. If so, allow the component v2 from by policy update.

Hello @vineetham123 , Maybe you are talking about the master branch. I didn't find the 'main' branch. However, I tried to do the same in my local. Unable to generate this issue.   You can do one thing, In your local .m2 delete the biz.aQute.bnd folder and let Maven install it again. Then try to ins...

Hello @AEM_Forum , Yes, content is all about data.  In migration time we use Content Migration and Data Migration terms because in general content is meaning specific to AEM. (page, DAM, tags) and the Data generally means User account, product info (DB data). This means content is a subset of data.

Hi @goyalkritika , Maybe you made a mistake in XML. I tried to generate the same but it's perfectly working. I doubt in your multifield property you missed , composite="{Boolean}true" Still I am sharing the full XML with you, Hope you find your mistake, <?xml version="1.0" encoding="UTF-8"?> <jcr...

I can't give you any reference articles but I have a tailwind setup with the latest archetype(42).You can follow this setup example: https://github.com/SadyRifat/aem-vue/tree/fe-tailwind-setup/ui.frontend  Hope this helps you.

Hello @kashyap691 , The custom component making is fully internal. I just share the idea. Till now I haven't seen anything like this in any public blog. However, the parsys allowed component is a different discussion.  Since you mentioned you are facing trouble setting the component policy from the ...

Hello @kashyap691 , From my experience, I faced this situation many times and was successfully supported by a simple component. What I did is, I created a new component called "flex container". This is 100% the width of the layout and has a paysys.Features of this component: Different Background ima...

Hello @supriya-hande , For your requirement, the best practice is using Sling Delegation Pattern where you need to change the logic of "Options for Child Pages" in your Java implementation class. The core list implementation: https://github.com/adobe/aem-core-wcm-components/blob/main/bundles/core/sr...