-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Migrate Website to Docusaurus 2 Alpha #105
Comments
I'd love help with this! I was tracking the v2 for awhile but haven't touched this website in quite some time. |
Thank you @phated! May we know the reason for leaving the home page as a standalone HTML instead of building it into the Docusaurus website? I noticed this was the case for the Docusaurus 1 website as well but just wondering the rationale. |
@yangshun the original website was created from a purchased theme and none of us have really worked on it. However, my friend is a talented UI designer/dev and is currently working to port her React redesign here—which is what inspired me to get this migration completed. We hope to have more to show off soon and I'll send an updated showcase! |
Thank you! Do let us know how we can help out (code reviews, UI suggestions, etc)! If you like, you could show us the redesign mocks we can comment on the feasibility too! Looking forward to showcasing gulpjs.com on Docusaurus v2 showcase ❤️ |
Issue Body:
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:
I will be helping you migrate and be the POC throughout the migration process. Let me know what you think!
cc @yangshun @wgao19
The text was updated successfully, but these errors were encountered: