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 make.wordpress.org 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: https://d.pr/i/ExTJ3o)

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.

#meeting-notes