Title: Design Meeting Notes for 10 July 2019
Author: Estela Rueda
Published: July 10, 2019
Last modified: July 11, 2019

---

 [  ](https://profiles.wordpress.org/estelaris/) [Estela Rueda](https://profiles.wordpress.org/estelaris/)
8:14 pm _on_ July 10, 2019     
Tags: [meeting-notes ( 132 )](https://make.wordpress.org/design/tag/meeting-notes/),
[meta ( 7 )](https://make.wordpress.org/design/tag/meta/)   

# 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](https://wordpress.slack.com/archives/C02S78ZAL/p1562781652244500)
and [find the meeting’s agenda here](https://make.wordpress.org/design/2019/07/09/design-meeting-agenda-for-wednesday-10th-july/).

## Housekeeping

### WordPress User & Developer Survey

There is a call for feedback on the [Updates to the WordPress User & Developer Survey](https://make.wordpress.org/updates/2019/06/28/updates-to-the-wordpress-user-developer-survey/).
[@melchoyce](https://profiles.wordpress.org/melchoyce/) asked if we wanted to discuss
any questions as the design team. 

Two suggestions by [@mapk](https://profiles.wordpress.org/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](https://profiles.wordpress.org/melchoyce/) clarifies that the survey
is mostly publicized through [WordPress.org](https://wordpress.org/) and provided
a [link to data from previous years](https://wordpress.org/news/2017/12/wordpress-user-survey-data-for-2015-2017/)
to guide us in our choices.

[@karmatosed](https://profiles.wordpress.org/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](https://profiles.wordpress.org/karmatosed/)
suggested that next week we focus on the TrelloTrello Project management system 
using the concepts of boards and cards to organize tasks in a sane way. This is 
what the make.wordpress.com/marketing team uses for example: [https://trello.com/b/8UGHVBu8/wp-marketing.](https://trello.com/b/8UGHVBu8/wp-marketing)
board and decide what needs to be done. [@youknowriad](https://profiles.wordpress.org/youknowriad/)
asked how to access the [Trello board](https://trello.com/b/fnHScayo).

[@PiotrGawinski](https://profiles.wordpress.org/piotrgawinski/) is a new member 
and would like to find a small project to get involved with and [@boemedia](https://profiles.wordpress.org/boemedia/)
recalled the link for [Calls for Design](https://make.wordpress.org/design/calls-for-design/)
column in Trello.

## Updates

[@mapk](https://profiles.wordpress.org/mapk/) let us know that [Gutenberg 6.1](https://make.wordpress.org/core/2019/07/10/whats-new-in-gutenberg-10-july/)
was released today! It includes some really cool enhancements with lots of people
contributing. [@youknowriad](https://profiles.wordpress.org/youknowriad/) gave us
some explorations to look through:

 * [Live Drag and Drop](https://github.com/WordPress/gutenberg/pull/16457) 
 * [Edit/Navigation Mode](https://github.com/WordPress/gutenberg/pull/16500) (mostly
   for a11yAccessibility Accessibility (commonly shortened to a11y) refers to the
   design of products, devices, services, or environments for people with disabilities.
   The concept of accessible design ensures both “direct access” (i.e. unassisted)
   and “indirect access” meaning compatibility with a person’s assistive technology(
   for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)
   but touches on design) 

 [@drw158](https://profiles.wordpress.org/drw158/) shared a[ component audit](https://github.com/WordPress/gutenberg/issues/16367)
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 ReactReact
React is a JavaScript library that makes it easy to reason about, construct, and
maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/)
component library, not the Figma component library.

The first issue opened is related to the [ButtonGroup and Toolbar](https://github.com/WordPress/gutenberg/issues/16514).

### Discussion

[@dingo_d](https://profiles.wordpress.org/dingo_d/) from theme review team is looking
for designers to help create a better preview for themes on WordPress.orgWordPress.
org The community site where WordPress code is created and shared by the users. 
This is where you can download the source code for WordPress core, plugins and themes
as well as the central location for community conversations and organization. [https://wordpress.org/](https://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.](https://meta.trac.wordpress.org/ticket/30)
The demo should showcase GutenbergGutenberg The Gutenberg project is the new Editor
Interface for WordPress. The editor improves the process and experience of creating
new content, making writing rich content much simpler. It uses ‘blocks’ to add richness
rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
blocks, as an example, see [Chaplin Theme](https://andersnoren.se/themes/chaplin/).

To clarify the problem, look at [Theme Twenty Nineteen](https://wordpress.org/themes/twentynineteen/)
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 blockBlock Block
is the abstract term used to describe units of markup that, composed together, form
the content or layout of a webpage using the WordPress editor. The idea combines
concepts of what in the past may have achieved with shortcodes, custom HTML, and
embed discovery into a single consistent API and user experience., etc. It doesn’t
show off the full potential of the theme. To resolve the issue, there is a[ separate demo site](https://2019.wordpress.net/).
The XML demo data should be imported using the default importer. There is an [.xml for Twenty Nineteen](http://friendly-raven.w6.poopy.life/)
but it doesn’t contain menus or widgets. [#meta](https://make.wordpress.org/design/tag/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 tracTrac Trac is the place where contributors create issues
for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).
ticket:

 * MetaMeta Meta is a term that refers to the inside workings of a group. For us,
   this is the team that works on internal WordPress sites like WordCamp Central
   and Make WordPress. 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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/melchoyce/) shared an opportunity to
[getting involved with usability testing](https://make.wordpress.org/design/2019/07/05/block-library-installation-design-hand-off/).
And for designers looking for small tasks, there is always the [Meta trac](https://meta.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~needs-ui&keywords=~needs-ux&keywords=~ui-feedback&keywords=~ux-feedback&group=component&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&col=component&order=keywords&report=9).
Try to stay away from anything titled “Redesign (big section for WordPress.org)”

[#meeting-notes](https://make.wordpress.org/design/tag/meeting-notes/)

### Share this:

 * [  Threads ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?share=bluesky)
 * [  Facebook ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?share=facebook)
 * [  X ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?share=x)
 * [  Reddit ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?share=reddit)
 * [  Email ](https://make.wordpress.org/design/2019/07/10/design-meeting-notes-for-10-july-2019/?subject=%5BShared%20Post%5D%20Design%20Meeting%20Notes%20for%2010%20July%202019&body=https%3A%2F%2Fmake.wordpress.org%2Fdesign%2F2019%2F07%2F10%2Fdesign-meeting-notes-for-10-july-2019%2F&share=email)

# Post navigation

[← Design meeting agenda for Wednesday 10th July](https://make.wordpress.org/design/2019/07/09/design-meeting-agenda-for-wednesday-10th-july/)

[Block Directory in WP-Admin Concepts →](https://make.wordpress.org/design/2019/07/11/block-directory-in-wp-admin-concepts/)