100% @Lokesh_Vajrala you are bang on.   I somehow align with your thoughts. Finding ROI is very hard.

Thanks @EstebanBustamante for the insights and yes you covered most of the important considerations.   If client is in Adobe Experience suite it might make sense but if a client is on custom infra and looking at AEM as Content repository,  I am not sure how much it make sense to move to cloud.

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..