Using AEM SPA and AEM Native (server side) on the same website

[SamFlyn]

Hi,

I have started a project where the client developed a single website using "regular" (server-side) AEM development. They followed all the best practices. However, a migration opportunity presented itself that involves migrating react components from an old legacy CMS (funny enough happens to be AEM 6.2) to the new 6.5. Since we do not want to re-write all of the components in the 6.5 (which are server side) to react spa, is it possible to keep a suite of server-side components and another suite using AEM react SPA?

Thanks in advance,

Sam

[Shashi_Mulugu]

@SamFlyn I don't think you can achieve this in a single page. What u cab do is create/maintain two different projects under fit, one with traditional aem archetype and another with spa archetype and you can either create pages using spa templates and use react based components or use traditional aem templates to use traditional components.

[SamFlyn]

Ohh no we didn't want to mix and match components on the same page. Pages that are built using SPA would be just on a template, components using native would be on a "normal" template. But I was wondering if it was ok to have both types of template on the same root site.

[Shashi_Mulugu · Accepted solution]

Yes you can have both varieties under same content heirarchy