Gutenberg Phase 2 Friday Design Update #22

Hey everyone, happy Friday! ヽ(•‿•)ノ I want to thank @kjellr for handling the update last week while I was away.

Gutenberg 5.9 was released Wednesday! As @youknowriad pointed out, there were over 40 contributors, and 6 of them submitted their first PR.

A few noteworthy features and enhancements included:

Widgets to blocks

Included in 5.9 were a couple improvements for the widgets screen.

Block Directory

@melchoyce posted an update to the Block Directory. There’s a prototype and some mockups for review. If you haven’t offered up some feedback, please do! Mel is looking to have a usability test written for Contributor Day at WCEU.

Tightening up

This week several designers spent time cleaning up loose ends and making small improvements throughout Gutenberg.

Usability testing

Last month’s usability testing videos are up on make/test. Please review them and leave some feedback about your observations.


Another reminder that there’s a plan to run a usability testing table for Gutenberg at WCEU. Read about the plans and sign up to get involved.


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Design Meeting Notes for 12 June 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

Meeting was lead by @boemedia

There will not be a Triage or Design meeting next week (17-19 June) due to most members traveling to WordCamp Europe in Berlin.

There may be some #design channel activity on Thursday 20 June during Contributor Day at #WCEU.

Triage will resume on Monday 24 June after #WCEU.

Updates

@mapk cannot attend our #design meeting due to a schedule conflict. Gutenberg updates will resume after #WCEU.

Open Floor

We moved to a ticket review https://github.com/WordPress/gutenberg/issues/14744, which @boemedia will comment

@hedgefield reported that the 13xp body text used by WordPress is becoming too small for accessibility reasons.  As resolutions and monitors are increasing, most of the web has embraced 16px as the default standard for text. He would like to explore further, perhaps during #WCEU Contributor Day (aka creating a plugin instead of fiddling with the inspector) so we can see where the bottlenecks are.)

For example some columns in the post overview would be fine with smaller text for the less important properties to save space.

@boemedia asked if someone would be available to develop such plugin and @clorith was mentioned. He collaborated on Site Health with @hedgefield.

@azaozz cited the “design experiments” new plugin that could help out. https://github.com/WordPress/design-experiments

@boemedia suggested to open a ticket and if it is not discussed during #WCEU, perhaps could be brought to the table at a later #design meeting.

Next ticket that was introduced by @pbiron https://core.trac.wordpress.org/ticket/44900, will be added to the call for design to be explored during #triage at a later meeting.

@azaozz brought the attention to another ticket that deals with “inclusive design” around user’s name settings. This is a very culturally diverse topic and there is a link to a really good article on w3.org about it. I’ve tentatively set it for WP 5.3, would be great if we can do something for the User Profile screen

https://core.trac.wordpress.org/ticket/6148
Although the topic is an interesting one, we recommended he gather more information as to what are the user needs in reference to name fields and perhaps a discussion with #polyglots is a good start. There is a link from W3.org that discusses the issue https://www.w3.org/International/questions/qa-personal-names

#meeting-notes

Gutenberg Phase 2 Friday Design Update #21

Widgets to blocks

The experimental widgets screen introduced in Gutenberg 5.8 is still being iterated on. Feedback is being collected in the GitHub issue, and there’s a short-term project board to track tasks.

Block Directory

Work on the block directory is continuing, with lots of great discussion happening in the GitHub issues and in the Figma file. Expect a summary post with updated designs soon.

Accessibility

Tightening up

There’s also been a lot of great work regarding nested blocks this week:


Finally, a reminder that there’s a plan to run a usability testing table for Gutenberg at WCEU. Read about the plans and sign up to get involved.

Thank you for reading and for all your contributions. I hope everyone has a great weekend!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #20

Happy Friday! Gutenberg 5.8 was released Wednesday. Over 42 contributors helped bring this release to the masses. Let’s get to the Gutenberg design details.

Some of the recent updates in the plugin include:

  • Headings block supports custom text colors.
  • Gallery images can be reordered from within the block.
  • Proof of Concept of the block-based widget screen.
  • Update to the Calendar block icon.
  • Width constraints on the Media+Text block.
  • Can drop blocks into the Group block with new block appender.
  • Shortcode block input height adjustment.
  • And many more!

Navigation block

During this week’s core chat, contributors discussed the technical implementation of the Navigation Menu block. Nothing was decided, and considerations are being thought through entirely. Developer reviews can really help keep this moving forward.

Widgets to blocks

The /wp-admin widget-block interface is moving forward thanks to ongoing feedback and iteration. The accessibility team discussed the designs during their meeting and provided additional feedback.

It’s still very rudimentary right now, but it does allow some basic interactions. Please try it out and leave some feedback in the Github issue.

Tightening up

Accessibility

Feedback on publishing flow issues

The Gutenberg Team would really like to get some feedback on the latest publishing flow design proposals.


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #19

I hear some countries have a longer holiday this weekend, so I hope everyone enjoys their time off and gets the rest they need. In the meantime, Gutenberg keeps progressing.

Navigation block

@tinkerbelly posted an IA flow for the block with some ideas around existing menus and new menus. Take a look and leave some feedback.

Widgets to blocks

This is picking up again with lots of PRs coming together to explore different parts of the puzzle. If there’s a particular PR you’re interested in, please jump in with your thoughts.

Block Directory

@melchoyce posted a competitive analysis for the new Block Directory. Some great insight is gained there to help inform the design decisions on this. I get so excited when I hear about previewing blocks in the editor before installing them. I encourage everyone to contribute to that conversation.

Design explorations on the Block Directory will be posted today on Github.

