Navigation Menu
Navigation & layoutBrick 0.1.2

Navigation Menu

Navigation Menu provides site destinations with optional rich link panels through Atom-owned semantics and behavior.

Live example

Built from the published package

Interactive
Choose with confidence

Know when Navigation Menu is the right part

Use it when

Use it for primary destination links when some categories reveal rich groups of additional destinations.

Choose another path when

Do not use it for application commands, form choices, small action lists, or content tabs.

Installation and imports

tsx
import { NavigationMenu } from "@flowstack-ui/brick/navigation-menu";
import "@flowstack-ui/brick/styles.css";

The complete stylesheet above is the recommended default. For a measured route-aware build, replace it with the shared foundation and this component's stylesheet:

tsx
import "@flowstack-ui/brick/styles/core.css"; // once at the application root
import "@flowstack-ui/brick/styles/navigation-menu.css";

Add the modular stylesheet for every other Brick component the route renders. Do not combine modular styles with styles.css or tokens.css.

Quick start

tsx
<NavigationMenu.Root>
  <NavigationMenu.List>
    <NavigationMenu.Item>
      <NavigationMenu.Link href="/docs">Docs</NavigationMenu.Link>
    </NavigationMenu.Item>
  </NavigationMenu.List>
  <NavigationMenu.Viewport />
</NavigationMenu.Root>

Visual recipes and states

Controls are paintless until hover, focus, open, or active. Links and triggers use 32/44/48px sm/md/lg minimums. Compact chevrons communicate disclosure, current links use a one-pixel underline, and the measured IndicatorArrow connects the open trigger to the Viewport without becoming a second selection bar. The Viewport uses the restrained shared control radius by default; consumers that need a different brand treatment can set --brick-navigation-menu-viewport-radius without adding a behavioral variant. In vertical orientation, the Viewport follows Atom's measured active-trigger offset so the connector stays attached while panels of different heights replace one another.

Public contract

API

Start with the public parts and root options below. Components with multiple parts separate each area into its own named subsection.

Public exports are NavigationMenu, NavigationMenuRoot, NavigationMenuSub, NavigationMenuList, NavigationMenuItem, NavigationMenuTrigger, NavigationMenuContent, NavigationMenuLink, NavigationMenuIndicator, NavigationMenuIndicatorArrow, NavigationMenuViewport, NavigationMenuRootProps, NavigationMenuSubProps, NavigationMenuListProps, NavigationMenuItemProps, NavigationMenuTriggerProps, NavigationMenuContentProps, NavigationMenuLinkProps, NavigationMenuIndicatorProps, NavigationMenuIndicatorArrowProps, NavigationMenuViewportProps, NavigationMenuSize.

PropValuesDefault
sizesm, md, lgmd

Action-like rows accept tone="neutral" or tone="danger" when exposed; neutral is the default. Behavioral props come from the matching Atom parts.

Shared responsibility

Accessibility

Name icon-only triggers and label every command or destination clearly. Preserve Atom roles, keyboard behavior, focus return, disabled and selection states, dismissal, and forced-colors affordances.

Responsive behavior

Popup geometry stays collision-aware and constrained to available space. Narrow layouts preserve usable targets, logical alignment, zoom, and writing direction; applications decide whether the pattern belongs in their mobile information architecture.

Stable visual contract

Styling and tokens

Customization

Set documented variables on Root or Content as applicable. Use className and style for local layout without replacing semantic state, focus, or positioning attributes.

Tokens and CSS hooks

Public variables use the --brick-navigation-menu-* namespace for gaps, control geometry and states, focus, chevron, indicator, viewport surface and sizing, and motion.

Documented tokens are --brick-navigation-menu-gap, --brick-navigation-menu-control-min-block-size, --brick-navigation-menu-control-padding-inline, --brick-navigation-menu-control-radius, --brick-navigation-menu-control-foreground, --brick-navigation-menu-control-hover-background, --brick-navigation-menu-control-open-background, --brick-navigation-menu-control-open-foreground, --brick-navigation-menu-control-current-foreground, --brick-navigation-menu-focus-ring, --brick-navigation-menu-chevron-size, --brick-navigation-menu-chevron-stroke, --brick-navigation-menu-chevron-gap, --brick-navigation-menu-current-underline-size, --brick-navigation-menu-current-underline-offset, --brick-navigation-menu-indicator-size, --brick-navigation-menu-indicator-offset, --brick-navigation-menu-indicator-color, --brick-navigation-menu-indicator-border, --brick-navigation-menu-viewport-background, --brick-navigation-menu-viewport-foreground, --brick-navigation-menu-viewport-border, --brick-navigation-menu-viewport-radius, --brick-navigation-menu-viewport-shadow, --brick-navigation-menu-viewport-padding, --brick-navigation-menu-viewport-max-inline-size, --brick-navigation-menu-motion-duration.

Stable output includes data-size, component data-slot hooks, and Atom state attributes.

Advanced reference

Open these details only when you need to inspect DOM ownership, native forwarding, or lower-level composition.

Maintainer resources

Tests, playground evidence, source notes, and release history remain available without crowding the plug-and-play guide.