Problem/Motivation

Modules in the module list at admin/modules can have links to their help, permissions, and configuration page.

We could add a 4th link, to the drupal.org project page for that module's project.

This is possible where modules are downloaded as releases (as opposed to git clones) because the d.org packaging script adds a 'project' property to the info.yml file.

This would further help associate things in the Drupal admin UI with their home on Drupal.org.

Steps to reproduce

Proposed resolution

Add a link called "Drupal.org project page" next to the other module-specific links in the details element on /admin/modules.

Remaining tasks

  1. Fix the icon for Claro.
  2. Usability review.
  3. Other reviews / refinements.
  4. RTBC.
  5. Commit.

User interface changes

A new link and icon on the /admin/modules page for modules hosted on Drupal.org.

Before

Screenshot of the /admin/modules page showing the 'Devel' module without the change applied (current 9.3.x appearance)

After

Seven

Screenshot of the /admin/modules page showing the 'Devel' module with the grey Drupal logo icon next to the 'Drupal.org project page' link

Claro normal

Screenshot of the /admin/modules page using Claro theme, showing the 'Devel' module with the grey Drupal logo icon next to the 'Drupal.org project page' link

Claro hover

Screenshot of the /admin/modules page using Claro theme, showing the 'Devel' module with the blue Drupal logo icon next to the 'Drupal.org project page' link while hovering over the link

API changes

Nope.

Data model changes

Nope.

Release notes snippet

TBD.

Comments

joachim created an issue. See original summary.

joachim’s picture

Here's a patch.

It needs a greyscale druplicon icon to go on the link, which is outside of my capabilities.

cilefen’s picture

❤️: Good idea!

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

vikashsoni’s picture

StatusFileSize
new16.53 KB
new19.44 KB

@joachim Thanks for the patch patch working fine
After patch there is " Drupal.org project page " Anchor link added to help module.
For ref sharing screenshot

aaronmchale’s picture

Issue summary: View changes
Issue tags: +Needs usability review
chrisfromredfin’s picture

For what it's worth, we intend on having this functionality via Project Browser, where there will be a detail page for each module, and then a link off to the d.o project page itself. With that said, having it right here on the modules page I believe is also a good idea (though as joachim says it needs an icon to be consistent).

One issue we've been considering is also that core modules and contributed modules are treated differently. What happens with this patch for core modules? Do they all link to /project/drupal?

dww’s picture

StatusFileSize
new4.02 KB
new3.03 KB

Holy miracles, batman! #2 still applies cleanly in 9.3.x branch. 😉

I'm not totally sure we should be changing stable templates here, but if we are, we now need to also fix stable9. Attached here. Not sure what that first hunk is doing in the interdiff, I didn't change anything in core/modules/system/src/Form/ModulesListForm.php.

Also realized claro has its own version of this template, so added that, too.

Note: This will also start working for Git clones for folks using git_deploy, or the composer thingy that rewrites info files when you install via composer, or any other method that gets Update manager working for your non-tarball-based install. Update manager needs the project key, too.

Still needs the grey icon, but uploading what I have for now.

dww’s picture

Issue summary: View changes
StatusFileSize
new5.94 KB
new1.71 KB
new56.23 KB

Oh right, core is now providing a Drupal logo SVG (for use on the status report). So it's easy to copy that into a 787878 subdir, change the fill color and dimensions, and add a little CSS to point to it.

Of course, Claro does everything differently. ;) I'm not entirely sure the best way to make this happy on Claro. But here's a version that works nicely with Seven.

Screenshot of the /admin/modules page showing the 'Devel' module with the grey Drupal logo icon next to the 'Drupal.org project page' link

Also added a proper issue summary here.

dww’s picture

Issue summary: View changes
StatusFileSize
new52.16 KB

Before screenshot for the User interface changes section.

dww’s picture

p.s. I'm happy to report that the original patch by @joachim is already doing this:

'#title' => $this->t('Drupal.org project page <span class="visually-hidden">for the @module module</span>', ['@module' => $module->info['name']])

So I don't think this needs an accessibility review. That goodness should already be sufficient to address any possible accessibility concerns with this change.

dww’s picture

Issue summary: View changes
StatusFileSize
new14.56 KB
new10.44 KB
new78 KB
new82.52 KB

Took another look at this and dove in to figure out how Claro really handles all this stuff. This seems to be working properly, and I'm following existing patterns. So hopefully this is cool. Adding Claro screenshots to the UI changes section.

Meanwhile, upon further reflection, we almost certainly should not be altering either stable nor stable9 for a new feature like this. That's basically the point of stable -- it doesn't change (except for really important bug fixes). So I reverted those changes. If we were going to alter stable*, we'd also want to fix core/themes/stable*/css/system/system.admin.css. But I don't think we should touch stable at all.

dww’s picture

Status: Needs review » Closed (duplicate)
Issue tags: -Needs usability review
Parent issue: » #2906547: Add links to Drupal.org project pages to module listings in /admin/modules

Whoops! While searching, found #2906547: Add links to Drupal.org project pages to module listings in /admin/modules. Marking this one duplicate and moving effort (and credit) over there.