HTML over the wire: one template, many modes. Chirp renders a single template with named blocks as a full page, an htmx fragment, a multi-target OOB swap, or a streamed [Suspense or SSE payload] — the return type decides which. A fragment is one of those named blocks rendered on its own; an OOB swap updates several regions of the page from a single response. This section is for the hypermedia practitioner who wants those return-type mechanics in detail.
Return a full HTML page from a template with the Template return type
Render a single named template block on its own, so htmx can swap just the piece of the DOM it asked for.
When to use{% block %} vs {% fragment %}— the directive for blocks that render only as swap targets
How Chirp reads a template's structure from Kida to discover OOB regions, validate blocks, and build layout contracts
Compose Chirp pages from Kida template constructs — extends, block, include, and call
Register custom template filters and globals, and use Chirp's web-specific built-ins