shadcn.io is an independent project built on shadcn/ui
The bar shows Products and Company. Products lists Product 1 through Product 4. Company lists About, Team, Careers, and Contact. Each list opens under its own trigger.
Keep each panel under its own trigger when the lists are short. A Dropdown Menu fits one menu that is not part of a site bar. In React, Base UI moves between the triggers with Tab.
Installation
Anatomy

Usage
<div className="w-full max-w-md rounded-md border bg-background p-px">
<NavigationMenu>
<NavigationMenuList>
{sections.map((section) => (
<NavigationMenuItem key={section.trigger}>
<NavigationMenuTrigger>{section.trigger}</NavigationMenuTrigger>
<NavigationMenuContent>
<div className="flex w-48 flex-col">
{section.items.map((item) => (
<NavigationMenuLink
key={item.label}
render={<Link href={item.href} />}
>
{item.label}
</NavigationMenuLink>
))}
</div>
</NavigationMenuContent>
</NavigationMenuItem>
))}
</NavigationMenuList>
</NavigationMenu>
</div>FAQ
How does each panel open under its own trigger?
Base UI always opens panels in one popup, which moves to the trigger that is open, so the demo passes no prop.
What are the links?
Products lists Product 1 to Product 4, and Company lists About, Team, Careers and Contact, from two sections at the top of the file.
How do the links use my router?
Each link is your router's link rendered through NavigationMenuLink, so it keeps the menu's styles and focus handling.
NavigationMenuLink takes the Next.js Link through render, as in render={<Link href="#" />}.
API Reference
Navigation Menu
No extra props in this demo. The rest is on the Navigation Menu page.



