Design Share #67 (Oct 21-Nov 1)

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.

If you have updates you’d like to include in the next Design Share, drop a note in the #design channel. If you have questions, you can also ask them there, or as a comment on this post.


General Updates

“Show template” option

Status: In progress | @joen

A suggestion for adding a “Show template” option to the view dropdown. Issue.

A dedicated Styles screen

Status: In progress | @joen

Continuing with the proposal to bring a dedicated global screen for styles, small tweaks were added based on the ongoing conversation. Issue.

Editor Comments

Status: In progress | @joen

Continuing with the collaborative effort to bring 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. comments to the editor. Issue.

Ambiguating Write/Design tools

Status: Conceptual | @joen

Two options for bringing more visual differentiation between tools. Issue.

Photo Directory

Status: In progress | @fcoveram

After sharing the first proposal, we began iterating parts of the design and polishing the idea. Our latest decisions involved dismissing Profile area and move the “random” feature to a separate banner in the photo details page.

Make’s homepage

Status: In progress | @fcoveram

Today, we started exploring a visual representation of the community behind WordPress in the hero section of Make’s homepage. The current photo is from years ago, and our challenge is to depict the community through a timeless graphic. The outcome will be share in this ticket.

DataViews: Density preference

Status: In progress | @jaykoster

Depending on the data set or configuration of field visibility browsing a data view could be more ergonomic if the information was more or less densely composed. A new option (similar to the ‘Preview size’ option in Grid layout) can enable users the ability to further configure the appearance of data view tables. Follow along in this issue.

Advancing the Pages data view

Status: Conceptual | @jaykoster

Initial concepts for updates to the Pages data view including visualised hierarchy, dynamic pages, new filters, quick-editing, and updated visual design. Find out more in this issue.

Global styles iA exploration

Status: Conceptual | @jaykoster

A high-level look at how the Global Styles interface might evolve as we build out the Styles section in the site editor. Check out this issue for more information.

System Updates

As part of efforts to advance the WordPress Design System, the following are visual updates to this effort.


Updating active menu item styling in the site editor

Status: Needs feedback | @jaykoster

A problem with the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. in the site editor is that the active item has a blue background and white text, which identically matches primary button styling and potentially leads to confusion. In this issue we’re exploring alternative approaches to the active (and hover) style treatments.

Badge component

Status: Needs feedback | @jaykoster

As the site editor evolves there have arisen several situations where ‘badge’ elements have been utilised. In this issue we’re exploring how this can be formalized as a reusable component.

Updated Figma Library

Status: In progress | @jaykoster

Work is under way to update the WordPress components Figma library, to be distributed via Figma Community. More on this soon 🙂


#design, #design-share