Repository navigation
feat(dash0): tonal gradients between the flat and the shiny look - #603
Merged
Merged
Conversation
The flat redesign (#582) removed every gradient and the dashboard read as dull. This brings a few back, tonal and without glow. - One gradient token, --primary-gradient: cyan-blue to electric blue, never violet. It paints the default button, the page-header tile and the progress fill. Hover slides it to its darker half. White text clears 4.5:1 on every stop. - KPI tiles take a tone (primary, ok, warning, error, neutral): a colored icon chip and a faint wash from its corner. Zero down or zero incidents stay neutral. - The status banner is washed with its status color from the left edge, instead of a 4px left border. - Onboarding card: a 2px primary line on top, the gradient tile, a wash on the "next up" row. - Still no tinted shadow, no blurred blob, no hover lift, no page glow in the org app. Unit and e2e tests and the design reference document the new rules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #603 +/- ##
==========================================
- Coverage 83.34% 83.30% -0.05%
==========================================
Files 1238 1238
Lines 127020 127020
==========================================
- Hits 105868 105813 -55
- Misses 21143 21198 +55
Partials 9 9 🚀 New features to boost your workflow:
|
fclairamb
enabled auto-merge (squash)
October 18, 2026 20:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The flat redesign (#582) removed every gradient and the dashboard read as dull. This brings a few back, tonal and without glow.
What changed
One gradient token
--primary-gradient: cyan-blue to electric blue (hue 245 to 270), never blue to violet. Same in both themes.bg-primary-fill.background-positiontransition). The button does not move.theme-tokens.test.ts).Status washes
KpiTiletakes atone(primary,ok,warning,error,neutral): a colored icon chip and a faint wash from its corner. Zero down or zero incidents stay neutral, so color only shows up where it means something.Still out
The design reference documents the new rules (Buttons & badges → Gradients, KPI tiles, status banner, color tokens).
Tests
cn()handling ofbg-primary-gradient. 2665 pass.electric-identity-*anddestructive-button-shadowspecs pass. The content-area scan now allows only the primary gradient and washes that fade to transparent, with positive controls for a glow and an opaque gradient.dashboard.spec.tsandempty-state-onboarding.spec.tspass.onboarding-checklist.spec.ts"dismissing survives a full reload" failed once on SQLite: a pre-existing race (it reloads before the dismissalPUTlands), unrelated to this change, tracked separately.🤖 Generated with Claude Code