{}
This track walks through what BESPA is doing on every request and every interaction. Read this if you want a precise model of incremental updates, page nesting, and how a click in the browser turns into a targeted DOM swap.
Topics
autorenew Incremental updates
State variables drive partial-DOM redraws. The smallest possible patch goes over the wire and replaces only the affected widgets.
link The action-URL pattern
The four URL shapes the framework interprets: ? for state, ^ for the parent page, ~ for the top page, and everything else for normal navigation.
dashboard_customize Embedded pages: overview
The three mechanisms for putting one page inside another — inline embeds, overlays, named frames — side by side, with a table you can use to pick.
view_quilt Nesting pages
Embed one BESPA page inside another to compose dashboards, split panes, modal flows, or any structure where a sub-page has its own state.
space_dashboard Targeting frames
Direct a link or form submission at a specific named page in the tree using target names — _parent, _top, or a custom frame name.