-
Notifications
You must be signed in to change notification settings - Fork 126
Adds Noon, Evening and Afternoon variations #333
Conversation
|
The buttons especially in noon are still problematic, with some background colors both the default and outline buttons look like plain text. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
From the screenshot, it looks like section 3 and 5 in afternoon is the same? |
|
The button outlines in styles 2 and 4 don't look good in any of the variations. Is there something we can do about it? |
|
I'll try to add a different color in Afternoon. |
I think this will be the most difficult part about adding the variations. In styles/blocks/section-2.json the button is set to contrast and base: Then in noon (as an example), section-2 can be updated like this: |
|
(the outline button can not be changed the same way) |
Preview changesYou can preview these changes by following the link below: I will update this comment with the latest preview links as you push more changes to this PR. |
Yes the colors can be changed. And I mean I can implement it and I could make a decision about what colors to use but you might not like it 🥹 |
|
Here is the list of color changes that were made: I would like to know if the color palette presets should be updated to match the changes in the global style variation. Noon
Evening
|
|
Overall, looks good! Saw no issues with the styles other than what Carolina has mentioned. What @richtabor mentioned about style variations is still on my mind for this one: is it simply echoing the changes you are already proposing here, @carolinan? Essentially what we want to avoid is having style variations that have color or font palettes that are unique from the discrete color and font presets, these: If we can keep those in sync, we can move fast. Otherwise we should get the presets perfected first, and then combine them into variations. What do you think? Note, I was AFK for a bit and catching up, so apologies if I'm missing a nuance, and thank you for the pings! |
|
Yes, that was my intention, for the palette color and the global style variations to match. It is not clear to me why the palettes needed to change. |
|
I believe it would be easier to manage these as separate pull requests. |
Having one font size on the button block and another on the button element meant that the default button and the outline button had two different sizes.
|
In afternoon, section 5 is drastically different when comparing the pull request and Figma, so I have not touched it. |



Description
Adds combined variations remaining in #193.
I had to change the hues and order of some color palettes for the section styles to work. I'll update the Figma with the new colors.
Screenshots
Evening:
Noon:
Afternoon: