ctulocal1/2019-district-contract

Initial static-site build script for shell-contract unification

Opened this issue · 0 comments

Since the entry point to the web app can be from any contract article in any contract--as well as through a home page--a static site must be generate by combining the app shell code with every page of the contract and deployed to a public directory. This public directory will be the basis for Netlify to serve up all contracts as a static site.

Each static page will include manifest and service worker code to form the basis of the PWA and make it capable of download and installation.

Also, the static site deployment code will form the basis of the service worker's local routing. So that local settings and feeds can be combined with serving up the contract snippet to create a full app experience.