Design meeting notes for May 30, 2018

The full transcript of this meeting is can be found on Slack.

Since last week, we slightly changed our meeting structure, starting with incoming calls for design. This way the actual design requests get more focus. When there’s time left, we discuss other topics or projects we’re already working on.

  • The core-php team requests design feedback on #43986.
    We discussed the screenshots and found there’s a lot of information in a small window. Summarized, we have a few suggestions that we will add as feedback to the ticket, together with a screenshot by @melchoyce, who originally designed the plugin cards.
  • The training team asks for an infographic for Github
    There’s a complicated workflow that the training team would like to clarify with an infographic. This ticket was adopted by @khleomix and new contributor@estelaris, props for that! Together with @juliekuehl, they will work on this.
  • The training team asks for design help for the learn.wordpress.org site
    This website has not been used since 2013 and needs some TLC.  The training team reached out to the design team to redo the website. As this is a fairly large project, there’s no set expectation for finishing this soon. It will either be a project of months. We discussed breaking this project into smaller chuncks, starting with research. Props for new contributor Andi who picked up this call to do initial research in the week coming.

Final question comes from @joyously who asks if we ever triage UI/UX feedback for meta tickets

@karmatosed says we haven’t done for a while, since the list of core tickets got out of control. She suggests bringing this in once a month and asks if anyone is interested in leading this, but no decision on this follows. The list has been added to the feedback section of the design handbook, so if you want to work on one of the tickets async, feel free to take a look.

Thanks everyone for attending and making this an interactive and constructive meeting again.

#meeting-notes