Develop workflow for updating the production website

[JeremyMcCormick]

There needs to be a way to update the production site from Github.

One strategy might be pushing the site content as part of making a release, which could require the tag to be formatted a certain way. I suggest versioning by date like YYYY.MM.DD.N where N is an optional release number, in case there was more than one on a given day.

An example would be: 2022.03.15.1

Tags that do not follow this format could be ignored in CI, in case someone just wants to make a release or tag which does not trigger an update to the production site.

[gmantele]

Very anecdotal comment:
Your tag example (2022.03.15.1) uses a different syntax from what you suggests just above (YYYY-MM-DD-N). Did you mean the separator should be . or -?

[JeremyMcCormick]

Very anecdotal comment:

Your tag example (2022.03.15.1) uses a different syntax from what you suggests just above (YYYY-MM-DD-N). Did you mean the separator should be . or -?

My mistake - I corrected the comment. I would use a "." separator.