60 lines
2.5 KiB
Markdown
60 lines
2.5 KiB
Markdown
# Analytics Workspace Showcase
|
|
|
|
- Status: `completed`
|
|
- Owner: `codex`
|
|
- Date: `2026-03-25`
|
|
|
|
## Goal
|
|
|
|
Add a full-screen Storybook scene that proves the current Cadence UI component set can
|
|
compose a polished revenue operations dashboard similar to the provided reference without
|
|
introducing one-off primitives or drifting away from the active Material-inspired design
|
|
language.
|
|
|
|
## Scope
|
|
|
|
- In scope:
|
|
- add one new `Scenes` Storybook story for a revenue analytics workspace
|
|
- compose the page from the existing component surface plus lightweight layout-only markup
|
|
- keep the scene responsive so it remains readable on desktop and mobile widths
|
|
- validate the result in Storybook and through the docs build
|
|
- Out of scope:
|
|
- adding new shared components or changing existing component APIs
|
|
- matching the reference screenshot's exact monochrome branding over Cadence UI's active tonal system
|
|
- adding this scene to the curated smoke contract unless it becomes a required regression surface
|
|
|
|
## Constraints
|
|
|
|
- Follow `DESIGN.md` over the raw screenshot when visual details conflict.
|
|
- Reuse existing components such as `Card`, `Input`, `Badge`, `Avatar`, `Button`, `Tabs`, and `Progress`.
|
|
- Keep the implementation isolated to docs surfaces unless a clear shared gap appears.
|
|
|
|
## Affected Surfaces
|
|
|
|
- `apps/docs/src`
|
|
- `docs/exec-plans`
|
|
|
|
## Plan
|
|
|
|
1. Add an execution plan so the scene work is resumable and reviewable.
|
|
2. Build a new full-screen Storybook scene that mirrors the reference information architecture:
|
|
sidebar, hero header, KPI cards, trend chart, and AI summary panels.
|
|
3. Use the running Storybook instance to inspect spacing, hierarchy, and responsive behavior.
|
|
4. Run the narrowest useful docs validation suite and record the outcome.
|
|
|
|
## Validation
|
|
|
|
- `pnpm harness:validate:docs`
|
|
- browser review against the local Storybook instance on `http://localhost:6006/`
|
|
|
|
## Orchestration Task Sketch
|
|
|
|
- `T1`: add the new dashboard showcase scene
|
|
- `T2 -> T1`: inspect and validate the scene in Storybook
|
|
|
|
## Status Log
|
|
|
|
- `2026-03-25 15:45` started plan for a new Storybook dashboard scene based on the supplied analytics reference
|
|
- `2026-03-25 16:02` added `Scenes/Revenue Dashboard`, verified `pnpm harness:validate:docs`, and reviewed desktop/mobile rendering against the local Storybook iframe
|
|
- `2026-03-25 16:04` noted an unrelated existing Storybook dev-index failure from `apps/docs/src/components/progress.stories.tsx` that does not block direct iframe review of the new scene
|