[PLAN] Use Menus to generate the links in the sidebar [#3381754]

Problem/Motivation

The navigation prototype is an HTML mockup where the menu links have been hardcoded. In order to progress further and enhance the functionality of our prototype, we need a plan to transition from using hardcoded links to integrating Drupal menus. This adjustment will help us analyze the usage of our existing menus and strategize the creation of new ones.

Our current objective is to integrate four new menus, each with its unique set of requirements and potential modifications:

Administration Menu - To refine this menu, links such as 'Content' and 'Help' might need to be removed.
Rename Shortcuts to Bookmarks - The 'Shortcuts' menu is intended to be rebranded as 'Bookmarks'. We need to discuss the new name's alignment with the system's objectives to ensure consistency in terminology.
User Account Menu - We need to determine whether to include a thumbnail of the user's image in the MVP.
New Content Creation Menu - Should this menu be integrated within the existing navigation module, or would it be more effective as a separate entity? Additionally, we need to decide which items will be included in the Create menu.

Proposed resolution

Move from the hard-coded HTML prototype

#3383896: Generate menu items using plugins

MVP - Move to menus

Menus - customization beyond the MVP

Comments

Comment #1

17 August 2023 at 18:55

baluv3 created an issue. See original summary.

Comment #2

lauriii

he/him

Finnish

Finland

commented 30 August 2023 at 14:12

There's some work in progress in #3383896: Generate menu items using plugins.

Comment #3

ckrina

she/her

Catalan

Barcelona

commented 18 September 2023 at 10:00

Just added #3387957: Define logo origin on the Toolbar since we'll likely have to define this soon.

Comment #4

mherchel

he/him

English

Gainesville, FL, US

commented 18 September 2023 at 18:49

Just merged #3383896: Generate menu items using plugins.

Had discussions that fit into this issue with @deviantintegral and @tedbow at https://drupal.slack.com/archives/C7AB68LJV/p1695052420501349.

Both of them are confused on where the data is coming from.

From @tedbow

I am little confused about the purpose of this issue vs using the menu system. It sort of uses the menu system, as in NavigationAdmin uses a menu but NavigationUser does not. Eventually will these all use menus? If so couldn’t you have just as much control over the markup by just having specific templates for these menu rather than just introducing the new NavigationSection concept
does 'base hook' => 'menu', mean that all the theme process stuff will still apply to these navigation sections also? (edited)

from @deviantintegral

I was also a little confused about this, but assumed I'd just missed prior context. The big thing I see is that I could see modules adding items to navigation sections that aren't menus, but some other UI widget. Like I think environment indicator is a good example of that? But I also think until we start wanting to create releases there isn't much harm in merging the MR, given that it's less hardcoded than the current code.