Skip to content
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

Update Docusaurus to 1.3.0 #6510

Merged
merged 7 commits into from
Jun 22, 2018
Merged

Update Docusaurus to 1.3.0 #6510

merged 7 commits into from
Jun 22, 2018

Conversation

yangshun
Copy link
Contributor

Summary

Docusuarus 1.3.0 brings about some backwards-incompatible CSS changes. So the team is helping the major users update 😄

Thankfully Jest doesn't have much custom CSS, so there isn't too much to be done.

Changes made:

  • Upgraded Docusaurus - CSS changes
  • The landing page logo was invisible to the user because it was a white-outline logo on a white background. Changed it to the non-outline version.
  • Changed the theme of the syntax highlighting to a "ocean". It has more contrast and looks better. Hopefully it's welcome. If not I'd be glad to revert it.
  • Enabled in-page navigation in siteConfig.js for better user experience while browsing the docs.

Test plan

Ran the site locally and visited every page.

screen shot 2018-06-20 at 9 42 21 pm

@SimenB
Copy link
Member

SimenB commented Jun 21, 2018

yarn lint --fix from the root of the project (not the website directory) should fix it 🙂

@SimenB
Copy link
Member

SimenB commented Jun 21, 2018

Mind including the yarn.lock changes?

@SimenB
Copy link
Member

SimenB commented Jun 21, 2018

I love the new theme and navbar, btw!

@SimenB SimenB requested a review from cpojer June 21, 2018 05:50
@yangshun
Copy link
Contributor Author

yangshun commented Jun 21, 2018 via email

@thymikee
Copy link
Collaborator

Not sure about the color theme changes. What I'm concerned is that the dark background of the code on white website seems to me like it's "popping out", and kinda distracts me when I change focus from one code block to another.

@thymikee
Copy link
Collaborator

To fix this, we could make the code background opaque a bit (just less contrasting to the website bg), just not sure how if the code will still be readable though.

@yangshun
Copy link
Contributor Author

Hmm got it @thymikee. Do you want me to revert the code background theme? Alternatively, pick another theme from https://github.com/isagalaev/highlight.js/tree/master/src/styles 😄

@thymikee
Copy link
Collaborator

Not quite revert, because I like that the new theme is better at syntax coloring :D. Would be nice to tweak it a bit.

@cpojer
Copy link
Member

cpojer commented Jun 21, 2018

Can we use a light syntax team please?

@yangshun
Copy link
Contributor Author

I shall leave the theme as it is. Would be better not to include them in this PR 😄

@endiliey
Copy link
Contributor

Excited to see this update 😊. Pretty url ? (No .html) ?

@yangshun
Copy link
Contributor Author

yangshun commented Jun 22, 2018

@endiliey Thanks for the reminder, I turned on the cleanUrl option. @SimenB this is ready to be reviewed again.

@yangshun
Copy link
Contributor Author

yangshun commented Jun 22, 2018

Are the CI failures legit? They don't seem related.

@SimenB
Copy link
Member

SimenB commented Jun 22, 2018

Not sure about the CI failures... Doesn't seem related

@cpojer cpojer merged commit 404da0f into jestjs:master Jun 22, 2018
@SimenB
Copy link
Member

SimenB commented Jun 23, 2018

Opened up #6529 tracking CI failures

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants