Magnolia comes with modules and libraries that help you develop a Single-Page Application (SPA),
"a web application or web site that interacts with the user by dynamically rewriting the current page rather than loading entire new pages from a server." (Wikipedia).
To serve SPA pages, you need to:
- Connect the SPA to the REST endpoints of the Magnolia public instance which will serve page content and template information to the SPA.
How is a Magnolia page served as an SPA page?
An SPA expects two types of input: page content and template definitions .
- Page content, which is always edited in the Pages app, is requested by an external SPA through the Magnolia Delivery endpoint API v2.
- Page, area and component template definitions are requested by the SPA through a dedicated Magnolia template definition endpoint.
Once available to the external app, they are passed to a function in the app app that renders the final page tree.
Rendering an SPA page
The page node represents the root content for a given application state, for example a page title or page properties.
Note: In front-end terms, a page is also a component, just a top-level one.
- Each JCR node then represents a page, area or component.
Editing content of an SPA page
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
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:
Browse a minimal demonstration project: