Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

2026 renderer roadmap — the hyper-specific demo

The first concrete Gantt: nine rows for the M-* milestones, one bar per milestone, three owners. Used as the shared fixture by:

  1. The snapshot test tests/gantt_snapshot.rs.
  2. The storybook story s_chart_gantt_2026_roadmap.
  3. This chapter (hero PNG).

When the fixture changes, all three regenerate together.

Target visual

gantt
    title 2026 Renderer Roadmap — target visual
    dateFormat YYYY-MM-DD
    axisFormat %b

    section Renderer
    M-VEC     :2026-02-01, 6w
    M-MASK    :2026-03-01, 7w
    M-BLEND   :2026-04-10, 7w
    M-FILTER  :2026-04-25, 7w
    M-TEXT    :2026-05-15, 7w
    M-BOOL    :2026-07-01, 11w
    M-CHART   :2026-09-15, 9w

    section App
    M-INT     :2026-08-01, 11w
    M-EXPORT  :2026-10-01, 11w

Mermaid here, wgpu in production

The diagram above is rendered by mdBook's mermaid plugin so the book always shows the intent. The hero PNG (lands when the render pass ships) is the actual wgpu output. They're separate artefacts on purpose — the mermaid version is for the book, the wgpu PNG is for product fidelity verification.

Hero asset (regenerated by just snapshots)

When chunk 3 (render pass) lands, this section embeds:

![2026 roadmap rendered by wisp-chart](../../../assets/wisp-chart/gantt-2026.png)

Try it live

Run wisp-chart in Chrome via WebGPU — the same fixture rendered in a browser tab.