Develop plan for splitting portfolio sites into their own repo(s) #1876
Description
We want to split portfolio sites away from the data-analyses repo because they're public-facing, whereas a lot of other work in the repo is not public-facing. Also they are some of the largest files in the repo, slowing down git operations in the repo as whole.
Outcomes
- propose a couple plans for how to split: thematic grouping or one repo for each site?
- description of deployment process:
- staying the same as how sites are deployed today?
- do we want to setup automated deployment flows in github actions?
- do we want to keep including built portfolio sites in git history in the same way?