Migrate / transition to a Greenwood Theme Pack

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

This would effectively allow this repo to additionally be consumed as a package from npm in a Greenwood project using the (soon to be released) "Theme Pack" capability.

Details

This would require such tasks like

1. Adopt Greenwood theme pack convention, figure out DX
   • Updating package.json and creating a prerelease script to correct prepare templates and pages
2. Validate in https://github.com/thescientist13/knowing-your-tco, push content to new repo
3. Needs fix consistency with user plugin node modules resolution ProjectEvergreen/greenwood#692
4. index.html override interim solution - support custom pages through theme packs ProjectEvergreen/greenwood#681 (comment)
5. Updating README.md to provide broad array of usage options
   • Installation
     • "clone" and go with git
     • degit?
     • npm / Greenwood
     • copy / paste!
   • Usage (slides API)
   • comment on distributing and publishing apps made with Greenwood ProjectEvergreen/greenwood#610
6. Contribute back to Greenwood publishing discussion?
   • Further technical details about peer vs dev deps?
   • bundle dev dep plugins as part of the plugin itself!? (reduce peers)
   • index / pages
7. Rename repo to theme?

New Issues

1. Add tests using gallinago - add test cases with gallinago #26
2. Adopt truly encapsulated pages (MVP) - add support for truly encapsulated pages for theme pack (for plugin authors) #24
3. Figure out deps - figure out best way to manage plugin dependencies through just this project's package.json #25
4. Track supporting yarn build and yarn serve workflows (since our Netlify build is broken currently) - add support for Greenwood yarn serve and yarn build #27