Migrate to Docusaurus v2

[asklar]

Chris Glein (@chrisglein) we don't control the order of inclusion as that's done by docusaurus.
If/we move to docusaurus v2, a lot of this can go away since we can just embed react components instead of dealing with css styling

Originally posted by Alexander Sklar (@asklar) in #251 (comment)

[asklar]

We will need docusaurus v2 to support the top level pivots before we can move.
Tracked by facebook/docusaurus#3320

[slorber]

Hi

There's a PR to track, likely to be in next version:
facebook/docusaurus#3539

edit: merged

[slorber]

published the "top level pivots": https://twitter.com/docusaurus/status/1318234989717192704

[chrisglein]

Fast forward a couple years, there's now more information and tools for moving to v2: https://docusaurus.io/docs/migration

[YajurG]

Tried running the automated script as specified on the migration docs. Got an ERR_UNSUPPORTED_ESM_URL_SCHEME which was related to running the script on Windows, and running on WSL should have fixed it. Ran the same script on WSL and got the same error, so have send a message on the docusaurus migration support channel on their Discord and waiting for a response.

[YajurG]

Giving a progress update here:

Completed:

• Ran automated migration script successfully to create initial Docusaurus v2 website
• Resolved several compiler errors related to markdown formatting in several files in the new v2 website
• Able to successfully build the v2 website
• Fixed broken links in v2 website header for documentation and API pages

Pending/To-Do:

• Still need to resolve broken links for homepage and other tabs in the v2 website header
• Can't find the working URLs that the other tabs in the header are supposed to direct to