Separate Core modules into separate packages on module page

Created on 14 August 2013, almost 12 years ago
Updated 14 May 2025, 1 day ago

I'm sure this has been discussed a lot already, certainly over here: 📌 Introduce tags[] in module.info.yml file to categorize modules by provided functionality. Postponed: needs info and here: #2042443: Move modules related to web services to a separate package on the module listing page

On a default install of drupal 8 you get 2 packages, Core and Multilingual.

When you install Foo module the configuration is not config/core/foo, it's in some sub category like admin/config/development/foo, or admin/structure/foo or whatever.

I would suggest that we separate out the Core packages into similar subcategories on the modules page: (example package taken mostly from the configuration sub menu)

  • Core Appearance
  • Core Development
  • Core Content
  • Core People
  • Core Media
  • Core Multilingual
  • Core System
  • Core Web Services

I'm not suggesting that we use those exact names, but something similar to the url subgroup they belong to for continuity.

I am suggesting that they all start with 'Core' so that they are easily differentiated from contrib modules, and they all naturally group together.

I think this would be a big usability improvement, and a quick win.

Feature request
Status

Closed: duplicate

Version

11.0 🔥

Component

system.module

Created by

🇳🇿New Zealand sphism

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024