Hi there,
I don’t have a good example implementation, since they’d depend quite heavily on how you handle and publish releases. Two workflows I am aware of people using:
- use semver directory structure and duplicate unchanged content in /1.1, /1.2, /1.3 . This would require that you have a git workflow where you do this already, since I’m not trying to suggest you restructure your repo or release process. Then the deploy just works. You might have “default” be the last stable version by pointing your main index.html there rather than to actual-latest-version that could be in beta or not-quite-released-yet.
- another workflow that I am aware of someone using is branch deploys + subdomains, so each semver is a branch, and they effectively have hundreds of branches one per version and all their docs are linked in a version-first way (index is a table of contents and each link goes to https://branch-1-1-1--theirsite.netlify.com aka branch-1-1-1.theirsite.com, https://branch-1-1-2--theirsite.netlify.com etc). That is a bit challenging as updating the look and feel of the site at branch-2-0-0 won’t be “automatically backported” to branch-1-1-x that are effectively frozen in time, but it does allow you to manually merge design changes back into those branches if that is important to you.
There are dozens of other ways to do it, but hopefully those two that I’ve seen work (though I apologize I can’t link to them) will inspire and inform.