Design meeting notes august 14th 2019

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here. You can join the Slack channel by following the instructions in our handbook.

Updates

@mapk updates us on Gutenberg developments. Gutenberg 6.3 is out! Including new Navigate/Edit modes, and some major Table block updates. Priorities for Gutenberg development will now be discussed every week in the #core-editor channel, great for anyone wanting to stay up-to-date and lend a hand.

@melchoyce did a new iteration in the block directory mockups that she’d like feedback on. User testing will also be done at WordCamp Brighton this weekend.

@davewhitley points us to the Component Review project, to review all the new UI elements introduced in Gutenberg, and make them generic enough to use in all of WordPress and document them properly.

@hedgefield lets us know that WordPress 5.3 will likely include an update for the Site Health grading, and also wonders whether design could take a look at wordpress.tv, which is becoming a bit dated. Literally, there is no 2019 content on the wordcamp.tv landing page. @karmatosed and @melchoyce ruminate on the pressed-for-time meta team and their priorities, concluding that adding a few tickets with mockups and asking in #meta would be the best approach.

Open floor

@blaidalfo expressed interest in helping with the Figma libraries containing the WordPress components. @davewhitley also contributed some documentation which can be found here. An official list of maintainers will be published soon. If you want in, let us know in #design!

#meeting-notes

Design Meeting Notes for 10 July 2019

These are the weekly notes for the design meeting that happens on Wednesday’s. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Housekeeping

WordPress User & Developer Survey

There is a call for feedback on the Updates to the WordPress User & Developer Survey. @melchoyce asked if we wanted to discuss any questions as the design team. 

Two suggestions by @mapk:

  • What is the one thing that you struggle with most in WordPress?
  • What is something you know now about using WordPress that you wish you knew earlier?

There is also a discussion about whether this is focused on developers or end users, as having both as survey targets make it very difficult to narrow questions. 

@melchoyce clarifies that the survey is mostly publicized through WordPress.org and provided a link to data from previous years to guide us in our choices.

@karmatosed suggested we read the data and provide our suggestions as comments and insights as feedback on the post mentioned above.

Topics for next meetings

Another call is to add discussion topics for upcoming meetings. @karmatosed suggested that next week we focus on the Trello board and decide what needs to be done. @youknowriad asked how to access the Trello board.

@PiotrGawinski is a new member and would like to find a small project to get involved with and @boemedia recalled the link for Calls for Design column in Trello.

Updates

@mapk let us know that Gutenberg 6.1 was released today! It includes some really cool enhancements with lots of people contributing. @youknowriad gave us some explorations to look through:

@drw158 shared a component audit he’s been working on to clean up the component library as it has grown and exploded to places beyond the editor. The audit is related to naming, structure, and composition, not code audit, so designers at any level can contribute and it is on the React component library, not the Figma component library.

The first issue opened is related to the ButtonGroup and Toolbar.

Discussion

@dingo_d from theme review team is looking for designers to help create a better preview for themes on WordPress.org, including better-looking demo data. The demo data should be used internally and perhaps theme developers can use it too. For reference, here is the old meta-ticket.  The demo should showcase Gutenberg blocks, as an example, see Chaplin Theme

To clarify the problem, look at Theme Twenty Nineteen in WordPress.org, it has a great theme screenshot, but the “preview” doesn’t look like the screenshot. It is missing elements like logo, nav, cover block, etc. It doesn’t show off the full potential of the theme. To resolve the issue, there is a separate demo site. The XML demo data should be imported using the default importer. There is an .xml for Twenty Nineteen but it doesn’t contain menus or widgets. #meta must add those manually. 

For step 2, we would like to have the option to change the presets of the demos data in the previewer, like chose between business/site vs. blog styles (business, portfolio, blogs, etc.)

So far actions go on trac ticket:

  • Meta ticket needs updating to have everything linked (there seems to be a lot of unlinked things).
  • Volunteers to take existing data (hopefully linked) and start working?

@williampatton will clarify actions and smaller tasks for design needs on trac ticket and design team has agreed to cross collaborate with themes team.

Open Floor

@melchoyce shared an opportunity to getting involved with usability testing. And for designers looking for small tasks, there is always the Meta trac. Try to stay away from anything titled “Redesign (big section for WordPress.org)”

#meeting-notes

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

Design meeting summary March 22, 2018

Find the transcription here on Slack.  The links on the main topics will jump straight to where this item was discussed in the meeting.

Housekeeping

Design team related

  • Lack of feedback from Calls for design
    A few designers had a negative experience when callers for design never properly got back after designs were delivered. As a team, we feel the need to inform people who call for design how we’d like to proceed.
    We’re opting on setting up a guide on how the design process takes place and what can be expected from the designers, but also what we expect from the one who calls for the design. @boemedia will start a draft in Google docs, and after iteration it will move over to the handbook so we can point to this document when someone calls for design.

Triage Inbox

See Inbox column on Trello board. Calls for design made via the Make blog, Slack, etc. should be transferred to Inbox each week, along with any new cards that need to be acknowledged.

Calls for design

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.

Items labeled ready to be a meeting topic

Filter Trello board for ‘meeting’ label which means that some work has gone into the card, and we have enough detail to make a decision on it.

Requests to review existing tickets

Typically from Trac or GitHub

  • no requests this week

If time allows, follow-up on older cards

Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.

Final question by @boemedia about the Invision licenses. What’s the status? @karmatosed says we have it and she will write a post and explain how designers can get a license.

#meeting-notes

 

#meeting-notes

If you’re curious about design for WordPress org…

If you’re curious about design for WordPress.org, I just posted extensive UX research survey results about WordPress.org network of sites on the meta p2 😉

#cross-posting, #meta, #research