Explanation
Why Stario is shaped the way it is: mental models, architecture patterns, and boundaries—not step-by-step tasks.
For hands-on paths, see Tutorials and How-tos. For API contracts, see Reference.
Essays
The Stario way — MPA-first hypermedia, backend truth, thin client, when realtime earns its keep.
Handlers, context, and the writer — the per-request path through
ContextandWriter,c.alive, and the 204-then-continue pattern.The go-to architecture — CQRS-shaped HTTP, SSE subscribe loop, Datastar,
UrlPath, andRelay.Telemetry design — spans, attributes, events,
span.stepat bootstrap, and tracers as part of app structure.No validation layer in the framework — where validation belongs (especially Datastar signals).
Start here by goal
| Goal | Read |
|---|---|
| First runnable app | Hello world → Getting started (Tiles) |
| Live UI with SSE | Getting started → The go-to architecture |
| v4 routes and assets | Routing (UrlPath, StaticAssets.register) |
| v4 Datastar imports | Datastar (data, at, SSE, read_signals) |