beef up branch deploys for static assets

maxheld83 commented 4 years ago

uh, doing this properly is turning out to be pretty complicated:

[ ] adapt my (container-based, to be safe) action to push to gh_pages to:
- merge in subdirectories but also deleting the history (so as to avoid the repo getting too fat)
- write out a JSON of all the current branches and tags available on gh-pages and paths, because there's no way to do this directly in JS. Needs a data object first. This data object must sit at the root, and be overwritten by every push to gh-pages, updating it by reading the file structure anew.
- set a robots.txt or whatever to make sure the other branches and tags aren't being indexed by search engines
- deploy the latest release (or master or whatever) also to root
- ensure that no directory name clashes with any of the refs
[ ] adapt pkgdown
- to show the refs.json as a dropdown
- and also write the ref to description?

maxheld83 commented 4 years ago

this is too complicated and out/of scope for now, so this will be on the backburner

maxheld83 commented 4 years ago

duplicate of #29

subugoe / metar