Drupal CMS Extend menu page titles don't match tab labels

Created on 21 February 2025, 16 days ago

Problem/Motivation

I am reviewing Drupal CMS with my marketeer hat on.

Under the "Extend" menu, the sub-menu page titles do not match the tab labels. There is also one duplicate page title.

There are six tabs displayed:

  1. List tab - page title "Extend". This is the default tab, so understood this might not match.
  2. Recommended tab - page title "Browse projects". This is a duplicate of the next tab's page title and doesn't reflect the page's content, which is a list of Recipes. Perhaps change both to "Browse recipes".
  3. Browse modules tab - page title "Browse projects". Change so they match.
  4. Update tab - page title "Update". These match.
  5. Update Extensions tab - page title "Automatic Updates Form". This page doesn't perform automatic updates; I need to perform these manually, so it is poorly named. Change page title to match the tab label.
  6. Uninstall tab - page title "Uninstall". These match.

There is inconsistent capitalisation between "Browse modules" and "Update Extensions".

What's the difference between a project, module and extension in this context? All three terms are used within just the tab labels and page titles under the Extend menu? Will our marketeer persona understand the difference or just get confused?

Steps to reproduce

Drupal CMS base install on local. No additional content types or recipes installed.

Proposed resolution

Change the tab labels and/or page titles as suggested above, with consistent capitalisation and nomenclature.

🐛 Bug report
Status

Active

Version

11.1 🔥

Component

update.module

Created by

🇬🇧United Kingdom dunx

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @dunx
  • 🇮🇳India GGH

    This not for Drupal Core, This is for Drupal CMS project.

    Can someone change this Project, Not able to do from my side or is this project still not open for issues?

  • 🇳🇿New Zealand quietone

    Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies .

  • 🇬🇧United Kingdom catch

    @ggh you need 'Drupal CMS development repository' as the project.

  • 🇦🇺Australia pameeela

    What's the difference between a project, module and extension in this context? All three terms are used within just the tab labels and page titles under the Extend menu? Will our marketeer persona understand the difference or just get confused?

    I totally agree with this sentiment, however, we can't address these fundamental issues by renaming pages and tabs. To this end we are working on a full overhaul of this section and its IA. We are still in the early planning of this so I don't have any issues to point to yet.

    Also, these pages come from three different places: core (Extend and Uninstall), Project Browser (Recommended and Browse modules) and Automatic updates (Update and Update extensions). AU already has an issue: 📌 Update tab and page title to be more clear Active and Consider displaying the core and extensions update forms on one page Active is also relevant. PB is moving super fast and frequently, so I think this is a moving target and not really worth addressing until it gets a bit closer to stable. If you want to propose a change to the core 'Extend' tab, I'd suggest you create a core issue with the specific change you are proposing.

    I appreciate that marking this 'won't fix' may seem strange since the changes are totally sensible, but there's nothing that we can do about this in Drupal CMS itself.

  • 🇦🇺Australia pameeela

    Oops

  • 🇬🇧United Kingdom dunx

    Understood. It is getting increasingly difficult to know where to target issues. I'm looking at Drupal CMS to try and suggest improvements to that as a product, but it's a bit of a Frankenstein's Monster, with parts taken from all over.

Production build 0.71.5 2024