You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrate the ReactNative website (repo) to Docusaurus v2.
This site is a complex versioned site, but has no i18n, so we can normally migrate it today.
It is a good test to try the new migration cli, and see if Docusaurus v2 has good enough feature parity with v1.
I'd like the Major League Hacking community folks to work on this migration.
Rachel Nabors (@rachelnabors) and Bartosz Kaszubowski (@Simek here and on Discord) are helping to maintain the v1 site.
Some important things to consider:
v1 has many (too much) versions, and a long build time in the CI (30-90min). We don't need to support all these versions, we can only keep versions from 0.60 and "archive" older versions as a standalone v1 site
there's a requirement to generate all the missing pages, for all the versions (???)
static files to redirects moved/renamed docs (here) => should be easy to handle with the client side redirect plugin.
The ReactNative docs are actively edited, so for this migration, we should not focus our initial efforts on fixing the content related issues (md -> MDX), but rather try to focus our efforts on the infrastructure, and handle the changes on the content/docs only once the rest is handled.
The text was updated successfully, but these errors were encountered:
💥 Proposal
Migrate the ReactNative website (repo) to Docusaurus v2.
This site is a complex versioned site, but has no i18n, so we can normally migrate it today.
It is a good test to try the new migration cli, and see if Docusaurus v2 has good enough feature parity with v1.
I'd like the Major League Hacking community folks to work on this migration.
Rachel Nabors (@rachelnabors) and Bartosz Kaszubowski (@Simek here and on Discord) are helping to maintain the v1 site.
Some important things to consider:
The ReactNative docs are actively edited, so for this migration, we should not focus our initial efforts on fixing the content related issues (md -> MDX), but rather try to focus our efforts on the infrastructure, and handle the changes on the content/docs only once the rest is handled.
The text was updated successfully, but these errors were encountered: