Define how to implement the cut from v1 to v2 with respect to current dependencies.

[SilasBerger]

LearningView for GBSL and Lerbermatt heavily relies on links to the current v1. For v2, every class will receive their own page. This means, we need to take into account two key points:

• All links to https://gbsl.silasberger.ch/gym1/ and https://lerbermatt.silasberger.ch/ should remain valid
• Any changes to articles and scripts for the new classes should not impact the old ones (otherwise, links would also be invalidated)

[SilasBerger]

• Remove login button from GBSL page config
• v2 is merged to main
  • login functionality (including login / user pages) exist, but are not immediately visible / have no effect
  • no visible change from the user's perspective
• Create new scripts
  • gym1, gym2 and fms1 remain unchanged
  • new empty scripts: gym28, fms27 -> populate over the course of the comping school year 24/25
  • new script: gym27 -> copy everything over from the current gym1 script
  • existing pages remain unchanged: if a page needs to be updated, first create a marked copy for the legacy scripts: mypage.[gym1,fms1].mdx / MyTopic.[gym2]
  • if changes to components are not backwards compatible: create a copy for the current page and rename the old one: FooBar -> FooBarLegacy (use that on legacy pages)
• Once we are ready to start using the API:
  • re-add the login button
  • create an individual script per class (copy everything over from the respective year script)
  • as before: when upgrading a page to use the API, use markers for versioning