# Returns Gallery

URL: /chirp/docs/examples/returns-gallery/
Section: examples
Tags: examples, return-values, fragments, streaming

--------------------------------------------------------------------------------

What It Teaches Use this example when you are deciding which return type to use. It puts every major Chirp response shape on one page, with routes that demonstrate when each type is appropriate. Route Return type Use when GET / Template Full-page render with no htmx negotiation GET /fragment Fragment A named block is always the response GET /page Page Browser requests need a full page; htmx requests need a block POST /oob OOB One action updates multiple targets GET /stream Stream A response can flush sections as they complete GET /suspense Suspense Initial render needs a shell first, then deferred blocks GET /events EventStream Post-load updates should arrive over SSE POST /validate ValidationError Invalid form data should re-render a 422 fragment POST /mutate MutationResult One mutation supports multiple UX flows GET /redirect Redirect The browser should navigate elsewhere Run It PYTHONPATH=src python examples/standalone/returns_gallery/app.py Open http://127.0.0.1:8000/ and click through the cards. Contract Surface The example is useful for contract work because it deliberately exercises the HTML surfaces Chirp protects: fragment block names, OOB targets, deferred Suspense blocks, SSE fragment payloads, and validation fragments. Run: PYTHONPATH=src chirp check examples.standalone.returns_gallery.app:app pytest examples/standalone/returns_gallery/ Source app.py gallery.html README.md Next Return Values Fragment Blocks Streaming

--------------------------------------------------------------------------------

Metadata:
- Word Count: 201
- Reading Time: 1 minutes