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 Slack channel by following the instructions in our handbook.
Housekeeping
- We can still use more volunteers for note-taking. Along with this, there are 2 opportunities to participate by running triage sessions. This includes both the core and Gutenberg triage. Please leave a comment below if you’re interested.
- With daylight savings affecting different time-zones, we would like to know your thoughts on the current timing for the meeting. We would love to hear from you if you think that we need to make adjustments. Please leave a comment with your thoughts.
Gutenberg
Gutenberg 8.9.3 is here. @michael-arestad shared notes from the #core-editor chat:
- @karmatosed is working on iterating the options panel.
- Custom CSS is on the horizon for the Group block.
- @nrqsnchz is working on a feature to allow users to upload subtitles for a video.
- The Navigation screen has a few more proposals.
- The Widgets screen is ready to be implemented.
- @mapk is starting designs for the query block.
Updates
@ibdz reported that he is working on creating a WP-Admin Core library in Figma. Perfect timing to work along with #core-css that focuses on CSS Audit and CSS Scheming. Any update will be posted in the future meetings. ~180 unique colors in WP-Admin Core will be updated soon.
Discussion
@karmatosed suggested this meeting experiments with being 30 minutes for a few weeks. The idea like any could iterate and of course no time should stop conversation. Upon discussion she further suggested that we begin with the following changes:
- Move meeting to Tuesday only for Triage, combined.
- Try to have it focus on release this week: doing both in 30 mins.
- Make sure it’s just Triage, only issues need attention, not discussion.
- Move discussion issues to this meeting.
- Change this meeting to 30 mins from next week.
@michael-arestad asked, Are these updates useful? Most of the folks involved are in this meeting. Perhaps we could just do it like the #core-editor meeting where folks all share their update task-coordination-style.
@mapk and @nrqsnchz both like the idea of removing any burden from folks. Also it’s fine if each person comments what they’re working on and any feedback they need. This will get posted in the notes so more folks can chime in.
Other suggestions given:
- Posting the shortlist of tickets 30 min before Triage? So, there’s more room to read before discussion.
- Invite Ticket owners to the meeting, this could work if we manage to have a list before Triage.
- ASync Design Discussion, where an issue is pinned to the channel, that becomes the Async topic for say 6 hrs, where people can comment on a thread of that topic, etc. Then the issues could wrap up discussion during a regular scheduled meeting. This way, there are constantly new issues that can be discussed throughout the day/week.
@cameronduncalfe asked if there is a single file that has all the default Gutenberg blocks (frontend) in Figma? @mapk and @michael-arstad confirmed that Gutenberg blocks being complex and we don’t have a single file like that.
@aristath raised the following points for discussion:
- A discussion about font-family stacks for the new font-family picker in Gutenberg.
- A PR to allow using non-percent units for column sizes by changing the RangeControl to a UnitControl.
The 1st one will be nice for global-styles so users can select the font-families they need, while the 2nd one is necessary if users want to build a side-header layout in FSE.
@karmatosed suggested taking conversations to the issues probably is good, but great to keep eyes on in this regard.
Open Floor
@estelaris suggested to keep the impromptu Zoom meetings. Those are good when they are not on schedule and have a specific goal.
@karmatosed suggested to perhaps start APAC Triages or office hours? We have to consider that as a team we focus a lot on a certain timezone, as we grow how can we adapt?
@estelaris further added by emphasizing to consider that we elect team reps who are not both in the same time zone? That would help keep other time zones involved.