[tylercschneider]

One Sentence Summary

A developer building a dashboard page that already has its widgets' data can now draw each widget in the page itself, without one extra request per widget.

ACs Covered

• A host that passes a block when drawing a dashboard gets each shown registered widget drawn from that block inside the page, with no Turbo Frame.
• Widgets drawn from the block keep the order and visibility the dashboard saved, on a dashboard drawn for viewing and on the grid an editor arranges.
• A dashboard drawn without a block loads each widget through its own Turbo Frame as before.
• Widgets built from a widget definition are not drawn from the block and still load through their own frame.

Decision Log

How does a host draw a dashboard's widgets inside the page's own request?

The host passes a block that DashKit calls with each shown widget's key in the saved order, over DashKit loading data or a per-widget request.

Code Example

dash_kit_render_widgets(config: dashboard) { |widget_key| content_tag(:p, "Drawn #{widget_key}") }

Out of Scope

• The host app dyb_web switching its client stat cards to this block is a separate pull request in that repo, after this is released.

Ticket Billed Against

Not specified.

Tokens Used

Not measured.

Effort

Not measured.

Time Spent

Not measured.

---

Generation Metadata

Scribe: pr-scribe bf13783
Rules: pr-body d344bb1, draft-reading 0d470c5, writing-style c3c2f61
Model: claude-opus-5-5, cc 2.1.303

🤖 Generated with Claude Code