Details
-
Story
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
SPA Editor 2, SPA Editor 3, SPA Editor 4, SPA Editor 5, SPA Editor 6, SPA Editor 7
-
8
Description
Usually, when developing frontend projects, developers may run a local Node server with live reload. Magnolia does not necessarily need to serve the page. Also for production projects, it's not uncommon for SPAs to be compiled/deployed as static resources on CDNs.
Start with the assumption that an SPA page is presented/served externally, on a different server. Could be Node for (local) development, nginx for production, etc.
Log potential limitations or benefits vs. rendering by Magnolia.
ideas:
- first denominator: mgnl:template property
- action in page-editor? maybe too complex with availability
- url config in template definition?
- open up support in pages app
Checklists
Acceptance criteria