User-testing Gutenberg • Yoast

At Yoast, we organize a company-wide user testing session each month. In these sessions, we ask our employees to take a look at a product or feature. On October 12th we focused on user-testing Gutenberg. We did this to gain a better understanding of how different users work with Gutenberg. This knowledge is sure to help us in our own contributions to the Gutenberg project. Today we’re publishing the test results for reference.

We will discuss these outcomes with the Gutenberg team and create issues on the Gutenberg repo for the things that need fixing. We hope others will be inspired by this document to organize their own user tests around Gutenberg. Fixing some of these usability issues isn’t even that difficult, but they have to be found in the first place. We have to keep looking. And when we do, we can make sure Gutenberg becomes the best web content editor around!

What is WordPress Gutenberg?

Gutenberg is the new content editor that is supposed to debut in WordPress 5.0. This new editor is a complete departure from the old WYSIWYG editor that is now available in WordPress. Gutenberg introduces the concept of ‘blocks’ of content that can contain almost anything and be arranged in any order. While we’re fairly skeptical about certain aspects of Gutenberg and the way it is developed, we’re also excited about the new era that this editor will bring. We’re actively looking at how to integrate Yoast SEO into Gutenberg.

Table of Contents

1 Setup

We gathered 40 people of diverse backgrounds and technical experience, from absolute beginners to experts and WordPress contributors, and divided them up into teams of two, who were tasked with recreating this post from The Next Web in Gutenberg v1.4.0. We chose that post because it has a bit of everything; It contains straight-up text and headings, links, images, galleries, quotes, embedded tweets and videos.

2 The results

Below are their feedback points, grouped per subject and edited for clarity. We’ve also tried to list possible solutions for most of them, and mention any related issues from the Gutenberg repo (that we could find).

2.1 Interface

Possible solution: change dropdown from showing what the block currently is to the text Convert into.

Possible solution: turn the arrow buttons into a grabber.

Possible solution: Dropbox Paper does a great job at making the inserter an obvious button. Related to the discussion in the first point.

Possible solution: display the Inserter between blocks. This has been implemented via this PR.

Possible solution: selecting a block could switch the sidebar to the Block tab, or the cog should be more accessible. Discussion about this took place in this Github issue.

Possible solution: Dock the toolbar at the top.

2.2 Content editing

Possible solution: While it’s nice not to get that big permalink popup when you just start writing, maybe it can appear in a more understated way, fading in as a small text above or below the title. Discussed here, has some REST API problems it seems. Putting it in the sidebar is an option too.

Obvious solution: it needs to be editable.

Possible solution: make the cover image block be the featured image.

Obvious solution: it should.

Obvious solution: it should stay open.

Obvious solution: when you edit a link, all other related popups in that menu should be closed.

Possible solution: don’t treat a

tag in a quote block as a ‘block breaker.’

Possible solutions: 1. Live with it 2. Don’t allow font size changes (should depend on the theme maybe) 3. Find an alternative way to display what the block type is, even when the block UI is not visible.

Obvious solutions: add those options to the column block, or add the column options to the paragraph block (a better idea maybe).

Possible solution: tweak the paste-conversion system also to overwrite the selected block (if it is empty).

Possible solution: remember the state of the block when you click Edit HTML, so any incompatible changes can indeed be discarded properly. In our case, pressing Overwrite cleared the entire block.

2.3 Media

Possible solutions: align it to the middle of the block, or add an extra button specifically to center the image (as you could also want the image to be left-aligned but not next to text).

Possible solutions: maybe a + button appears next to the first image, or add a block switcher to the image block to make the transformation easier.

Obvious solution: they should be. Noted here.

Possible solution: if the aforementioned grid layout was possible, this might not even be necessary, you can just chop and screw a gallery with some loose image blocks.

Possible solutions: just paste the URL as text, or convert the block to an image block.

Possible solution: center the image options pop up on the image.

2.4 Mobile

Possible solutions: rearrange the icons in a more calming manner, or restyle the buttons to look consistent here. Somewhat related to this discussion.

Possible solution: maybe just forget about tooltip on mobile, they rely on a hover, which doesn’t exist on mobile. Or only show the tooltips when you hold down on a button or something, a separate intent. Seems improved in v1.5.

Obvious solution: it should.

2.5 Positive remarks

3 Conclusion

As you can see, there is still a lot to gain regarding user experience. But, like G.I. Joe once said, knowing is half the battle. If we identify these issues now and come together to think about solutions, we can make sure the first version of Gutenberg that gets merged into core will be the best it can be. It won’t be perfect because it can’t do everything all at once, but in terms of content editing, we’re starting to get close to a solid v1.

Tim Hengeveld

Tim is our UX designer and one of the illustrators at Yoast. Using his prior knowledge as a game developer, he is focused on improving the experience and flow of our products, and does his best to make it look good while he’s at it.