BluKavantUI Design system
PATTERNS

Navigate a workspace

Pair a stable hierarchy with a focused detail view.

A REAL-WORLD SCENARIO

Move between records while keeping the context.

Use for a document browser, customer workspace or service console where a persistent navigation pane supports a focused detail area.

  1. 01Keep the hierarchy visible.
  2. 02Resize or collapse supporting content.
  3. 03Return without losing the draft.
STATE REFERENCE

Design beyond the happy path.

Select a state to see what the interface should communicate. These are illustrative snapshots; try the live component below.

EXAMPLE WORKSPACEBrowse

Customer workspace

Customers / Atlas Labs

Navigation
Atlas Labs · selected
Details
Account overview
Inspect customer
DESIGN INTENT

Browse

Highlight the active destination and keep its name in the content heading. Navigation should explain where the person is.

Try the working example ↓

WORKING EXAMPLE

Navigate a workspace

Component reference →

Type a note in the detail pane. Resize the divider, collapse the first pane, then expand it. Check that your note remains. Focus the divider to try its keyboard controls.

DESIGN DECISIONS

Make the important choices explicit.

Hierarchy depth

Use a simple NavigationMenu for a short list and TreeView for a genuinely nested structure.

Focus management

After opening a new view, make the destination clear. Restore focus to a useful trigger when returning.

Small screens

Prioritize the current task. Avoid squeezing two desktop panes into unreadable columns.

CONNECT YOUR APPLICATION

Keep the behavior. Bring your data.

The examples demonstrate interaction using sample data. Your application owns the real records, permissions and persistence.

01Routing
Connect navigation events to your application’s routes or selected record.
02Draft preservation
Keep draft data independently of whether a pane is visible.
03Layout preferences
Decide whether to remember pane size, and provide sensible defaults.
All patterns →

Search BluKavantUI