Menu Rule provider

[ns8482e]

Allow Site administrator to manage Admin menu according to their needs.

• Provide a Menu Rule provider json file menu.json similar to the placement
• Allow author to write rules to show/hide/position of the placement in the menu.json
• Navigation provider - evaluate the menu rule before adding menu to the menu items.

This will allow site administrator to control menu items and their order without change in orchard core code base.

Ref
#17112 (comment)

[MikeAlhayek]

I agree with this. It would be great to be able to use existing placements structure to define the position of each menu level/menu-item.

[sebastienros]

Configuration then. Deployed with the app. Like placement. And optional, meaning it shouldn't make menus implementation harder, only for the people who don't like @MikeAlhayek 's menu.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[ns8482e]

Configuration then. Deployed with the app. Like placement. And optional, meaning it shouldn't make menus implementation harder, only for the people who don't like @MikeAlhayek 's menu.

New structure is fine as long as it's applies to new sites, I personally prefer to have upgrade seamless, and new UI should be opt-in for existing sites and not other way around