Every dashboard is only one render. Many charts on one board — one spec, one picture. If the text size or the padding looks off, tell your agent.
You do not pick one chart and stop. Put a callout beside a callout. Stretch a bar across the board. That is a dashboard: tiles, combined.
Every dash is only one render. Not a page of widgets each hitting the engine. One spec. One picture. The two boards below are each a single `dashboard` render.
The full plant-ops board — seven tiles, shop-floor sauce — is the next drop. Not this one.
Callouts plus a 35-country bar. Still one `dashboard` spec. Still one picture.
If a number looks huge or a bar looks cramped: tell your agent. Smaller type. More padding. Give the list more height. They change the spec. You are not editing CSS.
That comparison board is also one render. Tiles do not multiply engine calls.
Next News drop: the plant-ops dashboard — OEE, throughput, downtime, plants, the cost line. Seven tiles. Still one render. That's the full dash sauce. We saved it.
Type is `dashboard`. `tiles[]` — each `chart` is any other type. `span: [cols, rows]` to combine cells. `layout` for `cols`, `gap`, `pad`, `tileHeight`. Default fit is fill. If a tile looks wrong and you cannot see why, read the `layout:` sidecar. Dense boards: `specPath`.
Do not paste seven `render_chart` calls and call it a dash.
Doors: News · Archive · Get started