Page History

Since the 6.2 LTS release, marketers and content practitioners can edit a JavaScript-based SPA (such as React or Angular) in the Magnolia Page editor in the same way they would edit a traditional website. This means developers can implement a headless approach with all of its advantages, and yet content authors still get the control, context and high-fidelity preview of the Page Editor.

...

All content editing is done in the Pages app of the Magnolia author instance. The Magnolia-provided SPA renderer libraries ensure that a SPA project can be edited in the Pages app. The SPA renderer produces template annotations, which the Pages app transforms into the green toolbars – editable page elements. Note: The green toolbars are generated whenever the page iFrame is loaded. Additionally, the green toolbars can also be generated by calling the document.mgnlRefresh() function.

The renderer libraries allow you to work with page hierarchies in the same way you would expect when creating non-SPA pages. SPA applications can load content from different Magnolia pages. The content can be organized using a navigation component or through back and forth buttons.

Example

The angular-minimal is a parent page to the about page:

Image Added

Content of both pages is freely accessible to the editor of an SPA application and links to both pages are placed next to each other on a blue navigation bar:

Image Added Image Added

On the Magnolia side, an SPA has a very simple template definition that just references the index.html file generated by the external React or Angular app.

SPA editing tutorial

Walk through the steps of adding new dynamic components to a managed SPA:

Hello Magnolia - SPA

Browse a minimal demonstration project:

Minimal Headless SPA Demo

See also

• Single-page application (Wikipedia).
• angular.io - a TypeScript-based open-source web application framework.
• reactjs.org - a JavaScript library for building user interfaces.