The Storage data page is unavailable for the content navigation block in the navigation module

Problem/Motivation

Unfortunately I was unable to install the Storage module on the main branch which is on 12.x meanwhile - somehow it hasn't worked out using the Lenient composer plugin. So the latest changes in the context of the navigation module were unavailable for testing but when installing storage 1.4.0 on the latest stable 11.3.3 there are two problems:

The local task Storage data is unavailable as a top level menu item in the content navigation block

When expanding the create submenu none of the created storage types are available, only the ones shipping with the standard profile are there:

Steps to reproduce

• Install the storage module
• Install the navigation module
• Add one or two storage types and then check the navigation sidebar and the create submenu

Proposed resolution

Add a menu link for the Storage data page (admin/content/storage) to the root of the content menu on menu/manage/content and add all the storage types created as child menu items of the create menu link.

some context: we've touched this problem space during todays usability meeting #3574712: Drupal Usability Meeting 2026-02-27 where we've discussed some usability issues in the context of the navigation module. One of the problems #3427660: Make the order of menu items in the content menu consistent with the order of primary tabs on /admin/content is that the list of top level menu items in the content navigation block can differ in number and order to the list of local tasks on admin/content. The cognitive load is high if for example the position of a certain page in the navigation sidebar is different than in the local tasks list (for example blocks and content are switching places). same as if another page has a local task but no top level menu item (for example comments). And we also wondered how the navigation would behave for contrib modules that are adding a local task to the content page - that is how i ended up up testing the storage module with the navigation module. I will post a summary of todays discussion to the aforementioned issue over the weekend. and in regard of the second point form the proposed resolution a word of caution. The navigation module seems to have some sort of caching issue and if the name of an entity is changed/updated or sometimes even if a new entity is added that change isnt reflected in the list shown in the create submenu (see #3569243: Updates to content type names are not reflected in the menu item labels).

Remaining tasks

User interface changes

API changes

Data model changes