Problem/Motivation

While reviewing #2035079: [PP-1] Figure out what to do with the install/uninstall modules page at #3373236: Drupal Usability Meeting 2023-07-14 we agreed that using a drop/split button for the module links could provide a better overall user experience, and make the module list slightly more consistent with other areas of Core.

Currently, the module links are hidden in the expandable description detail element, so moving them to a more prominent position could make them easier to access.

Steps to reproduce

Proposed resolution

1) Add drop/split button. This would involve adding a drop/split button to the far-right side of each module in the module list and moving the module links out of the expandable description detail element. For installed module, the drop/split button would contain the existing links

2) Add 'uninstall' link. We may also want to add a Uninstall link, as this could provide a slightly more convenient way of uninstalling a module right from the list.

3) Add 'install' link. For uninstalled modules, we could provide a single Install link, this could result in a slightly more convenient experience for installing a single module, where the user could simply click the link, rather than having to select the checkbox next to the module then scroll to the button of the list. On some sites the module list can be quite lengthy, so this could save time for users.

4) Icons. This issue does not currently have an opinion about whether or not the module link icons should be retained. Discussion and prototypes/screenshots may be required to assess how well icons work in a split/drop button layout.

Remaining tasks

1) Done. Add drop/split button.

2) Add 'uninstall' link.

3) Add 'install' link.

4) Icons.

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3374769

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

AaronMcHale created an issue. See original summary.

vbouchet’s picture

StatusFileSize
new508.59 KB
new7.9 KB

Here is a screenshot of the UI with links using 'operations' links type. For disabled module, I added the "Enable" operation.

Module list with operation links

I am sharing the patch as a starting point but it does not aim to be used as-is as I took many shortcuts to demo the end result.

zaporylie’s picture

Chiming in as this is a blocker for my contrib module that aims to inject an additional link to be shown next to the installed module. Currently, the list of potential links is fixed to only 3 options - help, permissions, and configuration. IMHO, the module interface should make it possible to inject any link. Dropping support for icons could and moving onward to dropdown, operation-style links could make that much easier.

mstrelan’s picture

Status: Active » Needs work

Should this be postponed on #2035079: [PP-1] Figure out what to do with the install/uninstall modules page? Seems we should "figure out what to do" before doing?

Setting to NW because we have a patch that we can start with, but please change to Postponed if we should not continue yet.

quietone made their first commit to this issue’s fork.

quietone’s picture

Issue summary: View changes
Status: Needs work » Needs review

This issue shouldn't be postponed. This was created by the Usability team as one of 3 well-scoped issues to be fixed before discussing further changes to the install/uninstall pages. Once the set of three are complete then further review of the page will be made. That is explained in #2035079-137: [PP-1] Figure out what to do with the install/uninstall modules page.

Converted to an MR.

Should we do items 2, 3, and 4 in this issue?

quietone’s picture

Issue tags: +Needs screenshots

This needs the latest before and after screenshots as well. They should be in the issue summary, either as a image or a link.

quietone’s picture

Status: Needs review » Needs work

And there is a test failure.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.