I have just recently drafted an article outlining all of my knowledge on integrating a JS front end with AEM. I would appreciate if you could provide some feedback and whether it can be further improved for the benefit of the wider AEM community. The article is below: https://www.linkedin.com/pulse/...

There is also a follow up article https://www.linkedin.com/pulse/approaches-integrating-adobe-experience-manager-aem-front-pereira-rbmlc/

I have created a better solution for AEM next JS here. It still needs a bit of tidying up but it is more scalable and native than the current official solution  https://github.com/rohanrp/aem-remote-ssr-example

I got Next JS 14 working with AEM after I downgraded the app router to use the pages directory. Not a great solution as so many great features exist in the app router but looks like that is the only supported workaround. It could be that pages directory routing is more CSR heavy which allows the rem...

No a solution has not been found

I have followed the tutorials but the main issue is the asset manifest file is not loading anything meaningful. I have tried both the page router and app router  

I have been exploring the template on https://github.com/adobe/aem-headless-app-templates for Next.js integration with AEM. This only seems to work with Next.JS 12 and not the latest Next.js. AEM remotepagenext resource type seems to hit two endpoints in Next.js. One to get the next data props and t...