Projects
Recipes add one feature to an app you have. These are the other end: a whole backend, built in order, including the parts that are genuinely hard rather than the CRUD around them.
| Project | The hard part | Uses |
|---|---|---|
| Chat | cursor pagination, and a socket that checks membership before it opens | Drizzle, WebSockets, auth |
| Trello | ordering cards under drag-and-drop without rewriting the list | Drizzle, transactions, policies |
| YouTube | an upload pipeline, and a feed that stays fast | storage, queue, Drizzle, auth |
What makes these different from a tutorial
Section titled “What makes these different from a tutorial”Each one has a section on the thing that is actually difficult, and each is honest about where the design stops working. The Trello chapter measures how many drags it takes before floating-point positions collapse — 42 — and then fixes it. The chat chapter explains why offset pagination breaks on a feed that people are writing to. The YouTube chapter has a video that is uploaded but not yet watchable, because that state is real and pretending it is not produces a broken player.
What they share
Section titled “What they share”All three assume the SQLite default and say what changes for Postgres. All three use
auth-basic — the Google sign-in
recipe drops straight in if you want it.
Every schema and every query on these pages was executed before it was written. Where a page quotes a result, that is the real output.
Where to start
Section titled “Where to start”New to Oven, start with the tutorial — these assume you know what a route file and a brick are.
Otherwise pick by what you want to learn: chat for real-time and pagination, Trello for permissions and ordering, YouTube for background work and file handling.