Thinking about this some more, I think we should handle updates to the site by maintaining a separate dcc-website-staging repo. This will allow us to have a live staging site to view rendered changes before publishing to the live site, so the process for updating the main site will be something like:
Make updates in staging repo
Review updates on staged version of the site
Open a pull request to the production version of the site and merge
Text edit PRs can made by anyone but Gillian is primary editor and lead which includes monitoring issues
Edits will need reviewer approval by DCC Site team - @kayaelle & @dmitrizagidulin for now
Structural edits made by developer on fork and tested locally with reviewer testing locally or if changes need approval/feedback beyond reviewer (most likely), staging repo created where the github pages can be viewed publicly; After testing complete, staging repo merged to main site repo.
Thinking about this some more, I think we should handle updates to the site by maintaining a separate dcc-website-staging repo. This will allow us to have a live staging site to view rendered changes before publishing to the live site, so the process for updating the main site will be something like: