Want to get involved? See the handbook and optionally drop into #design to chat. Most active design work happens in the block editor project, consider dropping into Needs design or Needs design feedback.
There’s a WordPress Component Library in Figma. Duplicate to edit, direct access is reserved for the design team.
The real goal for today was defined as collecting examples of other CSS style/standard guides (perhaps especially in regards to property ordering) and identifying what exactly needs to be standardized. Thoughts are currently being collected on this Codex user page. We should work on it throughout the week and then at next week’s chat discuss any dividing points and find a path to agreement. Standards will help us with future maintenance and creating/reviewing patches, so while a clean up may not necessarily be undertaken just to meet standards (much like PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. code bits are not patched just to space out some parens), we can adhere to them as we do other CSS tasks.
This sort of work really has to happen 3.5-early(-early) after the stylesheets settle but before they start moving again. A good approach may be to assign sections of the giant admin sheet or other smaller sheets to individuals/teams to comb through and clean up based on yet-to-be-determined guidelines. There is likely quite a bit of unused CSS in the stylesheets, but care will need to be taken to absolutely ensure that something isn’t being used before removal. azaozz also suggested that we also strive to have all basic HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. elements “work out of the box” in the admin by declaring general styles for tag selectors. If this is done, we should also make sure we look through the rest of the CSS and remove declarations wherever we can. wp-admin.dev.css is a monstrous 8000+ lines – let’s try to get it leaner wherever we can.
I proposed something that’s been briefly discussed here and there, which is the merge of colors-fresh (gray) into the main wp-admin stylesheet. There are some very valid concerns here regarding actual maintainability that need to be thought through. It seems that the real first step here is to get colors-fresh and colors-classic (blue) synced up again. Ideally, making changes in the two would happen on the same numbered line, which doesn’t currently seem to always be happening. A possible merge should either not significantly bloat wp-admin.dev.css or actually make it smaller, thanks to shorthand properties. Whether or not this happens, though, one of our goals for 3.5 should be to work with the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) group to create a high contrast theme for the admin.
