Design meeting notes for September 12, 2018

The full transcription of this weeks meeting can be found in our Slack channel.

We started off with another bit of information sharing amongst the group — this time focused on the tools we use to design and communicate.

Tool discussion

  • What are tools you like to use in designing?
  • What are tools you wish could get better?
  • How do you like to share the work you’ve done?

This is a summary of the tools that were mentioned in the meeting:

for rough sketching

  • paper and pen
  • Sketching on the iPad with Linea Sketch or Paper 53.
  • annotating or altering screenshots using browser inspect to make changes

for higher fidelity designing

  • Sketch
  • Figma
  • Adobe XD
  • Photoshop
  • Illustrator
  • InDesign for annotating mockups/wires for clients
  • WordPress + page builder + css
  • Balsamiq

for prototyping

  • InVision or InVision Studio
  • Balsamiq for mid level prototyping
  • MarvelApp
  • Axure

for planning, content and IA

  • Excel for content audits
  • MindDoodle for mindmapping
  • HotJar for heat maps to guide UX design

for collaboration and communication of designs

  • screenshots and screen recordings with Droplr
  • Zeplin for developer handoffs
  • annotated screenshots or PDFs
  • Marvel and InVision allow people to place comments on the design
  • DropBox Paper for comments and sharing
  • ProjectHuddle
  • Abstract is kinda like github for designers
  • Sketch Cloud and Figma allow commenting

Triage Inbox

No new cards this week

Calls for design: follow-ups

juliekuehl brought up Design for

  • The Training Team has been making progress on getting lesson plans ready and it would be great to start preparing to publish them.
  • Andi is working on wires for lesson plan layouts and re-organizing the homepage examples
  • best way to communicate and comment? Maybe Google Drive might work and Google Draw to comment?

boemedia pointed to WordPress logo usage style guide for WordCamps

  • it would be great if everyone could share an example of a WordCamp logo we believe does a good job of showing off how a WordCamp logo could be done.
  • You can see all the upcoming ones here:

If time allows, follow-up on older cards

Let’s look at a couple Trac tickets

1. Activating a new theme on multisite is very long-winded Needs updated screenshot/flow

2. Option to view condensed diffs for post revisions


Design meeting notes for September 5, 2018

The full transcription of this weeks meeting can be found in our Slack channel.

Introduction round

We start off with a brief introduction round: who is who? It’s been a while and this way new and old contributors get to know each other and each other’s background.

Contributing at WordCamps

What has been the experience of leading and attending the design table at contributor days at local WordCamps recently?

@karmatosed kicks of by posting a few talking points:

  • Is splitting design from other teams useful?
  • What should we change ‘now’ based on experience?

The team shares some recent experiences and @karmatosed suggest creating guidance for leading contributor day, but at the same time keeping different cultures, knowledge and skillsets of designers present in mind. A lot of suggestions come up and we conclude with @karmatosed making a Trello action item with some ideas in it that we can work from.

Triage Inbox

See Inbox column on Trello board.

Finally, @joyously asks if we can maybe change the order of the agenda, so we can spend more time following up on older design requests.

Thanks again to everyone who actively participated in this week’s meeting. Feel free to add your thoughts to the comments of this post.


Design Meeting Notes for August 22, 2018

Today’s meeting agenda was a bit light, so we opened did open hours to allow for folks to chat about anything specific items. You can also read the Slack chat log.

Open Floor:

Designing “Create a blog” pages on

@cathibosco asked for feedback on the latest page designs for “Create a Blog”, great job Cathi! We discussed the pages that have been created so far and had some ideas for improving readability and breaking up the long (but important) copy on the pages. If you’re interested in giving feedback feel free to jump in!

Trello cards

We discussed several of the Trello cards briefly, but didn’t have a major update.

Contributor Day

@EstelaRueda asked for some ideas as she is planning for Contributor Day at WC Nijmegen next week. We discussed some great analog ways to get folks prototyping and sketching as they contribute to current design needs in WordPress. You can checkout the Slack chat to jump to that section. Specifically speaking for this event it was recommended to focus on improving the handbook for design.

And that’s it for today. If you want to get involved feel free to jump into Slack and weigh in. We’d love to have you!


Design Meeting notes for August 8, 2018

In keeping with the loose structure, we spent the meeting focusing on a topic of the week and open floor.

Topic: the Design Team Handbook

Problem: a lot of information is there but not always where people expect it, or presented in a way that’s not easy to digest, or with labels people don’t understand.

@boemedia has begun work on a content audit of the 45 or so existing pages. This review will determine:

  • is it there? if not -> add content
  • is it in the right place? if not -> restructure
  • is it presented the right way? if not -> rewrite

@hugobaeta suggested that making the structure more visual might help us to audit and update too.

@karmatosed will get people to help at WordCamp Brighton too.

Others, please weigh in on this async after reviewing the Trello card.

Open Floor: Gutenberg

