AEM SPA integration provides various design models. In an application the developer chooses to use AEM as a headless CMS without using the SPA Editor SDK framework.
What would be an advantage for this design model?
A.
The content author can edit the app using AEM's content authoring experience.
B.
The developer has full control over the app.
C.
The SPA is compatible with the template editor
D.
The developer keeps control over the app by only enabling authoring in restricted areas of the app
AEM SPA integration provides various design models for different levels of authoring capabilities and developer control. In the design model where AEM is used as a headless CMS without using the SPA Editor SDK framework, the developer has full control over the app and can use any SPA framework or library. However, this also means that the content author cannot edit the app using AEM’s content authoring experience, the SPA is not compatible with the template editor, and the developer cannot enable authoring in restricted areas of the app.References:https://experienceleague.adobe.com/docs/experience-manager-learn/spa-editor-overview/spa-overview.html?lang=en#design-models
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit