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.
This is a bi-weekly update of work the design group contributed to. Work happens in overview issues, and in needs design, or needs design feedback issues.
The WordPress.org Forums, and the Pattern directory, are set to be converted to using blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes, and with that, slight color, font, and header updates.
Justified text is a constraint in some schools and newsrooms, so it’s something the editor needs to support. At the same time, it’s less legible, and should be applied all across a site rather than on a per-paragraph basis. These designs go with an issue that discusses this.
Further explorations in the initiative to merge the dark “Details panel” with the document Inspector. The panels have been abstracted so as to define their principles. The next step is to assemble examples for different contexts, e.g.; perusing the Inspector in the pages data view, experimenting with multi-document selection (similar to how the block inspector handles multi-block selection).
If you have updates you’d like to include in the next Design Share, drop a note in the #design channel. Most active design work happens in the block editor project, if you’d like to contribute directly, consider dropping into needs design or needs design feedback.
You must be logged in to post a comment.