As an AEM developer, staying current with Java versions ensures we can leverage the latest features, security patches, and performance improvements. With Java 21 being the latest Long-Term Support (LTS) release, it's a critical upgrade for enterprises and developers working on Adobe Experience Manag...

Hi @SahilDh1,I've never tried it, but there seems to be an API for re-ordering: https://developer.adobe.com/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html Good luck,Daniel

@jooca just be careful with using Sling mappings in case you need to support the same Vanity URLs on multiple domains. Reasons why are explained in the article: https://meticulous.digital/blog/f/aem-url-shortening-sling-mappings-vs-dispatcher-rewritesAlso, you said you have a requirement "We need to...

Hi @ayush-804,Since you asked this question, I assume you are talking about your FE components (their JS code) calling the same AEM API. In case my first assumption is correct, then it also depends on whether your FE components share any state between them or if they are fully independent of each ot...

Hi @30991930w169,I don't think this is possible, what you can try is to:Separate the code in the two repos into different modules and paths so they don't have any conflictsUse the Adobe Git repo to merge/sync the changes from both reposNote that you will need a custom GH Action or similar to achieve...

URL shortening or mapping is a crucial aspect of modern web development, so the same is valid in Adobe Experience Manager (AEM) projects. Short and user-friendly URLs improve user experience, enhance SEO, and ensure consistency across multiple channels. AEM default URLs are not SEO optimized, as the...