Usability test of Views

We tested Views in Drupal 8 at BADCamp 2012 and this uncovered a large number of usability issues. Since then we have been hard at work resolving them.

We resolved over 20 identified usability issues. Most of the issues revolve around the following fundamental issues:

  • What can views do? People are overwhelmed by the plethora of options and often don't quickly find the right approach.
  • Handler listings are overwhelming, and this causes people to miss the right handler.
  • People occasionally miss the "save" button, making them move off the page before saving.
  • On the detail level a lot of copywriting is overly descriptive, this makes people miss important help text.

Major

We have a number of major issues that we encountered. Most of these revolve around workflow and scan ability of listing pages:

Moderate

These issues will distract but not keep people from using the Views interface:

Normal

Finally, we have dozens of minor issues that often require little coding but have quite an impact on making individual forms better:

We have been working hard at solving many of these issues starting with the copywriting. However we are currently running up against a few issues that will need some serious help in the PHP department.

You can track views issues by following the tags Usability + VDC.

We look forward to your help, feel free to drop by #durpal-usability or #drupal-vdc if you have any questions.

Recent articles

The Drupal core product needs to become more engaging and useful right out of the box. Usability testing has shown why. Here, we want to look at how we can change our process to be more efficient and effective.
We tested Views in Drupal 8 at BADCamp 2012 and this uncovered a large number of usability issues. Since then we have been hard at work resolving them.
Drupal Seven needs to be continuously reinvented. We developed a proposal after much discussion, that set to change how Drupal 8 administration looks out-of-the-box.