Routes and pages
Map static, dynamic, optional, and catch-all URL patterns to page definitions.
Builder guide
Application Builder
Assemble published Modules into pages, templates, routes, and deployable applications.
Updated August 18, 2026 · 6 of 13
What does the Application Builder own?
It owns route and page definitions, shared templates, Module instances, environment configuration, authentication, SEO defaults, public runtime data, styles, translations, preview, and deployment settings.
Layout templates
Use reusable template regions or a published layout-template Module with a stable content slot.
Instance bindings
Bind Module inputs to route, params, query, auth, theme, config, environment, global data, or server data.
Environments
Keep environment-specific variables, global data, and styles together while preventing secrets from reaching the browser.
- 1
Create the route
Choose its path, page, template, query allowlist, protection, and route SEO.
- 2
Compose the page
Add published Module instances and configure their layout and input bindings.
- 3
Connect behavior
Route Module outputs to page state or to a public command on a specific Module instance.
- 4
Preview the matrix
Test each path, environment, theme, query shape, and authentication state before publishing.