User story:

As a developer I want to publish my entire SPA build into a Magnolia module, including the index.html page it creates, and use the index.html as a template script, so that I can easily setup the Page Editor to edit the SPA.

Notes:

Frontend frameworks always build a default index.html page which contains the relative links to other files (such as js & css) and sometimes other metadata such as a "base" path. Often the relatively linked files have new names with every build to prevent unwanted caching, and sometimes the js files are split to optimize app loading performance. It can be tiresome and error-prone to transfer the proper information from this file to a regular freemarker template script. Ideally a template definition can point directly to this generated index file and take care of anything else such as providing the functionality that a page directive does.

Acceptance criteria:

• Developer only needs to provide the path to the index file in their template definition.
• Developer provides a different template renderer name than freemarker, maybe "static", or "single-page-app".
• Developer does not need to add a page directive or any area directives in the file, or change it in any way.

Additional notes:

Possibly the renderer does the following (in the future):

• Loads the specified index.html file.
• Adds the Magnolia page directive.
• Set a BaseURL in the page.
• Write "Mapping configuration" to the page.
• Write "EditorHints" to the page (when in Page Editor).