Skip to main content

Revenue Dashboard

A single-page quarterly revenue dashboard for the fictional Aurora Cloud, Inc. — the kind of report a CFO takes into a board meeting. KPI tiles, a segment donut, a year-over-year bar chart, a recurring-revenue trend line and a segment table, all on one page.

The point of this example is not that it has charts. It is where the charts come from.

  • The charts are native vector, in both formats. Most engines export charts as flattened images: dead pixels that blur when you zoom, can't be edited, and quietly drift when you switch from PDF to Word. Here every chart is drawn from canvas primitives — the donut is filled arc paths, the bars are rectangles, the trend is a path with an area fill. The result renders as native, editable vector in both the PDF and the DOCX. No screenshots, no embedded PNGs, no separate charting library.
  • One JSON source. The same document definition produces the PDF and the DOCX. There is no second template, no manual port, and no Word-version surprises — the layout is computed once and emitted to each format's native drawing model.
  • Real data binding. The KPI tiles, the segment table and the commentary line all read from a companion *.data.json ($data.kpis, $data.segments, $data.summary), so the numbers live in data, not in layout.
  • Drawn to scale. The donut sweeps, bar heights and trend points are plain coordinates — easy to generate from your own figures, and laid out by the same engine that sets the type around them.

Everything here — chart geometry, KPI tiles, the data-bound table, the running footer — is declared in one plain-JSON source file.

Features used: Canvas, Data Binding, Tables, Columns, Separators, Styles, Headers & Footers