Binder Brand Book

The flows

I The first recipe. Sign in, paste a recipe into Hearth, read it, scale it for tonight's table, edit a step, save. From the sage cover to a library of one — end to end.
II The page, lived in. The cookbook page is alive. From a single resting view, five things the cook does to it — scaling tonight's portions, editing a step, writing in the margin, leaving a comment beside an ingredient, switching cups for grams. Each is its own sub-flow off the same page.
III A cookbook of your own. From a library of saved recipes to a book made with you — the boutique route, not the template.
IV Photographs. A photograph after dinner. Then another. And a book that knew what to do — adding photos to a recipe, and watching the layout quietly recompose around them.
V Friends. A library stays private. A collection is what travels. From a quiet invitation in the foot to a friend's curated shelf — and a recipe with someone else's ink in the margin. (Exploratory: this flow sits beyond V1 scope; it visualizes the social-layer brainstorm so the brand voice can be tested against the idea before any of it is committed.)
— Spec · Preferences · units. Spec mock for the Preferences UI of the structured unit system in _plans/unit-system.md. The Recipe · detail typography (muted alt column, peek toggle, method tags) now ships in the production IngredientsList — see any Recipe · detail screen in the flows above for the live treatment. Only the Preferences chip + locale picker remains as a separate spec, pending §12 step 9.

VI · Library · one recipe

A library of one.

The emotional payoff. A library of one. Same header, same folio.

9:41

HEARTH

1 recipe

Summer Corn & Basil Ragù

table.kitchen