Design meeting notes for April 1st 2020

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack channel by following the instructions in our handbook.

@karmatosed started off with the announcement that @estelaris has been chosen as a new team rep for the design team! Congratulations! She will take on such responsibilities as facilitating team meetings, managing our task inbox and triage, and keeping everyone up-to-date on what’s happening in WordPress design.

Next, @mapk updates us on Gutenberg. WordPress 5.4 dropped recently which includes a bunch of neat Gutenberg improvements:

  • Default fullscreen mode.
  • New blocks: Social links block, Buttons block.
  • Inline text color change.
  • Gradients for Cover block and Buttons block.
  • Latest Posts now has featured images.
  • Color options on Group and Columns blocks.
  • Block breadcrumbs.
  • MOBILE: Toolbar stays on top.
  • Easier image sizing in Gallery.
  • Table block captions.

The focus for Gutenberg development in April was posted and includes:

  • Full Site Editing: Continue improving the Edit Site screen and blocks
  • Global Styles: This will be a big one this month (support in blocks and UI)
  • Updated Inserter UI to support patterns and blocks
  • Updated Navigation/Menus screen
  • Continue G2 iterations

Then, @ibdz chimes in with an update on the Figma documentation for the Handbook. This is intended for new contributors to understand our process of designing in Figma. If you have experience with Figma, please leave your feedback in this doc. We will review next week and then put it in the Handbook.

Next, @audrasjb asked us to review the design of the automatic updates feature plugin, in order to get it ready for a merge proposal. More information can be read in this Make post.

Finally, @ibdz spots a tiny bug in the Handbook and @paaljoachim links to a small change to the block toolbar for review.

#meeting-notes

Design Meeting Notes 18 March 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’s agenda here. You can join the Slack channel by following the instructions in our handbook.

Housekeeping

Spring forward begins next week! We are also looking for nominations for design team reps, nominations will close on 27th March.

Updates

@mapk mentioned a list of items that need focus to finish the full site editing project. If you are for looking into contributing with your own design, reviews or drop in any feedback, there is also our Project Board.

Open Floor

@joyously requested a review of the forums page as it needs a new design to make it easier for users to navigate.

@notlaura checked with the design team if there are any specific points that need to be addressed by the CSS audit of wp-admin, as discussed in the #core-css team

Below are some tickets to leave comments and recommendations, or drop by the @core-css meeting on Thursdays at 10:00 pm (UTC+01:00) on Slack

@ibdz would like to add Figma resources to the Design Handbook and more advice for new contributors who want to get involved. @mapk and @karmatosed to draft a post to say what we are doing and propose opening the design flows.

Design meetings are:

  • Core/meta triage: Monday 17:30 UTC
  • Gutenberg triage: Tuesday 17:00 UTC
  • Design Team: Wednesday 19:00 UTC

#meeting-notes

#meeting-notes

Design meeting notes for 11 march 2020

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack channel by following the instructions in our handbook.

As nobody objected, we’ll be moving the meeting time forward one hour starting from the meeting on March 25th, to compensate for Daylight Savings Time.

There is a call still open for triage and notetaking volunteers. Reach out to @karmatosed for core design triage or @mapk for Gutenberg triage if you are interested.

@mapk brings a flurry of Gutenberg news. Version 7.7 is out, and more details about the work on full-site editing were published. It would be great if people could test the new UI and Block Patterns that shipped with 7.7.

@karmatosed proposed a once-a-month video meeting instead of the regular design chat in Slack. It could help people stay in touch in these work-from-home weeks, and offer a bit more loose design hangout. All were in agreement, so we’ll give it a first attempt at the last meeting of the month, which is also March 25th.

@ibdz asks where to find design resources for the new Gutenberg UI (G2) that launched with 7.7, and the Figma resources can be found here, with iterations happening here also. A page in the Handbook as overview of all Figma resources was suggested.

@paaljoachim brought an issue with a suggested improvement for the new fullscreen editor experience. More data about how users are grappling with this fullscreening of the editor by default would be nice to have.

#meeting-notes

Design meeting notes 19 Feb 2020

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack channel by following the instructions in our handbook.

We start off thanking @joshuawold for his incredible work as a team rep. He is taking a well-deserved break, and we hope to see more of him in the future.

