Skip to main content
Every widget is two halves. The pipeline says which data-source tools to call and how to shape the rows that come back. The payload is the chart or table configuration that draws them. Refreshing re-runs the pipeline. Restyling touches only the payload. The two are independent, which is why changing a chart’s colors never re-fetches anything.

​
Kinds of widget

Built on Apache ECharts. Line, bar, area, scatter, pie and the rest. The chart kind lives in the configuration rather than in the widget type, so asking to “make that a bar chart instead” is a restyle and not a new widget.
Vistazo’s own renderers, for the shapes a charting library handles badly. A single headline number, a data table, a pivot, a progress meter.
For charts the built-in renderers cannot express, such as chord diagrams, beeswarms, ridgelines, hexbins and waterfalls. These are authored code that draws SVG, kept as entries in the workspace Library and rendered in a sandbox. A widget points at an entry and never inlines the code.
Prose on the canvas. The only widget kind with no data pipeline.

​
Structure: headings, dividers, spacers

Markdown widgets can drop their card frame, which is what turns them from content into structure. A framed heading renders as another tile at the same visual weight as the charts it is meant to sit above. Unframed, it reads as a heading. The spacer matters more than it sounds. The grid compacts upward, so deliberate whitespace cannot be made by leaving a gap.
Data widgets keep their frame on purpose. The frame carries the title, the expand control, and the discussion button with its comment count. That count is the only way to see a chart has a conversation on it without touching it.

​
Discussions

Every data widget has a discussion thread anchored to it. Open it from the widget header, and @mention a colleague to notify them. Threads live with the widget, so the conversation about a number stays next to the number.

​
Editing a widget

Once a widget is on a dashboard it is edited in place, with no round trip back through a chat preview. Editing means asking. There is no properties form and no Save button, on the canvas or in the expanded widget. Ask Vistazo AI on the dashboard, or your own agent:
Drop the 2019 bar. Label this in millions. Make it a line chart instead. Point it at the new table.
Title, description, appearance, and which source feeds it are all reachable that way. When an edit carries a new transform, Vistazo validates it before writing anything, so a broken one is refused rather than leaving you with an empty widget. An edit that supplies rows directly, or that only changes styling, runs no such check.

​
Limits

A dashboard holds up to 100 live widgets, and archived ones do not count. See Limits.