Why it exists
The template builder provides authors with a route-centric editing interface where they can inspect the exact blocks used by a page and work with dynamic bindings without dropping into lower-level data views.
Use this when
- visually editing a page layout
- switching among parameter bindings for a dynamic route
- loading a route's current block set in one place
- avoiding block-sharing mistakes across parameter combinations
What it includes
- route-aware builder entry point
- dynamic binding selection
- batched block loading
- static and parametric route handling
- template builder, skeleton, and client UI
Core workflow
- Open the builder for a route.
- Determine whether the route is static or parametric.
- For parametric routes, load available bindings.
- Load the block IDs for the active binding or static route.
- Render the builder client with route, blocks, and binding context.
System surfaces
- route, binding, and block server loaders
