Moving dev stuff from #1380 for more targeted work...

We either need to finish #980 -- which still needs some work, possibly on the antwar level -- or port the site to a more stable build tool like phenomic or gatsby. Porting the site would also offer a few things, like full HMR, that #980 doesn't address but will require some serious thought. Either way these are the infrastructure issues we need to solve:

• Resolve <title> issues (e.g. #720).
• Display index pages correctly (#1085).
• Bail if YAML/Markdown parsing fails (#1070).
• Easier specification of custom layouts per guide (e.g. #1367).
• Consider a better hosting/deployment setup like Netlify (e.g. #845).
• Mark releases (synced with main package) and archive them (#176, #1017).
• Consider landing page image load improvements (#1548).

UPDATE: Fixed on The rebuild Branch

• Interactive bundles contain duplicate code (#877).
• Migrate away from marked and clean up process (webpack-contrib/webpack-defaults#73).
• Better HMR, faster builds, and quicker build tests.
• Continue component/utility modularization and simplification.

The last one refers to outsourcing much of the custom dev-related stuff to more modular packages as we've done with the voting app and extracted banner (though neither are actually being consumed yet).

Other Dev-Related Issues

• #1519 - Synchronized routing and /content structure with less configuration.
• #1400 - Turn the site into a PWA (sync w @TheLarkInn).
• #469 - Allow illustrations via Mermaid.

cc @montogeek @probablyup @geoffdavis92 @MoOx @bebraw @hulkish. If I've missed anyone please let me know, but I've tried to include everyone who has shown interest in site dev or has previously worked on site dev regularly.