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 Agenda for Wednesday 18 March 2020

This is the agenda for the weekly design chat on Wednesday, 18th March 2020 at 19:00 UTC

  • Housekeeping
    • Notetakers and triage volunteers
  • Call for Design Team Reps
  • Updates from any specific focuses
  • Discussion
  • Open floor

This meeting is held in the #design channel in the Making WordPress Slack.

If there is anything you would like to see added to the agenda, please leave a comment.

#meeting-agenda

Design Meeting Notes for 4 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.

Housekeeping

There is a reminder about Daylight Saving Hours. The proposal is to move forward meeting times by an hour on March 29. If people would also like a different time that is an option. Leave your comments at the bottom.

The design team is looking for notetakers. It’s imperative for the global community to share the notes on our meetings async. If you need any information, reach out to @karmatosed or any member of the team.

A second call is for triage volunteers, either core/meta or Gutenberg. @karmatosed and @mapk can help.

Updates

Several PRs got into WordPress 5.4 RC 1 on 3 March. The improvements coming in WordPress 5.4 include:

Some other work that needs ideas, suggestions and your design skills:

https://github.com/WordPress/gutenberg/issues/20345

https://github.com/WordPress/gutenberg/pull/20354

https://github.com/WordPress/gutenberg/issues/20631

Open Floor

A question was raised whether if the design team maintains discussions on Figma as opposed to GitHub. The design team doesn’t have much discussions on Figma, we try to maintain the discussions on either the PRs, GitHub or the Slack channel. But comments or design iterations are welcome. If you need access to the Figma account, please request it on the Slack channel.

@joyously presented an idea to link areas of an image to a URL. Some members recommended a plugin or to look for a third-party block. It would be a great enhancement to add.

A topic for discussion: the overall state of the UI elements in Figma. Feel free to add your comments below or leave them in the Slack chat.

Design meetings are:

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

#meeting-notes

#weekly-design-chat

Design Meeting Notes for 26 February 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

We are still looking for volunteers to help run meetings and triage, as well as notetakers. If you are interested in helping, lets us know in the comments.

Updates

Updates

@bemdesign shared an external post with us to show how much we have improved on Gutenberg and the positive effect that it has had on the community

We also mentioned that WordPress 5.4 Beta 3 was released yesterday and invited contributors to help with testing and bugs.

It was also shared a post on the Findings in the reclassification of WordPress.org documentation and mentioned that contributors have been working since WordCamp Vienna on it but we still need more contributors to help reclassify the 170+ articles.

Open Floor

@bemdesign invited the design team to participate in accessibility bug scrubs on Fridays at 15:00 UTC, followed by a team meeting at 16:00 UTC

This was a short meeting due to a lot of traveling happening within the WordPress community. 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 agenda for Wednesday 26 February 2020

This is the agenda for the weekly design chat on Wednesday, 26 February 2020 at 19:00 UTC

  • Housekeeping
  • Updates from any specific focuses
  • Discussion
  • Open floor

This meeting is held in the #design channel in the Making WordPress Slack.

If there is anything you would like to see added to the agenda, please leave a comment.


#meeting-agenda

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 agenda for Wednesday 29th January 2020

This is the agenda for the weekly design chat on Wednesday, 29 January 2020 at 19:00 UTC

  • Housekeeping
  • Updates from any specific focuses
  • Discussion
  • Open floor

This meeting is held in the #design channel in the Making WordPress Slack.

If there is anything you would like to see added to the agenda, please leave a comment.


#meeting-agenda

Design Meeting Notes for 15 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

Last week there was a call for both notetakers and triage facilitators. The call is still open, if you are interested, leave a comment after these notes or announce yourself in the #design Slack channel.

Updates

Gutenberg updates

@mapk let us know that the workaround full-site editing is moving forward. Several issues have been identified and Gutenberg designers are reviewing UX flows in relation to these issues. 

Other specific works happening around Gutenberg include usability testing on Columns blocks, more work and design for Navigation block and global styles.

Discussion

@karmatosed open discussion around WP 5.4. And the list created of items the #design team would like to include. The list is very optimistic and needs prioritizing.

We ask people to review the list and let us know in the comments what do you think should be worked out for 5.4.

Open Floor

We reviewed two tickets: #48850: Plugins Screen: introduce “Automatic updates” column/option and #49199: Introduce Automatic update opt-in setting for themes. Both tickets are part of the 9 priorities for 2019-2020.

We talked about options in text and toggles like “on/off”. See examples on the Slack chat. You can leave your thoughts on both tickets. @kjellr is back and retaking the topic of how themes work with Gutenberg. Follow up his experiments on the mentioned repository. In the future, there will be more updates in #themereviews and make/themes if people want to follow this topic.

#meeting-notes

#auto-update, #gutenberg, #volunteers

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 18 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

There are two things: @boemedia is stepping down as a team rep. She still be active as WordPress contributor. We want to thank her for being a team rep and her work/support.

Second, today is the last meeting of the year. We will take a holiday break and return on 6 January as our first meeting of 2020.

Updates

Gutenberg updates

@mapkt reported that due to holiday break, there will be no #core-editor meetings or Gutenberg releases until 8 January.

@mapkt together with @aduth reviewed the complexity behind renaming categories for the Block Library. Words are not easy to find, especially when plugins are already using some words. 

Updates

Preparing for 5.4.

@francina asked the #design team if there is anything to be included in 5.4. Ideally within a day or two so a post can go out before the holidays. @karmatosed created a spreadsheet to collect issues/tickets and ideas. @mapk will add any Gutenberg issues and there are already some tickets in trac. If this method of a sheet works, it will be added as a process in the handbook.

The tentative deadline for 5.4. is March, which means we will have about 6 to 8 weeks to work. Not all the items posted on the list will make it, but it will be good to start tracking them. A few suggestions to be considered now are background support to columns, color and typography items.

@shaunandrews mentioned the proposal to simplify the block selected state and @melchoyce would like to add both or at least of @davewhitley’s proposals on a new color palette for WordPress and a consistent spacing system. Another item would be around improving the selected/focus states for blocs

@michaelarestad brought up the site navigation when editing full site. The main goal is to have a one-cohesive, tightly-coupled system rather than multiple disparate interfaces.

The post will come up next week, so we have until Friday 20 December to add items, proposals or ideas to the spreadsheet.

#meeting-notes