Skip to content

Navigation UX Guidelines

InfraLynx navigation should feel steady under load and obvious at a glance.

  • the left sidebar remains persistent across domain changes
  • the top bar updates page identity without shifting layout structure
  • the right rail provides context and actions without becoming a second menu

Usability rules

  • users should always know which domain they are in
  • users should see the current hierarchy before they need to scan content
  • primary route changes should not hide search or destabilize the workspace grid
  • active state must be visible through shape, contrast, and emphasis, not color alone

Spacing and layout

  • keep the rail, top bar, workspace, and context rail on a fixed structural grid
  • maintain consistent padding rhythm between navigation surfaces and content
  • avoid adding local navigation styles that break the shell pattern

Context-aware actions

  • quick actions belong in the top bar when they support the current route
  • supporting references belong in the context rail
  • route-specific actions must not replace the global navigation model