There has been a long intense discussion in D8UX: Redesign Modules Page following the research we did to find a solution. We have done a lot of usability tests on this page, to uncover three major problems:
- The module page is overwhelming, thereby failing to inform users about Drupal’s extensibility.
- It is hard to find a module after you uploaded/downloaded it.
- Additional information such as dependencies and links draw too much attention.
We followed a process of trying to get to a resolution but failed to come to a consensus, in this new issue I wish to put out the proposal from the UX-Team. We feel its best to move forward with solving part of this problem, than trying to come to the perfect solution for everything.
The solution we propose follows the trend in the discussion to think about hiding some of the more complex information from initial view. We designed it in such a way that you can now quickly scan down the list of modules, there is no visual nesting and all dependency information is removed from initial view.
The rationale behind all of this is that the page feels very overwhelming while people deeply care about this additional information they foremost care about finding the module they are looking for, that is the primary use case the new UI is designed for.
- Keep all module information by default to just one row, thus improving the scanability as there is not an immense amount of vertical row differences.
- The dependency information and operations are all hidden from initial view, because they add a lot of visual clutter - they are now just one click away.
- The module description is now forced to just one line, when it goes beyond the module description is truncated. This allows us to scale to mobile, and also motivates module owners to brief.
We also made a large number of visual tweaks, moving away from the zebra striping and putting more emphasis on the module name than other information in the table. These details are not yet set in stone, but we do wish to move forward with the overall interaction pattern proposed.
This design is the result of a few very long discussion and various iterations within the UX-team, we are sorry for taking this long to push forward on this. With the help of jenlampton, nod_, aspcilious we were able to move this to an actual patch.
Overall the code still needs review,
- Accessibility review, does it work on screenreaders and keyboard only interactions?
- Mobile review, although we did keep mobile in mind we need to ensure that it works fine on smaller screens.
We would be happy to discuss visual details in subsequent patches, and even within the team we are still debating some of the visual details. For now, however, let's focus this issue to getting the basic interaction model in core.
User interface changes
No API changes.
* Search is not in this issue/patch, because we want to keep this issue focused.
We look forward to more code reviews and discussion!