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.
We have a number of major issues that we encountered. Most of these revolve around workflow and scan ability of listing pages:
We finally posted our proposal for a Drupal Seven style guide, after lots of discussion and iteration it's now at a point that we feel it reflects our idea of Drupals branding.
- Identify Drupal core values that we can use to determine the look & feel for the Seven theme.
- Unify the visual language in Seven and ensure the overall look-and-feel supports the core values.
- Identify the visual and UI patterns used by Drupal core so that they form a conscious, shared language for us to built upon.
- Provide guidelines and rationale for others (e.g. contrib) to build upon as new interactions, styles and platforms emerge.
This proposal will require quite some discussion, but hopefully after that we can document it and bring this into core. With cleanup phase coming up we can now focus on consolidating all the different styles that were brought into Drupal 8. Creating this style guide has been a tremendous effort, of many many hours by the team, totalling 5 full iteration rounds. A great deal of appreciation should go to Ryan Fredrick (ry5n), for taking a leading role in making this happen.