Using the Dashboard

Using the Dashboard

Mission Control UX beyond the Actions grid. Deep: using-the-dashboard.md · Tutorial 10.

Surfaces

Element	Purpose
Boot splash	Short warm-up on first load
Hero	Health banner, pods/replicas/last run/pass rate, primary Smoke CTA
Signal field	Live constellation behind the hero
Glass topbar / footer	Sticky brand + status
Workloads / Pods	K8s strip + log drawer (needs kubeconfig / SA)
Actions grid	All job cards
Live job panel	Stream, ✓/✗ chips, Stop, copy/download
Schedules	Recurring monitors — Schedules and Findings
Findings	Aggregated issues from quality jobs
QA Runs / Videos	History + recorded journeys
Command palette	⌘K / Ctrl-K

UX extras

Cue	How
NOC wall	Double-click Zyvor Mission Control brand
Warp	` or type zyvor
Refresh	r
Close log drawer	esc
Achievements	First visit / NOC / warp toasts
Reduced motion	Honors prefers-reduced-motion

Auto-refresh ~every 5 seconds.

Browse vs act

Reading pods/history/findings is safe. Starting jobs hits the target under test and writes reports/ — confirm URL, credentials, and scope before Run.

Practice

Test zyvor.dev · Common Workflows · Mission Control (Actions overview)