[wp-trac] [WordPress Trac] #49930: Replace wp-admin color schemes with CSS custom properties

[WordPress Trac]

#49930: Replace wp-admin color schemes with CSS custom properties
----------------------------+-------------------------------------
 Reporter:  kburgoine       |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Future Release
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  ui, accessibility, css
----------------------------+-------------------------------------

Comment (by notlaura):

 We've been keeping track of the project status in
 [https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit#heading=h.wx53p8iotjz9
 this Google doc].

 As of December 9, 2021, our next steps and remaining tasks are:

 - Review and merge pull requests on [https://github.com/ryelle/wordpress-
 develop/pulls Kelly's wordpress-develop fork].
 - Once unified on a single branch, we need to look for duplication and
 opportunities to normalize and consolidate. A natural by-product of one
 author per-file is we didn't collaborate on naming and sharing properties.
 - We need to make some decisions around handling rgba() and box-shadow
 values.
 - We need to address PHP and JS files that need to be reviewed and
 appropriately upgrade to Custom Properties if need be.
 - We need to consider the best way for existing Core Admin Color Schemes
 to leverage this API.
 - We need concise documentation to explain what's been done, how to
 leverage it and methodology/guidance for other contributors to maintain
 and expand on this API.
 - We need to add the --experimental prefix prior to merge.
 - We need to set goals and ongoing tasks (if any) to address while the
 --experimental API is in the wild. We also need to set project and
 community expectations for how the experimental API should be leveraged,
 when we recommend not using it and how migration to a stable set of
 properties will happen. Should we have a fallback where we map
 experimental properties to stable ones? If so, should that be opt-in or
 temporarily opt-out with the goal to sunset?
 - Are there any properties that should permanently remain experimental,
 “legacy,” or “internal”? Where we wanted to address them today, but the
 intention is to deprecate over time as we move towards a normalized
 palette? Keeping a non-official prefix on them could signal that
 intention, discourage adoption and reduce risk of that deprecation being a
 surprise.
 - How can we provide examples (like the suggestion of new Admin Color
 schemes to demonstrate) and documentation to set this project up for
 success and communicate timeline?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49930#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform