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
- Fix the icon for Claro.
- Usability review.
- Other reviews / refinements.
- RTBC.
- Commit.
User interface changes
A new link and icon on the /admin/modules page for modules hosted on Drupal.org.
Before

After
Seven
![]()
Claro normal

Claro hover

API changes
Nope.
Data model changes
Nope.
Release notes snippet
TBD.
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | 3012004-16.claro-hover.png | 82.52 KB | dww |
| #16 | 3012004-16.claro-normal.png | 78 KB | dww |
| #16 | 3012004-16.patch | 14.56 KB | dww |
Comments
Comment #2
joachim commentedHere's a patch.
It needs a greyscale druplicon icon to go on the link, which is outside of my capabilities.
Comment #3
cilefen commented❤️: Good idea!
Comment #9
vikashsoni commented@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
Comment #10
aaronmchaleComment #11
chrisfromredfinFor 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?
Comment #12
dwwHoly 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
projectkey, too.Still needs the grey icon, but uploading what I have for now.
Comment #13
dwwOh 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.
Also added a proper issue summary here.
Comment #14
dwwBefore screenshot for the User interface changes section.
Comment #15
dwwp.s. I'm happy to report that the original patch by @joachim is already doing this:
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.
Comment #16
dwwTook 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.Comment #17
dwwWhoops! 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.