Drupal Association members fund grants that make connections all over the world.
Over the years we have done numerous usability tests on the module page, and they all discoverd various problems that need to be solved in a redesign. The problems we found are :
- The module page is overwhelming, thereby failing to inform users about Drupals extendability.
- It is hard to find a module after you uploaded/downloaded it.
- Additional information such as dependancies and links draw too much attention.
Process for finding a resolution
- Prepare prioritized task list for the modules page, list of requirements for presentation and functionality.
- Verify our assumptions with some interviews
- Use those lists to find the best ideas for the most important tasks/requirements in all the mockups that have been posted.
With the information from this, we can continue our design iterations and finnally decide going down a certain path.
The list of things you want to do on this page, prioritized by importance:
- Find a module
- Enable / Disable / Uninstall module
- View module description to orientate what the module is about
- Change the permissions / configurations of a module
- View available updates / update module
- View current module versions
- View which modules are required to be able to enable, disable or uninstall a module
Current ideas for solution
It is quite messy to follow this topic around issue #88 the discussion for Drupal 8 started. In the past months we have consensus on a number of ideas but still have discussion about their specific design and implementation.
Agreed upon ideas
- Using a accordion like interaction to encapsulate information such as dependancies.
- Allow users to filter the list using search.
- Have a signal for showing which modules are "new".
- Have a signal for modules that require update(s).
Topics still under discussion
- How to group modules; using packages, categories, tags, nothing?
- How to filter modules (disabled, enabled etc.), what meta data is important?
- How to handle dependancies, disabling and enabling modules that require other modules is currently too hard.
As noted in the process for finding a resolution, we have concluded that we need to do interviews. The current progress of this is :
- Test script has been written
- 17 interviews have been conducted