Meeting notes

If you didn’t get to attend our meeting in Slack this week, don’t worry! That’s what these notes are for. You can see the previous agenda, and follow the Slack chat log.


Research & recommendations

There are so many great data points and insights here from the research the team has done with WordPress. It’s a treasure trove, thanks to everyone for the work, and it’s well worth checking out. We discussed having a walkthrough of the work. Keep an eye out for that!

What’s next for Dashicons?

We’d love to hear some thoughts on this post. We had a great meeting last week, and a thorough followup, walking through where we’re at with icons in WordPress, and where we can take things from here.


Create style guide for future WordPress pages

Tremendous work has gone into giving a guide for designers or developers to quickly create new pages based on work that’s been done previously. This is really helpful! We discussed in our meeting the work involved to convert the guides to Figma files, as the WordPress design team is able to use Figma for free, and it supports more collaborative design work.

Gutenberg Nav block

We’d love your feedback on all the hard work the team has put into suggesting various approaches to creating a Nav block in Gutenberg. For clarity the work has been broken into five individual issues for discussion.

  1. What happens when I add a menu? (smart defaults, onboarding)
  2. How do I add an item to my menu? (child blocks, link interface, types of content to include)
  3. How do I edit that menu item? (renaming, settings)
  4. How do I rearrange items in my menu? (ordering, hierarchy, sub-menus, still in progress, although this is starting to come up in 3 and 5)
  5. How are menus and menu items presented visually? (focussed state, horizontal/vertical styling)

Feedback on any and all of the issues is welcome. The biggest challenge right now is trying to fit all the complex interactions of a navigation menu into the block area. The team is also trying to follow the principle of putting as much in-context settings next to the block area, and avoiding too many settings in the sidebar.

A great point was brought up about ensuring accessibility is thought of and included in these early stages. We briefly discussed what this could look like, and the design team wants to continually be proactive in soliciting feedback from the accessibility team.

Discussion about bringing it all together (Slack link)

We discussed some of the challenges with making complex Nav blocks, and where the different settings should sit. If you have time, feel free to jump into Slack and read through it; these thoughts are very much in progress, so additional feedback is welcome!

Design feedback

We’d love feedback on a new WordCamp PWA proposal.