Repository navigation
Recommended way to implement a static menu? #2503
Replies: 1 comment
|
DropdownMenu, ContextMenu and Menubar are all built around Presence + Popper, they're fundamentally popover components (something you trigger, that floats and positions itself relative to an anchor), so trying to force one into an always-visible sidebar fights the component's whole design, even with For a persistently rendered menu with nested items, <NavigationMenuRoot orientation="vertical">
<NavigationMenuList>
<NavigationMenuItem>
<NavigationMenuLink href="/settings/profile">Profile</NavigationMenuLink>
</NavigationMenuItem>
<NavigationMenuItem>
<NavigationMenuTrigger>Settings</NavigationMenuTrigger>
<NavigationMenuContent>
<NavigationMenuLink href="/settings/billing">Billing</NavigationMenuLink>
<NavigationMenuLink href="/settings/security">Security</NavigationMenuLink>
</NavigationMenuContent>
</NavigationMenuItem>
</NavigationMenuList>
</NavigationMenuRoot>
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello. I'm trying to understand the recommended way to implement a static menu (rendered in place, not a dropdown).
I see components like
DropdownMenu,ContextMenu, andMenubar, but I couldn't find a pattern for a menu that is always visible, such as a sidebar menu or a list of actions/settings, with possible nested items.What is the intended approach for this use case?
Thanks.
All reactions