Change "Extend" menu item to "Extensions".

While it's probably quite disruptive, I kind of agree. All the other links are nouns, but this is a verb. Help is both, but I read it as a noun, i.e. this is the page where you will find help (noun). Opened an MR, added the issue template and added screenshots.

Hi
I have tested MR 2010 on Drupal version 11.x
The MR is applied successfully...

The "Extend" menu item to changed with "Extensions".

Attaching screenshot

Usability review

We discussed this issue at 📌 Drupal Usability Meeting 2025-05-02 Active . That issue will have a link to a recording of the meeting.

For the record, the attendees at the usability meeting were @benjifisher, @rkoller, and @simohell.

Thanks for picking up this issue and already providing an initial MR. The group had a clear consensus about the point in #2447955-19: Change "Extend" menu item to "Extensions" → with Extend being a verb while the rest of the menu items are nouns. This is a detail that was also raised during the discussions in 📌 Locate drupalisms that might create confusion among users Active and in the following we’ve encountered it again during the noun foraging exercise for Drupalisms.

We’ve then taken a look at the bigger picture, at this point the extend page only contains modules. Project browser is adding the concept of recipes to the extend page. In the future there is also the plan to add the concept of themes there as well. In parallel there is also the plan to restructure the information architecture of the admin ui: 🌱 Restructure the admin interface Information Architecture Active . In that context there was also one idea voiced in the course of an ux meeting and summarized in the second part of: #1973322-26: Add drop-buttons to the appearance page → about moving the theme list page into the extend page as well.

Taking these circumstances into account, we’ve then asked ourselves, is Extension the right choice or is there maybe a more clear alternative as the top-level menu item?

First we’ve looked how that kind of concept is called in other CMSes - WordPress for example uses Plugin. Problem with that noun, in the context of WordPress it is only the counterpart to the concept of modules in Drupal, while in the context of Drupal the term is already used as a “sub” concept of the concept of modules even though the user doesn’t have many touch points in the micro copy with that concept - so we’ve discarded it.
The other term that we’ve discussed was Project which is already used in the context of project browser as well on d.o. Problem with that, the term is way too generic plus it is missing some sort of cue what the purpose of that concept actually is - “project” is sort of too neutral.

Extension on the other hand clearly expresses the purpose of concepts like modules, recipes, and themes to extend Drupals function wise, at the same time all top level menu times become nouns. And we suspect that some people might won’t even notice the change if they only skim the top level menu items. So over all we had a clear consensus to agree to change the verb Extend to the noun Extensions.

If you want more feedback from the usability team, a good way to reach out is in the #ux channel in Slack.

one detail i forgot to mention, we've also wondered if it might be necessary in a followup to update some of the documentation on d.o? the core codebase seems already properly covered by the MR. we haven't had the time during the meeting to do any in depth research in that regard