Accessibility

The issues created from the accessibility audit are still moving forward. Many of the low hanging fruit have already been completed. The efforts are now being moved toward the larger and more impactful issues.

Next Friday’s accessibility chat in slack will save some time to discuss the keyboard navigation issue. This is a long standing issue that really requires some thought around how everyone views the editor. Is it a continuous view of content, or an application of blocks? With either of these comes a different approach as to how keyboards might navigation the interface. Some good issue to catch up on for this were listed by @afercia:

  • https://github.com/WordPress/gutenberg/issues/15322
  • https://github.com/WordPress/gutenberg/issues/11581
  • https://github.com/WordPress/gutenberg/issues/13663
  • https://github.com/WordPress/gutenberg/issues/5694

Tightening up

I’d really like to see more work on both the Columns block and the Table block in the next few weeks. There’s been some great enhancements lately, so I’d like to keep that movement going.

The color options for blocks is an interesting conversation. Everyone who has voted, (8 total votes) has voted to include both text and background color options for all text blocks. But there was an interesting suggestion which @tinkerbelly also commented about leading us to more explorations around how we introduce background color for the text blocks.


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #18

Happy Friday everyone! ヽ(•‿•)ノ Why so happy, you ask? Because Gutenberg 5.7 has been released this week!

In response to the accessibility audit there have been many great accessibility improvements. Everyone recognizes there’s still a ways to go, but it’s on the right path with so many issues already resolved.

Some of the impressive enhancements in 5.7 include:

Navigation block

While still in a rough PR, the Navigation block is being thought through and iterated upon. It’s using a new pattern to control the inner blocks (individual menu items) which can use some feedback. Chime in on the PR in GitHub.

Unselected

Selected

Widgets to blocks

If you’re itching to fiddle around with the wp-admin interface for widgets that are now blocks, and you have the Gutenberg plugin installed, you can access it through the plugin’s wp-admin menu here:

There are still a lot of bugs, but it should present the concept well. The new widgets screen is still limited in its abilities right now.

Also, if you haven’t read the UX flow for widget-to-blocks proposal, please do! I’m looking to connect with some plugin developers that use widgets to get their feedback soon. If you have some ideas of who I should contact, let me know in the comments.

Tightening up

There’s been a lot of focus on navigating through nested blocks recently. Some of the wonderful explorations include a PR for dashed borders to help the user see the nested levels, and a clickthrough PR which makes it so much easier to select the parent block and then dive into nested blocks purposefully. These two PRs will add so much to the experience!


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #17

Sorry, I was away last week and didn’t get an update published. Great things have been happening lately. Let’s take a look.

Gutenberg 5.6 improvements

Usability testing

Usability tests are being conducted weekly to evaluate Gutenberg. Posts will be published on make/test to share the videos so that everyone can comment and share their observations.

Accessibility audit

The accessibility audit performed by Tenon, LLC. through WPCampus has been released. There were several issues created in Github. The Gutenberg team, Accessibility team, and others are triaging them. Several were found to be either duplicates or Core bugs that required work beyond Gutenberg. Many of the other issues already have conversations leading to well-thought solutions. There’s been amazing collaboration between WordPress.org teams with this effort!

Tightening up


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #16

Due to the recent holidays and other happenings, various design contributors had some time off including me. Taking this into account, there’s still some good work getting done.

Navigation block

While the PR is still being worked on, there have been some great feedback from designers and accessibility.

Widget to blocks

A post was recently published about the UX flow for introducing blocks into the widgets screens in both wp-admin and the Customizer. The thought is to leave the current navigation labels (ie. Widgets) in the wp-admin navigation sidebar and just refresh the UI. This would be similar in the Customizer too.

Tightening up

Default Theme Patches!

Due to the new Group block being introduced, some patches needed to be created for the default Twenty Nineteen and Twenty Thirteen themes. If you have some time to test these out, please do and leave feedback.


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #15

Gutenberg 5.5 is released! The long-anticipated Group block is now available. In addition to a strong list of enhancements, there’s even a bit of a performance boost. This release included 48+ contributors, thanks, everyone!

This is a short post this week. For more information, read up on the release notes linked above, and visit the GitHub issues/PRs labeled Needs Design Feedback or Needs Design.

Focuses

Accessibility

Research

Prior to the release of WordPress 5.0, @jarahsames conducted a survey with WordPress users regarding the new Gutenberg experience. Here are the results.


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2

Gutenberg Phase 2 Friday Design Update #14

Let’s dig in!

Navigation block

@jorgefilipecosta is quick to get a prototype going! Check out the preliminary development.

Widgets to blocks

A question was recently asked of me if I had thought about the UX for both new and existing WordPress users. While I had thought about this, I realized I hadn’t really shared some flows with everyone. I’m aiming to get something like this articulated in Figma by Monday.

Some questions that arise when thinking through the UX:

  1. Should new users see anything using the terminology “widget” including an option to add widgets in the widgets.php page, or should the experience be completely focused toward blocks?
  2. Existing users who have existing widgets on their site.
    1. There needs to be a way that WordPress notifies the user of the switch to blocks. Do we automatically wrap the widget in the Classic Widget block? or teach the user how?
    2. Does WordPress show both a widget.php page and a block area page? This could help themes during the transition as well.
  3. Existing users who don’t have widgets on their site.
    1. If users haven’t used widgets yet, should WordPress just push them toward blocks and deprecate the widgets terminology similar to the new user experience?

Tightening up


Thanks for reading, staying informed, and contributing anywhere you can!

#design, #gutenberg-weekly, #phase-2