They don't work the way our guide does. Our guide, for a lack of a
better word, interleaves between paths, so the next button is almost
always incorrect.
We have always added a button to the correct next page manually anyway,
so just rely on that.
Things that happen in this shameless squash:
- Removed 404 page
- It doesn't work in VitePress and making it work in VitePress needs
some invasive hack in the theme that I'm not willing to do
- The default is more than enough, though
- Moved consoleVersionSelect include to another directory
- This avoids being uploaded to Crowdin for translation
- Inline all SafeB9SInstaller includes
- Not only do parameterized includes not work, but if/else statements
don't work at all
- The sysupdate include parameter hasn't been used since MSET9, so it
actually works just fine without any parameters. Hooray(?)
- Move mset9-chorus to an include, that logic doesn't work in VitePress
- Removed Get Started button from homepage, it breaks translations
- Tables in get-started are now shown by default; it seems VitePress really does
not want us to use inline script. So we cannot enable it upon
realizing that the browser is JS capable
- Include parameters are now in frontmatter to allow translation
- Hacked in a bunch of CSS values kanged from the old theme to make it
look not stupid
- Drop headers down one level to make table of contents work
