-
Notifications
You must be signed in to change notification settings - Fork 49
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
Mu/colors #245
base: main
Are you sure you want to change the base?
Mu/colors #245
Conversation
…/dark variants when necessary.
Hey! Finally took the time to handle the dark scheme. |
* ╰───────────────────────────────────────────────────────────────╯ | ||
**/ | ||
:root { | ||
--main-font-family: sans-serif; |
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.
We can totally remove these font variables. Sorry for the noise.
color: var(--fg-normal); | ||
} | ||
|
||
.keyboard form fieldset::before{ |
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.
This section is for styling the geometry/characters selectors (I wanted to try something very light, w/o colors, with a nice CSS animation to highlight the selected one).
{{- else }} | ||
{{- with . | minify | fingerprint }} | ||
<link rel="stylesheet" href="{{ .RelPermalink }}" integrity="{{ .Data.Integrity }}" crossorigin="anonymous"> | ||
{{ range $css := slice "css/theme.css" "css/icons.css" }} |
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.
This change is here to also load the css/icons.css stylesheet. Feel free to integrate it otherwise obviously.
@@ -1,5 +1,18 @@ | |||
{{ $name := .Get "name" }} | |||
<div class="keyboard"> | |||
{{ if $name }} |
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.
This change was aiming at moving the menu/links above the keyboard (instead of below the keyboard). Idem, feel free to reject that obviously.
Hey, nice to see some movement on these stylesheets. :-) I really like the light color palette, especially for the keyboard layouts ! Maybe we should use an external stylesheet for these SVGs, by the way. As mentioned in your previous PR, I really struggle with unnamed variables such as Accessibility-wise I think the palette lacks contrast on the various menus, and has too much contrast on keys. Let’s get through that. Main menu: before/afterThe new menu looks nice but I lack the visual indication for the sub-menu. The current pseudo-tab probably looks (very) outdated, but I thik it makes it clear that Slightly related, I kinda miss some “accent” information for the table of contents. Keyboard layouts: before/afterI’m certainly biased but ! prefer the older geometry selectors: thinner, slicker, impossible to miss. I think the navigation menu should stay below the SVG. And though I agree using glyphes as icons is debatable, the main point is that it scales nicely with the button text: same height, same baseline. Maybe a few SVG icons used as backgrounds could look nicer and still scale nicely along with the button texts? But again, that could be for another PR. Keys: before/after{light}/after(dark}These IIRC, in the current stylesheet these |
Long story short, maybe we should aim lower and focus on:
If this helps us focusing on the color palette, menu icons and font settings could be another PR. But as usual, this is just a suggestion. :-) |
Hey! Thanks for reviewing that! Color palette variable namingI have no special attachment to these variables, it just helps prototyping the colors for now. Main menu and sub menusTotally agree on your remark about not showing clearly enough that the submenus are indeed related to the main menu above. I just chose not to deal with that for the moment, I just needed a white background to setup the color of the other elements (and get rid of the greyish tabs). Geometry and characters menus (below the keyboard)I found the original buttons too similar to the keyboard keys and I tried to propose something that clearly differs from the keyboard itself. But that was just an experiment. Navigation menu (installer, tester, stats ...)I now understand better why this menu was below. Originally, it was not clear to me that this nav was related to the keyboard widget. So maybe we need to think about a way to let the entire widget to appear as a whole, hence visually attaching the nav menu into the widget. As for the glyphs, I just know I don't like the look and feel of unicode glyphs, not sure how we should do it anyway, and this could be another PR obviously. kbd stylingTotally agree for less contrast (either reversing style or using different shades of grey - maybe a version common to light and dark would suffice? |
Hey guys, here's a new PR with a reduced number of changes:
I chose to let the color palette variables explicitly in the CSS files because I tend to prefer having this color abstraction.
In case we want to change the palette later on for instance.
Wdyt?