Design meeting notes for July 4, 2018

There were several items this week that were not on the original agenda, so see the below notes and refer back to Slack

Triage Inbox

Design for page “Create a Website” on WordPress.org on Design team

  • there will be 2 versions of create a website — one longer and more involved and the other with a lot less copy
  • cathibosco will be looking into this and how to reuse some of the ideas from her work for “Create a Blog

#43028: Remove numbers before month in dropdown, it makes user confused when drowdown is not opened

  • comment added: I can see how this could help for scanning and also accessibility. Are there any examples of how other sites do this we can lean on?

Calls for Design: follow-ups

Plugin icons are complete and @cathibosco is doing a review. Last steps:

    • gather everything up and thank the contributors.
    • Also where to send the final package? Ask in #meta Slack and update issue https://meta.trac.wordpress.org/ticket/596

Create a new trello card for the headers? Same way of working?

@estelaris wonders where to store the Training Team infographic native .ai file she recently finished

  • Should be stored in their GitHub repo. That makes the most sense in this context.

Items labeled ready to review in the meeting

  • Nothing this week

Housekeeping

What will be the main focus for the next months for WordPress design?

  • @karmatosed: I wanted to suggest we start each month/ few months focusing on an aspect that needs work. My suggestion is we start with on-boarding. Suggested homework
    • give your feedback at in the shared doc
    • Think of an idea for an onboarding project and bring it to next week’s meeting.

Improve Trello board organization on Design team

  • Do we need this or can we close now? We can iterate later.
  • Some agree, but as part of our onboarding/documentation, the info on the Trello board it shouldn’t be confusing for new people
  • @boemedia: columns onboarding, handbook and outreach refer to the overview in the roadmap card in the team structure column

Triage participation

  • For those of you that haven’t been we do triage at 16:30 UTC in this very channel. We focus through issues for just 1/2hr but it’s a great toe dip into contributing.
  • @karmatosed is happy to train people up who feel ‘hmm leading triage is something I’d like to learn’.

Onboarding for tickets

  • Many people are confused or intimidated by tickets in Trac or GitHub, especially those who are not developers.
  • @karmatosed will be running a ‘non dev’ ticket onboarding session for trac and GitHub – covering Gutenberg also.
  • It will happen in the usual triage slot on Mon Aug 6, but note that it will be an hour long that day. Blog post announcement with details coming soon.

#meeting-notes