Design meeting notes June 17

These are the weekly notes for the design meeting that happens on Wednesdays. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel by following the instructions in our handbook.

First up, housekeeping.

We are still looking for volunteers to take notes and run triage (either coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. triage or GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. triage). If you are interested, leave a comment!

Next, @michael-arestad showers us with updates:

Gutenberg design update:

  • There is a new proposal for integrating the media uploader/inserter into Gutenberg. It will be discussed in the #core-media channel June 18th at 4 PM UTC.
  • There have been some minor updates to the “Add template part” flow moving closer toward the proposal here.

Core CSS meeting recap:

  • Discussion was centered around naming conventions and possibilities for complexity of variables
  • All colors in the wp-admin should be controlled by the color schemes
  • There is a plan to come up with color “buckets” to prevent us from having to target every use of a color individually when writing color schemes
  • Here’s a cool experiment from @ryelle that removes all colors
  • We did get a bit into naming and philosophies but not decisions were made
  • Chat will continue June 18th at 9 PM UTC in the #core-css channel.

Two calls for feedback this week, one from the Docs team regarding the External linking policy, and one for the WP notification center proposal. Please leave your comments on those posts.

For the discussion, we dove into how to improve and maintain our Figma library of design components. Main pain points are that it’s hard to navigate, not up-to-date, and nobody who’s responsible for maintaining it. @ibdz spearheaded a document to collaborate on and gather input from the likes of @noah @davewhitley @melchoyce, and YOU! If you work with Figma or another design library, leave your thoughts in that doc so we can figure this out.

Finally, @michael-arestad briefly discussed template parts in Gutenberg, and how to differentiate them from 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. patterns in the UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.. It’s hard because technically they are the same, but with different use cases. A post will be written soon with details.