Proposal for migrating to docusaurus v2

The current docs site is running in docusaurus v1 and I would like to migrate it to docusaurus v2. Since these involve a lot of changes I’ve tried to chunk out PRs as much as possible.

Prerequisites for docusaurus v2:

• The markdown has to be Markdown compatible
  • There are some img and br tags that are unclosed
  • The front matter inside the markdowns have special characters that should be wrapped inside quotes
  • There are some invalid MDX syntaxes inside markdown
  • Changes in consuming translations - https://docusaurus.io/docs/migration/translated-sites

These are some prerequisites that I’ve discovered when I tried to migrate to docusaurus v2 in my local (Basic functions work fine)

related issues:

• https://github.com/babel/website/issues/2546
• https://github.com/babel/website/pull/2044#issuecomment-501659623

I’d like to know maintainers thoughts on this 😄

After minimal migration repro:

Light mode:

Dark mode:

[harish-sethuraman]

I’ve opened a PR with base as main and v2 branch from my fork. Is this okay or can you guys create a v2 branch that we can maintain in this repo? I’ll send PRs to v2 branch of this repo?

[hzoo]

Nice!! We could deploy a separate v2 url (or even doc2.babeljs.io) until it’s ready and swap it, depends on how long we think it’ll take (I’ve actually tried to migrate a few times in the past in previous beta’s - partially made me want to try something else) maybe just keep a temporary branch like v2 until it’s good enough. If we merge into that new branch, it doesn’t really matter if you replace/new folder. Although it will cause some merge conflicts with existing PRs it should be fine since we haven’t been merging too many lately