After bombing on the other tutorial (tut) I posted about, I tried this one.
https://www.tothenew.com/blog/aem-with-nextjs-remotespa-a-comprehensive-integration-guide/
In summary, the tut recommends the following
Use the archetype flag frontendModule=decoupled
Set the root page (us/en/home) template to spa-next-remote-page
As a result, the root page properties did not show me an SPA tab, as the tut had led me to expect
Why did this happen? Thoughts?
I will say, a lot of issues result from a mismatch between the archetype version and the AEM version. I am using A50 with AEM cloud from Sept 2023.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Team,
The issue where the SPA tab doesn't appear in the root page properties could stem from a mismatch between the archetype version and your AEM cloud setup. Ensure you're using the latest AEM archetype compatible with your version, and check that the `spa-next-remote-page` template is correctly configured with SPA Editor enabled. Also, confirm that your Next.js SDK version is compatible. Updating the archetype or SDK might resolve the issue.
Regards,
Mnavi Sharma
Hi Team,
The issue where the SPA tab doesn't appear in the root page properties could stem from a mismatch between the archetype version and your AEM cloud setup. Ensure you're using the latest AEM archetype compatible with your version, and check that the `spa-next-remote-page` template is correctly configured with SPA Editor enabled. Also, confirm that your Next.js SDK version is compatible. Updating the archetype or SDK might resolve the issue.
Regards,
Mnavi Sharma
Views
Likes
Replies