The solution that many have taken to this dilemma is to separate the markup from the content – leveraging AEM as a “headless” CMS while the SPA consumes this content through RESTful web services. The downside to this approach is that marketers lose the rich, in-context authoring capabilities that AEM provides. Now, in AEM 6.4, we can build sites using these frameworks while still providing drag-and-drop, in-context editing to marketers.
To learn more about where we are today, where we are headed, and how you can participate in the SPA Editor Beta program, read Getting Started with SPAs in AEM on the Solution Partner Portal.
If you work at an Adobe Partner and are a member of the Solution Partner Portal, check out the new Implementation Best Practices series written by the Adobe Partner Experience team for AEM, Campaign, and other solutions and get updates on upcoming partner events and webinars.