Hello, We are using service pack 6.5.10, and we want to generate a sitemap.xml. Whatever documents I have read so far all talk about the AEMaaCS approach or OSGi config that comes with 6.5.11 or later version. I haven't found anything about the lower versions. Also, we recently migrated our existing...

Hi @arunpatidar I also thought of putting core components inside the core folder but I created the below folder structure. I hope that's ok. /apps/<tenant>/components/content /apps/<tenant>/components/core /apps/<tenant>/components/structure I will further categorize components inside the content fo...

Hi @Jagadeesh_Prakash, Sorry for the confusion but I am not looking for the overall folder structure. I am only looking for the folder structure under the components folder especially when you have a lot of components (both core and custom) then how do you manage the folder structure for the compone...

Hello, I just wanted to check if there is any guide on the folder structure for the components. I have researched a bit and found out about the /content and /structure folder. I am not sure if it's old school or still applies nowadays. Additionally, when we create a project using the maven archetype...

Hi @Ganthimathi_R Thanks for your quick response. Would you please provide the complete code for the second step?

We have a simple content approval workflow where authors can trigger the workflow once done with the changes. Now approvers group gets the notification and they can go and approve the content and complete the workflow that publishes the pages right away. We got the requirement from the approvers tha...

Hi @ShaileshBassi This seems like a possible solution for us as I can set this up for a particular project and not for the entire instance. I am totally new to the AEM so would you please tell me where can I find OOTB Launcher and OOTB "Dam Update Asset"? If it's ok for you, would you please list do...

We are not using renditions and have no plan of using them. Is there a way to configure the image core component or disable renditions so that when it tries to get the src of the image, it can use the direct path from the dam instead of the rendition path?

Hi @sunil_kumar_ This is what I found in folder config.publish > org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl.cfg.json. This came with the maven archetype only. We didn't add it. { "resource.resolver.mapping": [ "/content/careers/</", "/:/" ] }  I am not exactly sure...

I have published all the content including DAM to my local publish instance but for some reason, the images are not loading in publish instance with the core image component. I see all other contents though. Also, I have noticed that src has been manipulated. I see the correct path in the data-asset...