[Copilot]

Preserve older major-version documentation as website snapshots on subdomains such as v1.designsystemet.no, with a clear path to the latest documentation.

• Version banner: DOCUMENTATION_VERSION enables a Norwegian/English notice above the header, including error pages, linking to https://www.designsystemet.no/. Unset leaves the current site unchanged.
• Docker configuration: Passes the version label during prerendering and at runtime.
• Archive deployment: Documents snapshot retention and separate Azure deployment, DNS, and HTTPS setup. Subdomain provisioning remains manual.

docker build --target www --build-arg APP_ENV=production \
  --build-arg DOCUMENTATION_VERSION=v1 -t designsystemet-www:v1 .

• Fixes Versioning of Designsystemet apps #2730

[changeset-bot]

⚠️ No Changeset found

Latest commit: 315f1fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Barsnes]

@copilot We only want manual deployments. We just need an ENV var to be set, which should include what major version this deployment is for.
So, we want a deployment for v1.designsystemet.no, which we do manually.
Later on next year we will do one for v2, and so on.
This ENV var should also make the "alert" banner in the header show and tell the user this is an old version of the docs

[Barsnes]

@copilot We also need to make sure we can deploy this from our GH action dashboard. it should be a manual deploy where we set the ENV

[Copilot]

@copilot We also need to make sure we can deploy this from our GH action dashboard. it should be a manual deploy where we set the ENV

Added in 315f1fe: Actions → Deploy www → Run workflow, select the snapshot branch/tag, choose production, and enter documentation_version (e.g. v1). The workflow sets the ENV for prerendering and Azure runtime. Leave the field empty for current-site deployments. Dashboard steps are documented in the website README.

@copilot We only want manual deployments. We just need an ENV var to be set, which should include what major version this deployment is for.
So, we want a deployment for v1.designsystemet.no, which ...

Addressed in 315f1fe. Archives are manual-only: entering v1 or v2 deploys to a separate app (www-v1, www-v2) and sets DOCUMENTATION_VERSION during build and runtime to show the existing old-documentation banner. Current-site deployments remain separate; DNS/HTTPS setup remains manual.