thanks for your input and opinion here @mlaraadobe .

Thanks for sharing it here @arunpatidar . It consists of great discussions on why upgrade to AEM 6.5 LTS. But if a org is doesnt have any on-prem restrictions what should be there motivation behind choosing LTS vs AEM cloud? To play safe goto AEM LTS or To get new GEnAI features goto AEM cloud?

Thank you @daniel-strmecki . This is insightful.

Hey Adobe community, With AEM 6.5 heading towards End of Life (core support ends Feb 2027, extended support Feb 2028), a lot of us are asking: What’s next? Should we stick with Long-Term Support (LTS) or take the leap to AEM Cloud? Let’s dig into the real questions: Why Upgrade?Is it just about sta...

@mancillaign content and its semantic html comes from AEM author instance.   While we can technically customize aem franklin components , Adobe is discouraging the idea to avoid unnecessary complications in future while using other integrated features such as Universal Editor,  AEM Sites Optimizer  ...

@seshasai are you using Document based authoring or AEM EDS Sites?If you are using document based authoring, you can use metadata section to author JSON-LD schema as below screenshot..

@jayv25585659 your technical approach looks good to me. But functionally i have a question, if the field is modified via page authoring process, why cant that value be stored under the same page itself why under /conf?Also as per your latest post, Generic list is very good feature to store generic k...

Uncover the secrets behind AEM Dispatcher—the gatekeeper that powers secure, high-performance web experiences.Learn how smart caching and filtering can supercharge your Adobe Experience Manager sites.