-
Notifications
You must be signed in to change notification settings - Fork 317
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
ENH - Scalable colour system for theme #1174
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is WIP but I was curious 🙂 just two little comments of things I noticed along the way
Thanks - this is due to change plenty as I work towards the final bits. But an early review is always welcome. |
🤔 As I have been working on the theme today, I started getting a weird error while trying to use
About my setup:
Extended log-in here if needed
I have removed my If anyone has any pointers here it would be grand |
This is a new one, never seen it before. It's coming from jupyter-cache via Myst-NB, which means @choldgraf is probably the most knowledgable here. Are you still stuck there @trallard ? |
I resourced to start from scratch - new env, clone repo again and it's the only way I managed to get rid of this. I am not sure how this happened tbh as it only appeared after I merged |
Re: the cache, I think you need to delete the jupyter_cache folder in the build directory, that's where all the cached notebooks go. Then it should review from scratch |
I tried that too but the only workaround was starting from scratch. |
As I am adding the finishing touches and updates to docs I realised we'd need to update the screenshot in the Readme. Does anyone know how to create this type of half and half images? |
I did them with powerpoint. take 2 screenshots of the same page in each theme and cut one of them with a triangle then combine and save as image. The shadow is a byproduct of Mac screeenshots but I'm not sure it's necessary. I'm sure it's not the more elegant way to proceed but that would have take me more time to find another way. |
@drammock, thanks for the feedback on the admonitions, I fixed the colours on the light theme, and I agree these look much in line with the dark theme now Also, I replaced the inline code borders in the dark theme for a less bright shade of gray so hopefully, this will be less disruptive/jarring. As for the The target colour Note that in a separate PR I will add underline to the links as these are needed to meet WCAG (not solely rely on colour) so that will also help with any contrast issues against underline/search highlight. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes since my last review look great! Thanks @trallard. This time I did a thorough code review instead of just reviewing the built docs. Most comments/suggestions are minor tweaks to wording in/around the parts of the docs that are changed in this PR, but there are a few substantive questions in there about the CSS/SASS too. LMK if anything is unclear; I think we are 99% there.
src/pydata_sphinx_theme/assets/styles/content/_admonitions.scss
Outdated
Show resolved
Hide resolved
src/pydata_sphinx_theme/assets/styles/extensions/_sphinx_design.scss
Outdated
Show resolved
Hide resolved
src/pydata_sphinx_theme/assets/styles/extensions/_sphinx_design.scss
Outdated
Show resolved
Hide resolved
Just took a quick look, I am +1 on merging. I think it's a clear improvement, and we will get more feedback from ourselves and others once we put it in front of people so I think it's best to merge and iterate rather than trying to get it perfect this time. If y'all want to finish a few things first though that's fine too. |
Co-authored-by: Daniel McCloy <dan@mccloy.info>
hooray!!! in it goes, thanks a million @trallard this is a big big improvement that I'm really pleased with. |
Woohoo! 🎉 |
🎉 Thank you folks it was a long and complex PR, but y'all were more than supportive and open throughout all these months! |
should we make a feature release so that people give us feedback ? |
It might be helpful, but could we wait until #1353 is merged? With those changes we fix a lot of accessibility issues cropping in our tests |
I added the block release tag to make sure I don't forget |
So, apparently this is the place where the dark theme's background color was changed to bluish 😥 I find the former, very dark grey color was much better in the style and impression it gave out to the rest of the page, and that this particular change is quite bad. I guess it may need an issue to start repealing this particular change (I'm not opposed to all the changes in this PR of course), but I would like to learn the rationale for it to understand the context first. |
As mentioned in the first comment of this fantastic PR (thank you again @trallard for your commitment) these modifications were done after a long conversation in #1079 I don't remember all the threads but no color was changed without a good justification from the a11y experts. Note that if you want, you can still revert the color to what they were in your custom.css. |
Closes #1079
Closes #1052
As discussed in gh-1079 this PR will focus on adopting the new colour scheme and not any substantial style changes (these will come in a separate PR). Though I might need to adjust some styles/variables as part of this work, I will do my best to keep you all aligned and update the docs as needed.
🏷️ Edited: I am taking this out of WIP to encourage reviews, comments and questions.
Things I am still not super happy with or need work on (I will check the items as I work on them):
sphinx design
- I have changed the formula to decide on the text colour (using WCAG luminance and contrast ratio formulas but for some reason the mixins in_sphinx_design.scss
are giving me trouble so will debug here)mixin
Sans those little nags and whatever we encounter during the review, this seems to be in a decent place to start reviewing and hopefully merge soonish 🚀
Additional notes:
info
colour for the bg: in the proposal Figma file I had used primary/secondary/accent for these. I changed the colour tosecondary
in this PR, so I have the following questionsinfo
as the default colour? I am neutral about thisinfo, primary, secondary, accent
?For quick checks here is the link to the Read the docs PR preview