Design meeting agenda for Wednesday 3 October, 2018

The weekly design meeting is on Wednesdays at 17.00 UTC (see it in your time here). If you have anything else to add, please comment below or mention it on our Slack channel #design.

  • Calls for design
    follow-ups (if any) on our Trello board
  • Design ticket triage
  • Open floor – anything you’d like to share?



Design meeting agenda for September 26, 2018

The weekly design meeting is on Wednesdays at 17.00 UTC. If you have anything else to add, please comment below or mention it on our Slack channel #design.

  • Triage Inbox
  • Calls for design: follow-ups (if any)
  • Contribution day plan document: opinions and insights.
  • Open floor: we’ve not had one for a while, let’s have one! Bring your questions, thoughts, comments and insights.



Design meeting notes for August 1st, 2018

This week’s design team meeting was held yesterday at 17:00 UTC. You can catch up on the archive here.

Here are the summary notes:

  • There are no items to triage in our inbox.
  • There was an open discussion.
  • A weekly update on Gutenberg design was asked for and will be added.
  • This week Gutenberg released 3.4 and there is a weekly meeting still happening every week at 13:00 UTC on Wednesday’s in #core-editor. The project is in new feature freeze still but iterations and feedback is welcome.
  • 4.9.8 is due out and @joshuawold talked about what the experience was like for him and gave his insights from co-leading.
  • A final mention is worth adding of the #core-test channel and where you can find usability testing for the project.

You can join the chat each week in #design at 17:00 UTC on Wednesdays.

Design triage learning session on August 6th

During the weekly meeting a week ago, there was interest in having a video learning session using Zoom for design triage. This would be how to contribute using both Trac and also GitHub for Gutenberg. It is aimed at being for designers who want to learn more about what triage is and how to use Trac and GitHub, but anyone is welcome.

Some points suggested to cover are:

  • What the life is of a ticket or an issue.
  • What labelling means: specifically what ones designers need to know.
  • How trac works for tickets.
  • How GitHub works for Gutenberg issues.
  • How design triage sessions work.

The session with be on August 6th at 16:30 – 17:30 UTC. This will run instead of the usual triage session and be an hour long. Zoom will be used for the session over Slack, the idea being to ‘see’ and screen share.

A link will be given as a comment here and in #design before the start of the meeting. You will need to have the Zoom software installed to join.

In order to make this a session that everyone attending gains the most from I would love to know what you would like to see covered in this session. The session itself will have a format but questions along the way are most welcome.

This week’s design meeting agenda for January, 25

This week’s #design meeting is happening Thursday, January 25 18:00 UTC.

This weeks agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack


Design meeting summary January 18

TL;DR – We just had a really productive meeting where we touched on design needs, adding some structure to the work the design team is doing, as well as reporting on all the awesome stuff getting done. Interested in helping? There’s something here for you!

Below are the exciting things we covered in the meeting!

Calls for design

We’re looking for help, if you think you’re a match please reach out! If you have a call for design yourself you can add it as a comment on this post or join the weekly #design meeting and we can discuss after covering other items.

  • Design a featured imageA new blog post is will spread the word about to encourage folks jumping in and helping. The marketing needs someone to design a featured image for the blog post.
  • Design interface for plugin/theme compatibility with Gutenberg in WordPress admin – Now that Gutenberg is getting closer we need a way to reflect in the WordPress admin whether a plugin or theme is compatible with Gutenberg. This is a perfect ticket for a designer who’s interested in supporting a few hours a week for the next month on UX work related to sketching out ideas and figuring out how this would look.
  • PHP Servehappy project – Servehappy had been officially approved as a feature project for WordPress. We need a designer to work with the development team on what a page would look like talking about this project. In particular the design needs to present this linked content. The person doesn’t have to be technical as that could ensure the target market is reached correctly. However, it’s important that they are able to connect with the development team to bridge the gap of communication between what the team is building create and what users need.
  • Create a dashicon for WordPress Coding Standards. We need someone to create a new dashicon! That’s a ton of fun for the right person. You can more about dashicons here and here and here’s a tutorial on making one. If you’re interested this could be perfect for you.
  • Improve the content of the Grey Box™ on the Design page – It’s supposed to be a welcome to the team and sharing more about how to get started. Link to edit screen.
  • Plugin search – The team is working to identify what information will be good to use for filters and how to present that information. The plugin directory has been recently redesigned, so it will be important to take that into consideration (and not undo all that work) when helping the team add search filtering to the design.