@kjellr is working on a pending update of the Gutenberg design handbook. Feedback welcome.

Note that this is geared towards people designing for Gutenberg — either contributing to the project, or designing a custom block.

@karmatosed: Gutenberg feedback is being processed. Now is a great time to jump in and leave design reviews.

There are several ways to test, and you don’t need a local install:

  1. Say Hello to the New Editor
  2. Frontenberg, a frontend instance of Gutenberg with some restrictions so that anybody can test it out!
  3. Testing Gutenberg: A playground to test out the latest Gutenberg releases directly on the front-end.


Design meeting notes for July 25, 2018

Howdy! A day late but just as interesting as what you’d have read yesterday. Btw, it’s always lovely to have folks jump in, the last few meetings have been tremendous with everyone joining and weighing in, makes for a healthy and lively discussion. And.. if you couldn’t make it, well.. that’s what this summary is for.

There was no triage or topic of the week, so we’ll move right past that.

A topic we did end up discussing was related to outreach:

Topic: Outreach

Led out by @boemedia, we chatted about plans for an online design conference. You can checkout the previous Trello discussion. Monique is working on a document to share with the team on what the conference could look like. Keep an eye out for that on Trello! Or here, we’ll probably share it here too.

So what’s the TL;DR? Well, that’s not quite decided but here’s a stab at it based on what we’ve discussed so far: we’ll have a remote based design conference, probably 1-2 days long, sometime in Spring of 2019. We’ll have speakers, and hopefully lots of awesome attendees! If you’re reading this you’re probably a perfect candidate for joining us.

In the discussion on Slack we also chatted about the potential of doing a small version of the conference this year, and then leading into the well planned out version in the Spring.

This led into a conversation about the types of folks who get involved in Core, the motivations, and how we all want to help.

A topic of the week suggestion came up: if you’re new to the design team, what guidelines could be followed to understand the users we’re designing for?

Open floor

Design tools and sharing designs

During the open floor portion of the meeting we started chatting about the collaboration process as designers within (yeah, that’s a real url, I just found out a few weeks ago!) design projects.

As designers we’re used to working with visual tools, Sketch or Figma being good examples. In fact, there’s some great pattern libraries for WordPress that we’ve been starting to use. The problem we run into is wanting visual version control. We’re not sure if we have a great answer yet, but it was really interesting to discuss. A few options were mentioned from a commercial standpoint.

We discussed a perfect project that could benefit from version control, and acknowledge that it’s hard to find the perfect balance between open source design team needs and industry best practices.

And some great news!

The oldest UI feedback tickets in Trac are now all in 2018! This does include tickets that were mentioned in Slack, which may not have had definitive progress. However, it’s exciting to see that we’re getting closer.


Design meeting notes for July 18, 2018

In this new format we introduced a week ago, we kick off with inbox triage. You can read the full transcript of this meeting on our Slackchannel


Triage inbox

We have one incoming on the Trello Board: Create a style guide for future pages based on create a website and recent pages for example ‘Get WordPress’.

: It struck me with all the awesome work @cathibosco1 and others have been doing, we are creating a little design language.

This is really exciting but we haven’t documented it.

@hugobaeta  is willing to share his initial work on Sketch and @jayman is up for documenting this in the handbook, with @cathibosco and new contributor @ninjastar willing to help.

Topic of the week: onboarding

To recap, the idea of focusing on topics is we move projects on by focusing on something larger.

For a few weeks, a few people have been adding their feelings and feedback to a document. It’s not closing so don’t worry you can add even after this.

@karmatosed wants to take some time to discuss what is in the doc.

There are a lot of insights, and we agree on the fact that trac is a huge pain point for contributing. Besides, it’s compounded by fact that there are so many different outlets for discussion + work sharing (slack, trello, make, trac, etc.)

Improving the handbook

The discussion continues and we say improving documentation in the handbook would help.

Therefore we need people to help and review/audit the current content. If you’re in for doing so, you can do so in the Google Spreadsheet we created for this. If you have questions, ping @boemedia on Slack.

Next steps would be restructure, add new content and improve current information (not necessarily in that order).

Mentorship/buddy system

Besides good documentation we can refer to, the buddy system is still a strong wish, since the mentorship/mutual help is incredibly important. For starting, @karmatosed suggests putting up a mentor/mentee spreadsheet in Google and a handbook page to it for transparency. She also suggests some limits to the buddy system, that you can read about in our Slack meeting. There will be links to this sheet in the grey box as well in the front of the handbook.

Checking the buddy sheet will be part of the weekly design meeting agenda.

Open floor

Last five minutes are dedicated to the open floor. Anything people want to bring to attention? Anything someone need help on? What are people working on?

Cathi Bosco continues to work on the ‘Create a blog’ page and wants participants to understand she’s consolidating, since there are multiple cards on this topic on Trello. Therefore she mentions it again.

