Skip to content

Migrate Website to Docusaurus 2 Alpha #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Gauravsaha-97 opened this issue Jan 19, 2020 · 4 comments
Closed

Migrate Website to Docusaurus 2 Alpha #360

Gauravsaha-97 opened this issue Jan 19, 2020 · 4 comments

Comments

@Gauravsaha-97
Copy link

Hi there! The Docusaurus team is currently developing Docusaurus 2 and are 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

@alexkrolick
Copy link
Collaborator

I'm happy waiting until the stable version is released

@eps1lon
Copy link
Member

eps1lon commented Jan 19, 2020

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

Sounds awesome. I have little experience the docs infrastructure so I won't be able to assist much with questions why certain decisions were made.

I think having a long living pull request that gets frequently updated would work. I don't think we want to deploy an alpha but having a netlify deploy preview would help ironing out issues with an unstable release.

Embeddable interactive React components within markdown via MDX

😍

@MatanBobi
Copy link
Member

MatanBobi commented Jun 3, 2020

@afontcu What do you think about closing this one and managing the task within #487 ?

@afontcu
Copy link
Member

afontcu commented Jun 3, 2020

yeah, makes sense! Both issues are essentially the same but the other one is already linked to the project, so I'm closing this :) thx!

@afontcu afontcu closed this as completed Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants