Move to vuepress@next

[ricardobalk]

I should move to vuepress@next, as this newer version of VuePress has been completely refactored with TypeScript. And that's pretty good news, as I also converted most of my own code into TypeScript a while ago (#55).

• GitHub repository: https://github.com/vuepress/vuepress-next
• Docs: https://vuepress2.netlify.app/guide/getting-started.html

Workflow

So, what will the workflow be? I'm thinking of this:

TL;DR version: Try, fix, fix again, test, test, test, test, test, done.

• Create a separate Git branch.
• Try out vuepress-next.
• Move my current files on a component-by-component basis.
• See what breaks.
• Try to fix it.
• Actually fix it.
• Fix it again.
• Test the whole website 3000x
  • Does Docker still work?
  • Does the VSCode Dev Container still work?
  • Are the manifest files (e.g. package.json) up to date?
  • Does the site still render without JavaScript?
  • Are there any other ugly artifacts?
  • Try to build the site locally (yarn build)
  • etc.
• Merge the new branch into develop
• Test another 1000x
  • Try to serve the build locally (yarn build:serve)
  • Try to serve the build again with Nginx
  • Try to deploy the build to my VPS (yarn deploy)
• Merge branch develop into main
• Spread the news
• Consider using Vite, or Nuxt with Vite, whatever.