Skip to main content

Navigation

Status: No dedicated documentation exists in design-system-docs (checked main + all open PRs, verified 2026-08-19). This is a factual scaffold, not real guidance — every qualitative section below is an explicit placeholder for a human writer. Nothing has been invented.

Source: DTSL/design-system → packages/product/organisms/navigation/src/types/Navigation.types.ts (package @dtsl/navigation, exported as Navigation, updateGHBadge)

Props (verbatim from source)​

export interface NavigationProps {
	navData: NavData
	activeIndices: string[]
	nonMenuIds?: string[]
	loading?: boolean
	isNavExpanded: boolean
	onToggleNavigation?: () => void
	isNavToggleAllowed?: boolean
	collapseTooltipText?: string
	expandTooltipText?: string
	theme?: ThemeType
	className?: string
	mainMenutext: string
	variant?: NavigationVariantType
	managePlacement?: boolean
}

NavData, ThemeType, NavigationVariantType not extracted here — see source for full shapes. The updateGHBadge export suggests this integrates with GlobalHeader's badge system (see global-header) — worth confirming the actual integration when writing the real doc.

When to Use​

TODO — no existing UX/product guidance found in source, Storybook, or docs. Needs input from design/PM.

When NOT to Use​

TODO — needs UX/product input.

Decision Logic​

TODO — needs UX/product input on variant/theme selection and collapsed vs expanded (isNavExpanded) usage rules.

Accessibility​

TODO — needs UX/product input. Primary navigation typically needs a genuine landmark role and keyboard-operable expand/collapse — needs verification against the actual implementation, not assumed here.

Common Mistakes​

TODO — needs UX/product input.