Skip to content

docs: add manifesto flavortext to new recipes #220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
catgoose merged 1 commit into from
Apr 11, 2026
Merged

docs: add manifesto flavortext to new recipes #220

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions RECIPES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1952,6 +1952,10 @@ server-side throttling.

## 29. Interaction insulation for hot-region commands

> _Hypertext is the simultaneous presentation of information and controls such that the information BECOMES THE AFFORDANCE through which choices are obtained and actions are selected._
>
> — The Wisdom of the Uniform Interface

When the DOM inside an SSE-swapped region is replaced faster than the user can
click, node-bound handlers (`hx-post`, `onclick`) break because the target node
is gone before the browser dispatches the event. Delegated commands solve this
Expand Down Expand Up @@ -2041,6 +2045,10 @@ mux.HandleFunc("POST /tasks/complete", completeTask(broker, db))

## 30. Consuming structured control events in app code

> _A media type is a COVENANT. A sacred compact. It says: "if you receive this, here is how you shall process it." It defines the processing model, the structure, the controls, the semantics._
>
> — The Wisdom of the Uniform Interface

Tavern's control events carry structured JSON payloads. While
[tavern-js](https://github.com/catgoose/tavern-js) handles common UX
patterns declaratively, your app code can listen for the same DOM events
Expand Down Expand Up @@ -2133,6 +2141,16 @@ es.addEventListener("tavern-topics-changed", (e) => {

## 31. App-shell with lifeline and scoped streams

> _Master say: "but how does the client know when state changes?"_
>
> _Grug say: "server tell it."_
>
> _Master say: "but--"_
>
> _Grug say: "server. tell. it."_
>
> — The Recorded Sayings of Layman Grug, [The Dothog Manifesto](https://github.com/catgoose/dothog/blob/main/MANIFESTO.md)

> **Contract reference:** See [docs/stream-contract.md](docs/stream-contract.md)
> for the full stream contract and decision guidance table.

Expand Down Expand Up @@ -2319,6 +2337,10 @@ function closePanel(panel) {

## 32. Stale/degraded/live region handling

> _When what is possible changes, the representation changes, and the client adapts, because the client was never hardcoded to anything except "follow the links."_
>
> — The Wisdom of the Uniform Interface

The full lifecycle of a Tavern-connected region, from initial connection
through disconnection, recovery, and potential staleness. This recipe shows
how to wire up visual indicators and programmatic hooks for every state.
Expand Down
Loading