Polish dashboard UI and add audited, forkable examples - #30
Merged
Conversation
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 dashboard needs stronger visual hierarchy, readable charts on narrow screens, and complete examples that forkers can adapt safely.
This PR adds contrasting metric tiles, geometry-preserving chart reveals, contained chart scrolling, visible data disclosures, and touch/keyboard donut selection. It removes misleading positional hover effects and uses neutral change text when a number's sign does not determine its meaning.
Three complete synthetic dashboards live under /examples: daily cockpit, money overview, and work focus. The examples have deliberate block spans, coherent next actions, source warnings, and reconciled cash-runway calculations.
npm run examplesignores local identity and private snapshots. The existing schema and owned shadcn-compatible primitives remain in place.The design system documents composition, tokens, motion, accessibility, and fork adaptation. The UI audit records findings and limits. Twelve full-page local Chromium screenshots cover all examples on desktop/mobile in light/dark.
Validation:
Screenshots and reproduction: examples/README.md
Audit: docs/ui-audit-showcase.md
Scope is zaati-os only. No private repository, scheduled task, or deployment changes. Browser emulation and automated checks do not replace physical-device or human screen-reader testing.