@karmatosed closes the meeting and @garusky thanks by saying these discussions about the onboarding gave him more context.

We’d like to thanks everyone participating in this lively meeting and hope to see you next week either at Monday’s ticket triage or at Wednesday’s weekly design chat.



Design Meeting Notes for July 11, 2018

For all the details, see the conversation in Slack

This week we’re trying a more simplified agenda. This setup should allow us to have more space for everyone’s input. The aim is more discussion and interaction.

  1. Trello inbox
  2. Trello Calls for design: follow up on current projects
  3. Topic of the week
  4. Open floor

Trello Inbox triage

  • nothing new this week

Calls for Design: follow-ups

@estelaris is having a hard time uploading the infographic native files (.ai) to the training GitHub. She requests help after the meeting.

Topic if the Week

The topic of the week will be something we’d like to spend some extra time on. Nothing for today, but will be Onboarding next week

Open Floor

  • people were not sure what to bring up here, but note that it’s ok to bring ideas and concepts to the table that are brand new.
  • reminder about existing cards in Trello: if you see a project on the Trello board you’d like to work on but but status is unclear, check with the person on the card (either there or here in Slack.) They may not have updated it, or have been really busy and would love some help.
  • Filling the time with ticket triage was suggested, but not everyone wants to dive into triage and we already have a separate meeting for that.
  • Don’t forget the triage training for designers happening on Aug. 6, 2018


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 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

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


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.


Design meeting notes for June 27, 2018

Transcript of the whole meeting can be found in our Slack-channel.

Sketchpress and WP Admin Design System

Special topic: we spent a good portion of the meeting discussing how to bring together a few amazing Sketch resources that have been developed. The hope if that having one source of truth will make it easier to accelerate design for anyone working in the WordPress community. See Slack for the whole discussion but some highlight are noted here.

The resources and creators are:

  • @Sarah James from 10Up
  • @garusky from Milan
  • @Joen has an extensive Sketch file and library from his work on Gutenberg

Where will this live?

  • The SketchPress repo I created already has traffic and followers, so keeping it all in there might be good
  • A contributions file in the repo would be key to capturing all the efforts that would be merged into the single location
  • A solution is still being discussed…

How can we all contribute to this and help?

  • Let’s all be thinking about this

Triage Inbox

Nothing this week

Calls for design: follow-ups

@cathibosco requests to discuss the ‘Make a blog post‘ page design

  • Everyone agrees that subpages are a good design direction

Infographic of Training Team workflow

  • @estelaris shared that the simplified version is up in Trello and Training team will review and discuss which one they prefer

And that was all the time we had today.


Design meeting notes for June 20, 2018

Transcript of the whole meeting can be found in our Slack-channel.

Triage Inbox

Calls for design: follow-ups

  • @cathibosco has done some really nice work on the design for a ‘create a blog’-page for the Growth Council. We’ve discussion the fact that the page has a lot of content, due to lists. This makes the page very long. We’re exploring the possibilities of using Javascript accordion and will contact the meta team for this. @karmatosed addresses this has quite a few usability and accessibility issues that should be considered.
  • Next card discussed was the design for pages as requested by the training team. @Andi has done some nice mockups for new pages.
  • Also, @estelaris has worked on the Github infographic for the training team, explaining the workflow. WCEU contributor days provided new insights for this call. @foletto and David Needham discussed the design and workflow with Estela and gave her lots of feedback, which resulted in a new design and recommended an simpeler version. The Trello card will be updated accordingly.


Design team related

  • Thumbs up to all those who spoke or contributed at WordCamp Europe last week! – Both @joshuawold and @karmatosed did a workshop/presentation.
    Besides this, @joshuawold and @boemedia lead the design table on contributor day. WiFi was down but we were able to do some work on Trac tickets with laptop sharing, and we did some ui/ux sketching ideas, as well as discussed improvements to the admin. A few additional things as well.
    It was a great day! So many amazing people joined in. A full blogpost about contributor day’s design table will follow soon in this channel 🙂


@karmatosed briefly updates the design team with the current state of Gutenberg. For those who didn’t attend WCEU, the team is currently working towards being functional complete. This should happen in a few weeks. The MVP (minimum viable product) list can be found on Github. After that, the team moves into a bug fixing frenzy. If anyone wants to get involved right now, please use the feedback form included in the plugin. If all goes well, 5.0 will go into beta in August.

If time allows, follow-up on older cards

  • @jayman has spoken to @schlessera on the php/servehappy project at WCEU. They’re on the same page and design work for this will be continued tomorrow. Also, Alex Denning was asked for a content review of this page.
  • @joyously expresses her concern for #43986
    There was a brief discussion about the UX for this php notification and we’ve put the ux-feedback tag back on to get more eyes on the ticket, as currently, mainly the UI is discussed.

Thanks all who attended the meeting. If you have anything to add to these notes, please feel free to add this in the comments.