If you’re interested in helping reach out to Tammie Lister or Mel Choyce and they can connect you. Or you can comment in the Slack channel on the specific request (make sure to checkmark “also send to #design” if you do, so that it doesn’t get missed:

Structure of the design team

  • Trello board – We’ve created a Trello board to handle any issues that aren’t in Trac or Github. We had a great discussion about how the Trello board can be structured, how cards can be labeled, etc and ended on a good point for today. We’ll also discussed the need for folks to post to it. This board could ultimately replace the calls for design page on Make, with that page linking back to the Trello board.
  • We also have a Start Here card that will need some love. Then whatever happens here should get updated back into the design handbook.
  • It was also noted that it could be helpful for handbooks to start looking more like the Gutenberg one.

Monthly recaps

We’re going to start moving from weekly calls for design updates to instead posting a monthly summary based on the weekly #design meetings.@joshuawold and @boemedia will post the summary, and if a third person wants to help out we won’t say no! 🙂

Next steps

If you’re still reading this, and haven’t yet felt you can make a contribution to the design of WordPress, we can emphatically answer that you can! It might feel a bit overwhelming on where to start, the easiest way is to join the next #design meeting and look for an opportunity to give your support, or grab one of the calls for design issues above and jump in.


This week’s design meeting agenda for January, 18

This week’s #design meeting is happening Thursday, January 18 18:00 UTC.

This weeks agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack


Design meeting summary January 11

This is the design meeting summary of January 11, 2018. (Slack log)

In attendance were: @karmatosed, @boemedia, @mapk, @cathibosco, @mizejewski, @melchoyce, @joshuawold

We discussed the following:

Trello triage
Because the Design Trello board is a road map, last week we discussed it would be good to triage the lists and see how we can improve the board as a general guidance for new and exsisting contributors to the WordPress design team.
We will triage a few lists each week.

This week, we discussed the following lists/cards:

  • In general, if people add cards, it would be good if they give them a little more explanation on what they want to accomplish. It’s also important that everyone who is assigned to a card, does update.
  • It should also be ok for people adding themselves to an issue and also ok removing themselves.
  • Anyone who wants but doesn’t have access to the design Trello board, please send a dm to @karmatosed or @melchoyce on Slack
  • List: Outreach
    The idea of reaching out to other communities came from the Community Summit. People were able to share resources, help each other out, and the relationship was pretty beneficial to both sides.
    A list of non-WordPress conferences was created on the Trello board, where we can save interesting conferences for designers.
  • List: Structure
    *Card: ‘Creation of resources for handbook’ was changed to ‘Suggestions of resources for handbook’ (moved to handbook-list). On this card, people can drop suggestions for the design resources pages in the design handbook. Please fill these up as with as much information as possible.
    Once added to the page, the suggestion should be moved to the Trello list ‘done’. (or do people get rights to add the resources to the page on themselves?) -> not decided on yet.
    *Card: Improve Grey (former blue) box
    @Mapk will add some info on the card, including more description and details to make it more understandable for new contributors
    Let’s make it better and find inspiration on other team’s pages.
    *Card: buddy system for new contributors
    This idea was created in July 2017, but never got followed up. From here, we started discussing the status of cards should be added. Therefore, cards should be labelled.
    Action: create label system for Trello cards
    Label suggestions:
    • In progress
    • Need discussion/meeting
    • Good first issue (or our wording of that)
    • Needs decision on next step?
    • Needs help

    *Card: Comprehensive list of contributing designers
    The idea of this was ‘leave no designer behind’. Right now it’s hard to know who is doing what. If they are lonely, if they need back up, if they are just rocking and we should shine a light on them.
    There’s a Google doc with details of design contributors. Let other design contributors fill this out and pass it around on Slack (action for @karmatosed?)

It was a great meeting, thanks everyone for actively attending.
Discussing the Trello board took longer than expected. Therefore, the other 2 topics on this week’s agenda will be moved to next week’s meeting on Thursday.
The call for design by Maja Benke will be discussed in Monday’s Triage session, 17:00 UTC.

@mapk ‘s call for design on illustrations and the About-page was discussed on meeting – the sequel. You can follow this discussion on Slack.

See you next week on Thursday, January 18 2018 18:00 UTC!


This week’s design meeting agenda for January 11

This week’s #design meeting is happening Thursday, January 11 18:00 UTC.

This weeks agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack


Design chat summary December 4th

Howdy! Below are the summary notes from our #design meeting this past Thursday.

Volunteers covering weekly meetings

We discussed the previous post for volunteers to help support the design meeting(s) @boemedia and @joshuawold will cover the Thursday meeting going forward. The definition of what the role entails was discussed, and we created a doc to outline responsibilities.

In the future we may automate some of this, but for now we’ll keep it manual.

We also still need 1-2 more people to help cover the weekly triage meetings. Right now we have a few folks who’ve volunteered on a part-time basis (@boemedia, @joshuawold, @jamestryon). It was also noted that one meeting a month could be devoted to looking at things like the Trello board and the Calls for Design post.

Plans for 2018

We briefly discussed the goals for the #design team in 2018, and a need for a better system to capture where the team can support the efforts of WordPress.

A few points we touched on:

  • Profile pages – they need some work
  • Seeing everything at once – It’s hard to see a clear overview of everything going on. The #design Trello board offers a potential for covering this, but shouldn’t be the only source of truth. We also discussed how mentoring, and changing the format in Trello could help.
  • Helping other teams share what support they need – The big thing to crack is how to get teams to tell us what needs to be done. There’s a few things out there, such as the Trello board, and the Calls for Design post. It could help if someone volunteer to own either of these.
  • Getting started in #design – We briefly touched on the barrier to getting involved with design in WordPress. It’s hard. This is a general encouragement for anyone interested in helping with design.

Your help is valuable! If you’re wondering whether your support would make a difference, then the answer is yes!

Interested in helping out? Here’s a few Trello items that would love some attention!


There’s two meetings happening every week. If you want to help out in leading them let Tammie know, otherwise if you just want to be part of #design please jump in and join us. There’s a lot of excitement about getting more people involved in design. Let’s make 2018 awesome!