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 agenda for Wednesday 4th March

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

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

X-post: Daylight Saving Time Meeting Planning

X-comment from +make.wordpress.org/updates: Comment on Daylight Saving Time Meeting Planning

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

Gutenberg Phase 2 Friday Design Update #45

Happy Friday! The Gutenberg plugin has gone through 2 weeks in a row of releases earlier (7.4 and 7.5) due to the beta release of WordPress 5.4. However, we did not have a release this week. Our next RC for Gutenberg will be on this coming Monday with an expected release for Wednesday. We’ll then continue with our bi-weekly release schedule.

In those two releases, we saw a myriad of features:

  • Added text color options to the Group block.
  • New link UI for adding links to text.
  • Background and text color support for the Columns block.
  • New Social Links block.
  • Added inline color to specific words within text.
  • Added featured images to the Latest Posts block.
  • And everyone’s kid’s favorite; TikTok embed support.

Full site editing

Full site editing is experiencing TONS of mockups and UX flow explorations right now. Check out the Figma files to see the work happening there.

Template-part selected state as seen in the GitHub issue: https://github.com/WordPress/gutenberg/pull/19929

Global styles

The Global styles team has narrowed down the Minimum Viable Product (MVP) to just get some basic global styles into a “sidebar” interface for now. Mockups and prototypes are still being built around improvements.

It’s been recently broken down into more detail here: https://github.com/WordPress/gutenberg/issues/20331

Block patterns

We’ve also decided to trim down block patterns UX to an MVP as well. This will most likely begin as a sidebar that allows the selection of block patterns to be inserted into the content. Turns out attempting to redesign the Block Library will take more development effort. We want to get patterns in sooner, so an MVP feels the better way to go.

Block Patterns future UI

Lions, Tigers, and Sidebars! Oh my!

If this sounds like a lot of sidebars to you, we hear ya! It’s a quick way to test interactions out, get some feedback and forward direction. We understand that some of this work isn’t the ideal scenario, and everyone is working to improve it. Thank you so much to everyone contributing!


Get involved

Now’s a great time to get involved. While the work on this project is intense, it’s always important to glean new perspectives from other WordPress users and community members. Just drop into any of the links provided above to read up on the details and contribute.

Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Iterating the about page

As discussed in this week’s meeting, let’s work together to iterate the design team about page. Along with editing and updating the content, adding notes on the way the team works and types of work might be great.

What do you wish you’d seen on first coming to this team? What could be helpful for other teams to know on this page?

If you’d like to help, dive right into this document and let’s work on this page together.

Along with this page, are there any other pages you think would be great to update in the handbook? Leave a comment on this post if there are.

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 agenda for 19 feb 2020

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

  • Housekeeping
    • Design team and contribution badges discussion: let’s get a process!
    • How we work page proposal idea. A suggestion to improve the team handbook about page with more information about how we work as a team.
  • Updates from any specific focuses
  • Trello: what is in our inbox?
  • Discussion
    • Consolidating WordPress icons
  • Open floor

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

Leave a comment if you would like something reviewed, discussed, help or something added to the agenda.

#meeting-agenda

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