Skip to content

UI Shell Guidelines

InfraLynx product UI should feel like a calm control surface, not a marketing dashboard.

Visual Direction

  • dark-first foundation
  • restrained navy and steel surfaces
  • warm accent used sparingly for emphasis
  • expressive typography with strong hierarchy

Layout Rules

  • left rail for primary navigation
  • central workspace for the main task surface
  • right rail for context, status, and selected-item detail
  • avoid card mosaics as the default application language
  • top-level navigation should represent domains or working modes
  • sidebar grouping should separate platform, domains, and services
  • breadcrumbs should be generated from shared route metadata
  • context links should support the current route instead of duplicating the sidebar
  • labels should be operational and stable
  • active state must be visually obvious without relying only on color
  • avoid deep nested navigation until real domain workloads require it

Surface Rules

  • the main workspace should carry the strongest hierarchy
  • panels are acceptable when they clarify function, not as blanket framing
  • status and summary content should be dense but readable
  • motion should reinforce orientation and state change rather than decoration