Configuration and templating logic for Archived versions

Problem to solve

Some features on the site need to be version-aware (docs). There are a few places we'll need to use this logic:

Templates

How can we replace logic like this in Hugo templates?

Some links are also in Vue templates (e.g, the sidebar nav).

Site configuration

Hugo can provide different configuration files for different contexts.

We will need to adjust some configuration for archived versions, at least the baseURL parameter.

• How can we automate the config file as part of the release process?
• The baseURL setting should take care of most (if not all) links on the site. There may be places in frontend code that need similar modification at build time. We will need to test this.

Done when

• Site can run in a subdirectory (example.com/16.7) and render as an archived version should
• Or... issues created for specific steps needed to make this happen (and we can consider this issue a spike)