Decide which CSS custom properties will make sense for the Block Styling System

[Aljullu]

We are planning to support the new Gutenberg Block Styling System (see #2403). In phase 3, we will register some CSS custom properties so themes and users can hook up with our blocks and style them without the need to write CSS selectors.

We should discuss which CSS custom properties to create with designers and have a plan for them.

See @nerrad's and @haszari thoughts on this:

#2403 (comment)

• With css variable naming, I think we should try to avoid being too specific with variables (eg --wp-gs-wc-block-order-summary-item--border--color). To bring consistency we should identify common shared elements across all the ui/ux and name variables according to those elements, so for example the above example might become something like --wp-gs-wc-block-panel--border--color. The more specific we get in variable names, the harder it is to maintain consistency across the design of the blocks. This is where you can likely align with some of the work being done this sprint in finding those inconsistencies and fixing them.

#2403 (comment)

I agree - we should strive to name our colours/variables with high-level semantic names as much as possible.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Remove the stale label or post a comment, otherwise it will be closed in 10 days.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[Aljullu]

I don't think there is anything actionable related to this. Closing in favor of #5267, where we are working on adding global styles to WooCommerce blocks.