Dataface Tasks
    Heartbeat snapshot (JSON)

    Starter dashboard composition patterns

    IDGRAPH_LIBRARY-STARTER_DASHBOARD_COMPOSITION
    Statusnot_started
    Priorityp1
    Milestonem3-public-launch
    Ownerdata-viz-designer-engineer

    Problem

    Playground examples can prove that charts render, but they do not yet amount to reusable dashboard composition patterns. There is a later-stage chart-library job in turning the basic chart corpus into deliberate starter dashboards that combine summary, comparison, trend, and detail in a coherent way. This should not block the first pilot chart batch, but it should become an explicit later initiative rather than staying an implied follow-on.

    Context

    • Dashboard composition is where KPI and table support become especially valuable.
    • This work likely starts from improving and extending the playground examples rather than inventing a separate dashboard system from scratch.
    • The goal is not full dashboard-factory maturity; it is starter composition patterns that move beyond isolated chart examples.

    Possible Solutions

    • Leave dashboard composition implicit. Easier in the short term, but it makes composed-surface quality nobody's explicit job.
    • Jump straight to polished dashboard packs. Valuable eventually, but too large for the first composition push.
    • Recommended: start from the existing playground examples, improve them into a small set of starter dashboard patterns, and use that work to inform later dashboard-factory and chart-library composition quality.

    Plan

    • Define a few starter dashboard compositions that combine summary, comparison, trend, and detail.
    • Improve and extend the playground examples into those starter patterns.
    • Build them from the shared chart corpus under the available style packages where useful.
    • Note where chart-level decisions break down once multiple charts coexist.
    • Feed those findings into later dashboard-factory and chart-library work.

    Implementation Progress

    • This is later than the initial chart-batch milestone; it should not block M1.
    • Recommended composition ingredients: KPI, one comparison chart, one trend chart, and one detail table.

    QA Exploration

    • [ ] QA exploration completed (or N/A for non-UI tasks)

    Review Feedback

    • [ ] Review cleared