Public renderer
Understand the /s/<ws>/<site>/... renderer.
The public renderer turns a Mini Agency document into HTML for visitors. It is used for staging routes, published customer sites, and custom domains.
Route model
The app domain serves staging under a site-scoped route:
/s/<workspace-slug>/<site-slug>
/s/<workspace-slug>/<site-slug>/<page-slug>Staging renders the live editor document. Production renders the published version, usually through a custom domain or the configured production route.
Access modes
Staging supports access modes:
- Workspace-only: signed-in workspace members can view.
- Password: visitors enter a staging password and receive a time-limited cookie.
- Public: anyone can view, but the page is marked noindex.
Production should be public unless a separate access layer is configured outside Mini Agency.
Dynamic routes
Collection single-item pages resolve the item from the route. A listing page can link to item URLs through {{@url}}. The renderer injects the current item so fields such as {{title}}, {{coverImage}}, and {{body}} resolve to the right values.
Cache and invalidation
Staging uses no-store behavior because it reflects live editor state. Production publishing creates the durable visitor-facing version. If production looks stale, confirm the site was published after the latest edit and that you are not looking at a cached browser tab.