Next Build load vets-website applications

[mreed101]

Description

Next Build needs to load vets-website applications from registry.json and create a static page for each app.
The rootURL listed in registry.json should be the path name given to each respective application.

Screenshot

N/A

Supporting detail

To mimic the behavior of content-build, next-build will need the ability to build static pages that inject react applications inside of a template.

Currently this is achieved in content-build by adding the application to content-builds registry.json file.
Content-build will inject applications into a file called page-react.html which is the template for all applications.
Page-react has a loader called react-loader that checks to see if there is a loading message to give the user. It also checks to see if the application is in_maintenance. Once the application has loaded successfully the loading message is removed from the page.

The following is the current makeup of an application
{ "appName": "COVID-19 screener", "entryName": "covid19screen", "rootUrl": "/covid19screen", "template": { "title": "COVID-19 screening tool", "layout": "page-react.html", "private": true, "vagovprod": true } },

The meaning of the fields can be found inside of the new application documentation.

As a note, all applications use the layout of "page-react.html". This field may not be needed moving forward.

Some form of linking will need to be done with the vets-website repo that will allow a developer to test changes to their applications.
This page shows how this scenario is handled in CB.

Acceptance Criteria

• Applications from vets-website working inside Next Build
• Applications routes match rootURL