Next up, @karmatosed suggests we create a page in our handbook that describes our team processes. Workflows, resources, and also things like how contribution badges are awarded. Our process for this has not been the most consistent. It was discussed what the criteria should be for awarding a badge, and that we should do it on a regular basis. @mrMark suggested for example we could award a team badge after 15 contribution badges were earned in the past 30 days, though @folletto reminds us to not rely too much on rigid metrics alone, there should be room for the human aspect always. @karmatosed will write up a proposal for all this and we can iterate there.

Then, @mapk brought us updates from the Gutenberg front. Designs for full site editing are coming along nicely. Some issues that could use some eyeballs:

  • https://github.com/WordPress/gutenberg/issues/19204
  • https://github.com/WordPress/gutenberg/issues/20304
  • https://github.com/WordPress/gutenberg/issues/19886
  • https://github.com/WordPress/gutenberg/issues/20212
  • https://github.com/WordPress/gutenberg/issues/17335

A lot of things are coming together in this prototype, do check it out: https://www.figma.com/file/TR15iRvk7toGHnKb68QN1K/Full-Site-Editing?node-id=29%3A1016

@estelaris will soon report on P2 the findings of a working session at WordCamp Vienna to reclassify documentation into categories and subcategories to improve search.

@matveb shared an issue for the consolidation of WordPress icon usage. This touches on two topics: one how to lower the barrier of entry to making and updating icons (“input”), and one to make the new icons available in WP (“output”). There are a lot of different icons used now, no longer exclusively Dashicons. And the process of adding new icons is a bit unclear. Any thoughts on this are welcome to be shared on the issue: https://github.com/WordPress/gutenberg/issues/20284

Finally, @mapk needs someone to lead the Gutenberg triage next tuesday. Any volunteers are welcome to send him a Slack message. He’ll amend the Handbook page with more info on leading that meeting. It’s really not scary! https://make.wordpress.org/design/handbook/workflows/weekly-design-triage/

#meeting-notes

Design meeting notes for February 12th 2020

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack channel by following the instructions in our handbook.

Updates

@mapk started off by sharing an update on Gutenberg. Gutenberg 7.5 released! Some notable features:

  • Social links block
  • Feature images in the Latest Posts block
  • Inline text color options

@mapk also shared a post by Riad on February priorities for Gutenberg.

@nrqsnchz shared design iterations the team has been doing on the block library with a Block Patterns focus. This UI will significantly change the Block Library interface. Feedback is welcome!

Inbox

@estelaris shared an update on work for HelpHub pages. The team needs to find a way to organize the articles with the goal of creating better search. Check out the full Slack conversation if you’d like to help.

Open floor

Valentine Bora shared a few items in Meta/Forums that need design approval. Checkout the full Slack conversation for context and helping out.

#meeting-notes

Design meeting notes for Feb 5th 2020

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack channel by following the instructions in our handbook.

@karmatosed starts off asking for extra people to help run the triage meetings on monday, where we discuss open tickets and prioritize for the next release. Volunteers can speak up in the slack channel or via DM.

@mapk reports that Gutenberg 7.4 will be out soon, and it’s looking really good.

Next, @karmatosed asks for design feedback on the auto updates settings that’s new for 5.4. https://core.trac.wordpress.org/ticket/48850 Take a look at it and share your thoughts, this is an interesting new feature for WordPress.

@estelaris and @bph bring a design ticket for feedback. Helphup and Devhub don’t have a way for people to leave feedback on the documentation. This would add a comment form to those pages. @karmatosed advised simplifying the form and then iterating, and @michael-arestad had concerns about moderating, but the comments will not be shown publically clarified @bph.

Finally, @paaljoachim brings https://github.com/WordPress/gutenberg/pull/16014 to our attention.

#meeting-notes

Design Meeting Notes for 29 January 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’s agenda here.

Housekeeping

There is a call for volunteers for the Get Involved table at WCAsia. If you are attending, it will be a great opportunity to give back.

Updates

Gutenberg updates

@mapk is working on moving any design-related projects to the board on GitHub. If anyone wants to get involved and help shape the design of Gutenberg 5.4, there are several tasks that they can work on.

@kjellr invited the design members to attend the New Bi-Weekly Block-based themes meeting which will be a great opportunity for Design, Core and Theme teams to discuss the theme-related impact of full-design editing work in Gutenberg. Agendas and notes will be posted to the http://make.wordpress.org/themes

This was a short meeting due to #core and privacy meetings happening at the same time. We’ll be back again next week, in the meantime, please leave your comments.

