-
Notifications
You must be signed in to change notification settings - Fork 137
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
Docusaurus v2: Styling #335
Comments
I want to work on this issue. does i have to add any style or I have to change class name |
@Arvind644 : Joy Osive from Team Osive mentioned they have a working version and they are going to open a PR soon. Thank you for checking. |
Thank you. Does there are any other issue to work for |
@Arvind644 there are plenty of Issues that are open and can use some investigative work. |
@DianaLease I'm trying to assign this issue to @jesswang-dev, but she's not in the Accord Project organization, and it looks like I don't have permission to add her. I'm trying to help Jess get up to speed on past issues related to migrating the docs to DocuSaurus V2. CC @dselman @mttrbrts |
Thanks to a major new contribution from @prakharsr, we have a working build of the docs site in Docusarus v2 (in the
docusaurus-v2
branch)The new site should maintain the look and feel of the existing site at docs.accordproject.org, however much of the element hierarchy and class names have changed in Docusaurs v2.
Before we can release this new version, we should reapply the styling.
Existing styling is defined in https://github.com/accordproject/techdocs/blob/docusaurus-v2/website/static/css/main.css
The text was updated successfully, but these errors were encountered: