Support for users on older Plate versions

[richardantao]

Overall, this library is awesome, but the frequency of breaking changes is more than any other library I've seen, and the worst part is that the documentation for older versions is immediately stripped once a new version is released...

Is there a way that documentation can be maintained for older versions?

[zbeyens]

We didn't find an automated way yet. Feel free to maintain the docs you need at your pace. Here are the Vercel settings we use:

[Klausdk1999]

I had a similar problem, needing to access an older version of the docs and end up checking older data via git here. I would like to suggest adding the option to select between a couple of old version. Let me try to sketch some ideas on how to handle this:

• For now I would suggest adding current, 31 and 26 or some other versions suggested by @zbeyens or other maintainers based on bigger changes.
• As they are available on this repository git repo history, I would try to implement a solution to host all of them as they are and just redirect to the older ones.

I could try doing this when I'm off work and opening an issue but would be good to hear other opinions. I also did not check how the CI/CD is set currently and if I can check those files or suggest merges to the actual deploy configs.
In a separate issue I could also sketch a migration guide, as I might be working on it in the future.