Design meetings are:

  • Core/meta triage: Monday 17:30 UTC
  • Gutenberg triage: Tuesday 17:00 UTC
  • Design Team: Wednesday 19:00 UTC

#meeting-notes

Design meeting notes for January 22, 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’s agenda here.

Updates from any specific focuses

Gutenberg

@mapk shared that Gutenberg 7.3 was just released. There’s been a lot of improvements such as the Navigation block, the new Replace Media flow, new full site editing blocks, and a huge performance boost. 

Proposed design focus for the 5.4 release

@karmatosed and @mapk worked on a list of proposed design projects, tickets and issues to focus on for the 5.4 release that is coming up in February. Comments and feedback are welcome. The biggest item in need of design work is the editor, while most of the rest is providing design feedback.

Trello: what is in our inbox?

There was nothing new added to our Trello board this week.

Open floor

A few tickets, issues and PRs in need of feedback were raised. Please feel free to review them and add your comments:

#meeting-notes

Design meeting 8 January 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’s agenda here.

Housekeeping

Being this the first meeting of the year, we are looking for volunteers for 2 specific roles:

  1. Volunteers to be part of the notetaking pool for meetings. We rotate each week to spread the load
  2. We would like to train people to run triage sessions

And we got a volunteer for note-taking: @adampickering

Updates

Gutenberg updates

@mapk announced that Gutenberg 7.2 will come out today. @mapk will be running usability tests for the Columns block.

Also, designers are diving into full site editing!! There is a label in GitHub, so if anyone wants to talk through design ideas, leave your comments there.

Discussion

@karmatosed let us know that there is a repo for wordcamp.org that has a “needs design” label and needs our help. It is a great way to contribute by giving feedback or adding sketches as needed. 

Open Floor

@estelaris presented the first draft for the article page for HelpHub, the prototype shows the use of menus. Feedback was requested on:

  1. Avoid using hamburger menus
  2. The Documentation menu (blue block), is it possible to be expanded? 
  3. The Topics section at the top to help the user find out the information presented without having to scroll down unnecessarily

Feedback given:

  1. Avoiding hamburger menus is a +1!
  2. The menu in the blue block can be expanded, increase the font size and the padding to give eyes space to rest
  3. The topics section is a good solution, try other design treatments for the block
  4. Overall, increase the padding and/or line-height to create white space and do not use many font-sizes
  5. Do not use all-caps for titles

A new draft will be presented to the #design team next week and a P2 is planned after the #docs team provides the final sub-categories to open the design to public feedback.

#meeting-notes

#helphub

Design Meeting Notes for 11 December 2019

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.

Housekeeping

Although not everyone celebrates the same seasons or holidays, @karmatosed suggested to let next week’s 18 December be the last meeting of the year and meet again on 8 January.

To recap, next week will be the last regular triages and meeting of the year to reconvene in the first week of January. And if you don’t take a break, feel free to triage at any time. Leave a comment if you don’t agree or have another suggestion. 

Updates

Gutenberg updates

@mapk announced that Gutenberg 7.1 was released. A new feature is the Welcome Guide to replace the Tips for New Users. To read more about the new release, read here.

@ibdz gave an update on team profile badges. He chose the badges for Triage and Security. He did some research about unique color selection for those badges, sorted out from current badges. After matched those colors in the color wheel and chose some unique colors. See the images below:

Proposed new badges for new and upcoming badges. The shapes were selected from Dashicons that represent the teams. There are 3 shapes x 3 colors for each team.

Proposal: shapes and colors for Triage and Security badges

Please leave your feedback in the comments. A meta ticket will be open for the change of color in the Security badges. 

Redoing the colors for all badges feels like a good progression for this work. @ibdz and @melchoyce will collaborate.

Open Floor

@levinmedia brought up the Figma WordPress/components library that needs updating to current 5.3. @karmatosed mentioned that we have a process to update WordPress components.

@levinmedia finds the proposals page a bit formal for updating the components to match what already exists. If not proposing anything news, he suggests that the best approach might be to update components directly on the components page without publishing. Then, prior to publishing, enlist people that are familiar with Figma and the components to review and ensure they’re an accurate representation of what’s in code and adhere to Figma best practices. 

One thing to keep in mind if we copy or build updated components on the proposals page, existing components will not be linked anymore. When the new, updated components are published, the existing ones that are already in use won’t update. They’d have to be deprecated. Old components won’t vanish from an existing design, but they would need to be manually updated. Expect a make/design post to expand on this.

#meeting-notes

#meeting-notes