Design meeting summary for Wednesday May 23, 2018

Howdy! Following are a few of the takeaways from our meeting today, based on the previous agenda.

  1. Simpler agenda – The agenda has been streamlined. This is based on recent feedback, and more would be welcome as we try to hit the right balance of making things clear and getting things done.
  2. Defining design – We’re recognizing a trend in a lot of the tickets we’re trying to support on and tackle. We often run across problems that have been called out, but aren’t easily explained. As a design team we can start to won some of these tickets by clearly articulating (and encouraging others outside of the design team to do the same) the problem in a visual way. The ideal is that as someone new to the ticket (or coming back for the 10th time in as many years) I can get the basic gist of the ticket in a 10 second glance. Sketches, videos, screenshots, very simple bulleted lists, these are some of the ways to tackle this.

Calls for design

  1. Future private posts listed as already published with future date specified – We chatted about this issue and recognized that we couldn’t easily explain what was going on (without taking the time to dig in deep). A comment showing the current state of the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party will go a long way towards helping us to figure out where to take it next. You can follow the conversation we had on Slack.
  2. Tweaks to menu setup page – Similar to the above ticket, we need to make sure we understand the current state, and then propose a better future state. Putting out a call for anyone who is interested in doing that. If it’s your first time please reach out to anyone on the design team and we’ll be happy to guide through that process. Honestly it’s a ton of fun! There are many examples where someone from the design team was able to do that. You can also follow the Slack conversation we had today.
  3. Error 500 when a user has too many sites – Could use some design team love. If anyone can volunteer to make a tl;dr video clip of the problem it might move the conversation forward. View summary.


  1. Onboarding new contributors – You can follow the Slack conversation. We discussed the best way to onboard new folks, and had some suggestions on how a bot could be used to make that process better (without being obtrusive).