Design Team Meeting Notes July 01, 2020

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 agenda here. You can join the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel by following the instructions in our handbook.

First, Housekeeping. We can still use more volunteers for note-taking and triage leading. Leave a comment below if you’re interested.

Next, @michael-arestad brings 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. https://wordpress.org/gutenberg/ updates:

  • Gutenberg 8.5 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. will be released on Monday and will be the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. going into WP 5.5.
  • @noah has been busy working on the Figma library
  • The new template issue could use some feedback
  • Image editing is available with this update
  • @annezazu published for the FAQ for the FSE outreach experiment.

Requesting everyone to provide any feedback that can be given to the new template issue as the team is busy right now pushing as much as to be prepared for WordPress 5.5.

@noah and @ibdz reports on the update for WordPress Figma Libraries:

  • Updates are on the way to incorporate the new 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. Editor patterns, as well as some general cleaning to make these more relevant
  • @noah is building out the new elements in a page called “In Progress” in the Components and Patterns files. Various icon libraries is also being brought into a centralized location, which can be found here: https://www.figma.com/file/3O5hl33MYt8YPWcRWWuwNv/WordPress-Icons
  • @noah will write a p2 post on ‘Improvements to the Figma Libraries

@ibdz has been exploring some workflows to automate the process. Currently testing and experimenting with React-Figma but the result is still far from expectation.

Discussion

In regards to HelpHub @estelaris wrote a p2 post trying to define users and categorizing the articles into 4 big pillars (these are not final yet). @mapk suggested the following categories:

  • WP basics – overview, features, history, glossary, semantics, contributing.
  • Technical documentation: installation guides, requirements, best practices, technical how-to, security, troubleshooting.
  • Support documentation – dashboard structure, user permissions, screens, media screens.
  • Project related documentation – customization, themes & plugins, design how-to’s (blocks):

Open Floor 

  • @joen created a new WP-Admin color scheme “Modern”. It’s ready to merge and brings high contrast blue colors as well as some consistency with the new Block Editor colors. The patch attached to the ticket purely provides an optional color scheme called “Modern”, and it is not a default scheme. If it were to become default in 5.6, it needs to go through the ringer on many levels. It primarily does 2 things:
    • brings darker background color to the menu, and a lighter text color, increasing contrast.
    • adds a new spot color, a rather luminous blue that has great contrast properties against white.
  • @ryrlle brought in a Github PR that adds a “private content” container block so that the organizers can share content only with people who have bought tickets. For example, online event organizers want to be able to share Zoom links without worrying about zoom-crashers. @estelaris is looking for input on the editor view of the block.
  • @joedolson is currently working with @nrqsnchz and @ryelle towards the issue associated with 49999.
  • We are also seeking feedback on the tickets 50169 & 48894.

#meeting-notes