Skip to content

allow nested menu parents without a link themselvesΒ #3528

@sleidig

Description

@sleidig

As an admin I want to create nested menu structures but the grouping/parent item does not always have a target/link that it should open.

Currently, "link" is a required field when configuring menu items. However, for some "parent" items, we may want to only expand and show submenu items when it is clicked, without navigating anywhere itself.
The menu already supports this, if we delete the link property from the config in JSON. The UI doesn't allow that yet, however.

Image

The link field should indeed be mandatory if the field doesn't have sub-items. But you need to create an item first before you can add submenu items ... This is a bit of a chicken/egg problem. What kind of UX can we design for this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Client: by XType: UXconcerning user interface and in a broader sense user experience

    Type

    No type

    Projects

    Status

    Triage / Analysis

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions