Problem/Motivation

Currently, core and contrib modules are listed in between each other on the Extend page (/admin/modules), which can be confusing.

Steps to reproduce

Add a few contrib modules, go to /admin/modules and see that core and contrib modules are listed in between each other, and "Web services" with JSON:API, REST and Serialization core modules close to or at the bottom.

Proposed resolution

Separate core and contrib modules, by first showing the basic core modules, followed by experimental core modules, and then the rest of the core modules, labeling them clearly, for example "Core - Multilingual". Show contrib modules below, under their own "Contrib modules" header.

Now, no version and no separation between core and contrib modules

Current display

Proposal, show version and separate core and contrib modules

Proposed display with version and separation

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#10 1.1-3175164-10-current-display-no-version-no-core-contrib-separation.png1.44 MBressa
#10 1.2-3175164-10-suggested-display-version-core-contrib-separation.png1.55 MBressa

Issue fork drupal-3175164

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:

About issue forks

Comments

ressa created an issue. See original summary.

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.

ressa’s picture

ressa
he/him
commented
Issue summary: View changes

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.

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

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

ressa opened merge request !4084

ressa’s picture

ressa
he/him
commented
Issue summary: View changes
StatusFileSize
new 1.2-3175164-10-suggested-display-version-core-contrib-separation.png1.55 MB
new 1.1-3175164-10-current-display-no-version-no-core-contrib-separation.png1.44 MB
ressa’s picture

ressa
he/him
commented
Status: Active » Needs review
smustgrave’s picture

smustgrave commented
Status: Needs review » Needs work
Issue tags: +Needs architectural review, +Needs usability review

Tagging for architectural review to see if this is someone we want to implement in core or leave for a contrib module like contrib.

Tagging for usability to see if this introduces any regression.

Moving to NW though as I'm not sure using a hardcoded list is the best approach. Would be something that would have to be kept up with potentially and not sure committers will be for that.

Did post in slack also.

ressa’s picture

ressa
he/him
commented

Thanks for looking at it @smustgrave.

I agree that hardcoding the list is a less than ideal solution, but it was what I could make work, to create a rough sketch of my idea, and separate core and contrib modules.

I hope an experienced PHP coder can come up with a more elegant solution :)

And thanks for alerting developers on Slack. I hope that instead of possibly discussing it there, it would be great if it was discussed here. Slack, dare I say, feels a little "behind closed doors", and we have this great forum, where everyone can follow along. Also those not on Slack.

yoroy’s picture

yoroy commented
Issue tags: -Needs usability review +Usability

This is a complex topic and screen :) Before considering the proposed solution, it would be good to provide more concrete info on how the current sorting and grouping is causing problems. "Can be confusing" is a bit thin in that regard :)

I'm sure the current state can be improved, but not so confident that this proposal points towards a more managable situation:
- Already the core categories are a mix of "core-core" and additional topic/feature specific groupings (fields, multilingual, migrate...)
- Not all contributed modules add functionality on the same scale and scope. Commers or Groups introduce whole new concepts and would merit their own section, but would a contrib module that provides a new field type really add it's own section at the bottom instead of adding itself in the existing Fields section?
- Not sure how adding the version number helps here?

Main point is that it would be good to get a better grasp on the usability problems here before exploring possible solutions.

nicxvan’s picture

nicxvan commented
Status: Needs work » Postponed (maintainer needs more info)

I'm going to postpone this for the questions in 14.

Honestly I think we should close this as won't fix.

I agree this page needs work, but there are multiple issues taking about many alternative ideas.

I don't think this version makes the page more usable.

Having paragraphs come after workspaces I think is far more confusing than the current situation.

nicxvan’s picture

nicxvan commented
Version: 11.x-dev » main
Status: Postponed (maintainer needs more info) » Closed (duplicate)
Related issues: +#2035079: [PP-1] Figure out what to do with the install/uninstall modules page

I'm going to close this as duplicate.

Thank you for working on this, I don't see a way around 14 though.

Feel free to reopen if you think there is more information there.

Here is the related issue: #2035079: [PP-1] Figure out what to do with the install/uninstall modules page

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.