Migrate Website to Docusaurus 2 Alpha

[khushal87]

Hi there! The Docusaurus team is currently developing Docusaurus 2 and is almost done with an MVP that doesn't include translations and versioning features, which means there's feature parity with your website's current usage of Docusaurus.

Docusaurus 2 brings about many improvements:

• Client-side rendering with prerendering (site renders without JavaScript!)
• More flexible appearance - Customizable layouts, CSS modules, etc
• Embeddable interactive React components within markdown via MDX

I will be helping you migrate and be the POC throughout the migration process. Let me know what you think!

cc @yangshun @wgao19

[khushal87]

@lena-kashtelyan

[bernardbeckerman]

Hi @khushal87, would you be able to provide some pointers on the migration procedure and its expected scope, as well as any benefits of doing so not mentioned above? Thanks!

[yangshun]

@khushal87 the Docusaurus 2 migration task is super old and Docusaurus has already officially released v2... This task shouldn't be opened at all.

[yangshun]

@bernardbeckerman, for context, this is the original task: facebook/docusaurus#1834. It'd still be good to migrate to Docusaurus 2 eventually though, because Docusaurus 1 is no longer being maintained.

[Balandat]

@yangshun we have a pretty funky setup (see e.g. this script) where we are doing versioning of sphinx docs that we render via docusaurus. We do this by essentially manually stripping out the body of sphinx html documents and inserting them into static content that is then integrated into the docusaurus page (see here).

My understanding at least in the past was that this wasn't straightforward to do with docusaurus v2 - maybe that has changed?

[khushal87]

Hey @yangshun, so here I find that the docs are still using 1.7.2. So, migration to a stable version of Docusaurus 2.1.0 would be useful, right?

[lena-kashtelyan]

This is probably not happening soon and is already on the wishlist, so closing this for now.