AEM version and dependency to SPA projects on GitHub

[erlingklaeboe]

Hi.
We are planning to migrate our AEM site to SPA/SPA Editor/React.
Currently we running AEM 6.4.5 (on-premise) and have a couple of questions:

1)

Do we get any improvements with regards to SPA/SPA Editor/React eco system by upgrading to AEM 6.5 (SP4) first ?

Or is it more dependent on the GitHub projects mentioned below ?

2)

Are the SPA/SPA Editor projects on GitHub like
@Deleted Account/cq-spa-page-model-manager
@Deleted Account/cq-react-editable-components
@Deleted Account/cq-spa-component-mapping

independent of AEM version, and will they work well on both 6.4.5 and 6.5 ?

Basically we would like to know the benefits of upgrading to 6.5 with respect to SPA.
It is difficult to get any technical details out of the 6.5 Release Notes.
Thanks.

Erling

[berliant]

We always recommend upgrading to the most recent SP. 

The Service Pack package also includes SP fixes and improvements.

Available GitHub projects require a minimum version of 6.4.2 or 6.5. Both branches are equally supported. 

[raghavc · Accepted solution]

With AEM 6.5, below 2 new features is available

1) Use Template Editor to edit and configure the AEM editable parts of the SPA
2) Use Multi-site Management to create country, franchise or white-labeled SPA experiences

[Nikhil-Kumar]

@erlingklaeboe 

As compared to 6.4.x and 6.5.5 following are the changes that I observed as part of SPA Editor.

1. Now editable templates are available to use in 6.5.5
2. Due to the availability of the Editable templates we can have runtime CSS ataached.
3. Experience Fragment is enabled in SPA editor.

Thanks,
Nikhil