Next dashboard components

Next dashboards (dashboard-v2 node, DashboardVersion="Next", ui/dashboard) bind widgets through v2 layout (components.rows) and the Heat data service ($heat-dataservice channels). Configuration and payloads differ from Legacy components even when the same React component renders underneath.

Concepts (realms, channels, direct ingestion): Next data service and direct ingestion.

How wiring works

1. Runners publish $heat-dataservice (see dashboard-v2 upstream contract and dataservice concepts).
2. Layout rows set "component": "<ComponentId>" (e.g. MapDisplay) plus a configuration block (channels, titles, widget-specific options).
3. Data-service wrappers (e.g. MapDisplayDS) load channel data at playback time.
4. Widget config (e.g. mapConfig, composableChartItem) usually lives in layout configuration, not in the channel payload.

Component ids in layout are not the same as Legacy mount ids in all cases, but many names match (e.g. MapDisplay).

Component manifest (build-time)

Building ui/dashboard runs npm run build:manifest, which writes dist/dashboard-component-manifest.json. Source of truth: ui/dashboard/src/dashboard-manifest/registry.ts.

Dataservice migration

Full status table, reference JSON paths, and partial/layout-only notes: Dataservice migration status.

All components (14)

Reference JSON (maximal examples): tools/arbex/reference/next/<ComponentId>.json

Arbex RAG (per-widget): tools/arbex/rag/reference/components/

Authoring new pages

Copy _page-template. Document layout configuration, channel shape, and payload fields separately.

Related

• Dataservice migration status
• Next data service
• Legacy dashboard components
• dashboard-v2 upstream contract