fix(ui): refine dashboard components for Warm Precision tone

- KpiCards: remove gradient/glow, flatten to data-oriented panels
- BandwidthChart: replace hardcoded blue (#38BDF8) with accent token,
  use token colors for axis text and cursor
- QuickActions: replace icon grid with command-style list rows
  with left-border hover interaction
- EventsTimeline: remove timeline/skeleton, tighten to log-stream
  layout with divide separators and monospace timestamps
- Light mode: bump border-default opacity 0.12→0.14, darken
  text-secondary for dense readability

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jason Staack
2026-03-21 12:04:28 -05:00
parent b39014ef47
commit 298ed89c75
6 changed files with 273 additions and 155 deletions

152
web_redesign.md Normal file
View File

@@ -0,0 +1,152 @@
We need to redesign the website to remove all startup / SaaS / marketing patterns.
Current issue:
It feels too “salesy” and corporate — like a product trying to convince people to use it.
That is the wrong tone.
---
## Core direction
This should feel like:
- a tool
- a system
- a project that exists because it needed to exist
NOT:
- a startup landing page
- a marketing funnel
- a conversion-optimized site
---
## Tone
- Direct
- Honest
- Slightly indifferent to whether the user signs up
- No hype language
- No promises
- No “transform your workflow” nonsense
---
## Remove immediately
- Any “hero pitch” language
- Any “why choose us” sections
- Any fake trust signals (logos, testimonials, “companies use this”)
- Any email capture / gated content
- Any “Get Started Now” pressure CTAs
---
## Replace with
### 1. Simple top section
- Project name
- One blunt sentence describing what it is
- Links:
- GitHub
- Docs
- Download / Self-host
- SaaS (optional, not emphasized)
Example tone:
“This is a network control system. Its in active development. Things may break.”
---
### 2. “What it does” (not marketing)
- Bullet points
- No adjectives
- No hype
Bad:
“Powerful, scalable, next-gen network automation”
Good:
- Monitor device state
- Push configuration
- Track changes
- Run commands across devices
---
### 3. “What it is not”
This is important for your voice.
Example:
- Not finished
- Not stable
- Not for everyone
- Not trying to replace everything
---
### 4. Screenshots
- Real UI
- No mockups
- No gradients / marketing framing
- No captions trying to sell
---
### 5. Development status
- Be explicit:
- versioning
- breaking changes
- expectations
---
### 6. Pricing (if present)
- Simple
- No anchoring tricks
- No “save 20%”
- No fake urgency
---
## Visual direction
- Use the same Warm Precision system
- No big hero sections
- No oversized typography
- No soft gradients
- No “landing page layout”
Layout should feel like:
- documentation
- system panel
- terminal-adjacent
---
## Anti-pattern check
If any section feels like:
- its trying to convince the user
- its trying to impress the user
- its trying to capture the user
Remove or rewrite it.
---
## Goal
The site should feel like:
“This exists. If you need it, youll understand it.”
Not:
“Please use this product.”