Versioning of Designsystemet apps

[mimarz]

We need to figure out a good way for keeping older versions of Designsystemet documentation, this is mostly important for when we get to v2 and need to keep a copy of v1 documentation for users that haven't upgraded or decided to stay on v1.

[Barsnes]

I can add this to #4010.
It would add a new deployment for each release

[Barsnes]

I can add this to #4010. It would add a new deployment for each release

I did not add this. But should be simple enough to add this.
Making sure a domain is added after deployment is done might be an issue,

[Barsnes]

Yesterday we talked a bit about this issue. It was mentioned that we would like all pages that are not component docs to be updated, even on older deploys of the website (for example a v1.designsystemet.no)
There are a few things we can do.
First proposal: This is the easiest, which is just to have a banner at the top, and trust that the user will go to designsystemet.no to get the newest info. We can also have a banner pop up on every page above the MDX when the page is not viewed from designsystemet.no

Second proposal: Make the website do API calls to designsystemet.no, if it's not on that URL itself. This is harder to implement, and we can only do it "securley" for /blog and /patterns, since the other pages are tied to how to use Designsystemet for that specific version.

My honest take: Trust the user. Adding a banner above the header, and possibly a page available on our older documentation about what to expect should do it. I think most people will go to older deployments for component documentation, and not for reading outdated patterns.