Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This is a sub-issue of #538904: D8UX: Redesign Modules Page
In order to improve the modules page, an idea taken from the Modules filter module http://drupal.org/project/module_filter module is being discussed for implementation.
It concerns using vertical tabs presenting different preset filters to reduce the clutter and improve scannability of the modules page. This image shows the idea:
It is to be decided wether these tabs (especially the many for categories or packages) are useful, and if they should be visible all the time.
Next it would have to be decided how many tabs should be there and what they should filter by.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | modules-page-all_v2-tabs_highlighted.png | 168.42 KB | klonos |
| #1 | tabs-for-modules-page.png | 195.62 KB | eigentor |
Comments
Comment #1
eigentor CreditAttribution: eigentor commentedClearer image for newcomers to the issue, used in issue summary
Comment #1.0
eigentor CreditAttribution: eigentor commentedUpdated Format of Sub-Issue
Comment #2
klonos...I think that v2 of the mockup from #180 (where enabled/disabled tabs are removed and enabled/disabled checkboxes converted to radio button set) makes more sense.
Comment #3
jenlamptonI just want to say that I disagree with use of vertical tabs on the modules page 100% until we can fix the category/package problem. The existing categories/packages are completely arbitrary, and they only help people find modules once you know where a module maintiner decided to put his or her module. We need to solve that problem before we implement something like vertical tabs based on categories. (It's also a complete abuse of vertical tabs - but let's not get me started on that one) :)
Comment #4
webchickI agree with jenlampton. That's basically what I was trying to say over in #538904-173: D8UX: Redesign Modules Page
Comment #5
jenlamptonI opened a new issue specifically for the package debate, more at #1355292: Come up with better alternatives for groupings on the modules page
Comment #6
eigentor CreditAttribution: eigentor commentedTotally agree with the reorganization of categories being necessary.
"Completely arbitrary" is still a bit much to say, I would not say this is completely useless,
http://screencast.com/t/msdV7bNO8m
and people still might very well click on it.
You downloaded this funny thing called Panels - there you go. Actually the module groups that have their own name or are categorized in a good way
Still vertical tabs might not be the only way to do this, speaking of misused UI patterns.
Having multiple keywords like suggested in #1355292: Come up with better alternatives for groupings on the modules page would require to find a different pattern anyway.
So the problem to solve would be "There is a lot of items that can be categorized in many ways. The users cannot be sure as to what these items mean nor about the categories. Find an efficient way to categorize these items".
Ebay failed at it, this is for sure :P. But maybe we should think more in the way of Apache solr/faceted search: first filter with the search box, then categories to filter down more appear (which do not need to be vertical tabs :))
I guess that is an often used pattern in similar situations.
There will sure be shiny UIs for this. I like this basic concept, e.g. http://d2o0t5hpnwv4c1.cloudfront.net/445_quickFiltering/index.html#
Comment #7
quicksketchI strongly disagree with this proposal. All I'm seeing is a bunch of clutter with little benefit. The only thing of value that module_filter provides in my opinion is the search box. Of all the features in that module, it's the only one I use 99% of the time.
Comment #8
klonosApache solr provided categories/filters *would* be perfect if only Apache solr itself didn't require additional server-side setup AFAIK. vtabs on the other hand are already in core and don't have any specific requirements to work - just JS (that I guess solr needs too). I also *think* that vtabs nicely fallback to fieldsets when JS is not available. Am I wrong about all these?
Comment #9
jenlamptonThis is not what vertical tabs are for. Everywhere else in core they are being used correctly, let's not start adding inconsistency and incorrect usage now.
Copied from #1144806: Nodewords' use of Vertical Tabs on settings page actually hinders usability
The purpose of Vertical Tabs is to do the following:
- Collapse infrequently changed options, usually ones that a user will see frequently (such as when creating a node) that don't need to be changed each time.
- Provide a summary of the contents of each group so the user doesn't need to open each tab to verify its contents.
- Each tab is intended to be a short form that can be viewed without scrolling, so the user can quickly tab through each one if necessary.
Comment #10
klonosSo vtabs on the Modules page would...
- Collapse infrequently enabled/disabled modules, usually ones that a user will see frequently that don't need to be changed each time (core and other basic modules -like views, admin_menu and others- that once enabled, are rarely ever disabled).
- Provide a summary of the modules of each group so the user doesn't need to open each tab to verify its contents.
- Each tab is intended to be a short form that can be viewed without scrolling (once some previous filtering is done through instant_filter), so the user can quickly tab through each one if necessary.
Sounds perfect to me and that is precisely how things work in module_filter.
Comment #10.0
klonosAgain updating summary. Changed image.
Comment #11
lpalgarvio CreditAttribution: lpalgarvio commentedComment #12
joyceg CreditAttribution: joyceg commentedAdding vertical tabs seems to be a cool idea. It will definitely enhance the Modules page.