# A family cookbook — the recipe box, the stories behind it and an index of the family who cooked it Recipe No. 23, Kitchen and table. From The know.sh Cookbook: https://know.sh/cookbook/family-cookbook - For: a family gathering three generations of recipes before the cards fade - You bring: a recipe box or a drawer of cards, phone photos of the hard-to-read ones, and relatives willing to tell you what the cards leave out - You get: a cookbook of forty-odd recipes in five chapters, each recipe with its story, an index of the cooks and places behind them, and links the family can read - Time: an afternoon to set up, then a recipe or two an evening - Keep it: private while you work; share one document by a read-only link Every family has a recipe box that only one person can read. The cards say "a coffee cup of flour" and "bake till done", the best ones have no card at all, and the stories that made them matter — whose wedding, which winter — live in the heads of people who will not always be here to ask. This recipe turns the box into a cookbook. You photograph the cards and hand them to the assistant you already use, Claude, ChatGPT or another you connect to know.sh, and it files the whole box in an evening: each chapter a research document, each recipe a numbered finding with the same four parts: the story, the ingredients, the method, and what the card does not say. Then you sit down with the cards and correct it in the editor. know.sh builds an index at the back from the names that recur, so Rose, Walt and Aunt Jo each lead to the recipes they made, and **Look up** finds every recipe with buttermilk in it. When a chapter is ready, a read-only link lets the whole family read it on a phone at the stove. The card itself stays in the box and its photo in your camera roll. The cookbook holds the words, the family's corrections, and the answers you collected while there was still someone to ask. ## What you will use - **Shelf**: One shelf for the whole cookbook, say *The Halloran kitchen*, with a line on whose recipes these are. - **Research document**: One document per chapter: Breakfasts, Weeknights, Sundays, Holidays, Baking. The overview introduces the chapter. - **Finding**: One finding per recipe, filed as an *Observation*; the family essentials marked **Key**; recipes you know exist but have not found filed as a *Question*. - **Your AI assistant**: Claude, ChatGPT or another assistant you connect reads your photos of the cards, files each one as a recipe in the right chapter, and lists what the cards leave out. - **The editor**: Where you check every transcription against its card, fix what the assistant misread, and add what only the family knows. - **Margin notes**: Where relatives disagree: “Aunt Jo says lard, not butter.” The note sits beside the line it is about. - **The A–Z index**: The index of cooks, places and family names, built from the names that recur in your recipe titles and first lines. - **Public link**: A read-only link per chapter, with a password if you would rather keep it in the family. ## Method ### 1. Make the shelf and the chapters Make a shelf called *The Halloran kitchen* (use your own family's name) and say in a line what it is for: "Recipes from Nana Rose's box, and the people who cooked them." Decide the chapters before anything is filed. Five is a good number to start with: Breakfasts, Weeknights, Sundays, Holidays, Baking. You can always move a recipe later. Each chapter will be a document, and its overview is yours to write, in the family's voice. "Sundays were for the long oven: the pot roast went in before church and came out when we got home." These overviews are what a reader meets first, and they are where the index finds the names of people and places. ### 2. Photograph the box and hand it to your assistant Photograph every card, front and back, in good light, a chapter's worth at a time. Give the photos to the assistant you already use, in Claude or ChatGPT, with know.sh connected, and ask it to make a document per chapter on your shelf and a finding per card. Forty cards become forty recipes in one sitting instead of four evenings of squinting. Tell it to transcribe exactly what the card says before interpreting anything. "Oleo", "a slow oven" and "a lump of butter the size of an egg" are part of the record; the conversions come later, underneath. Where it cannot read a word, it should write *[unclear]* rather than guess. ### 3. Give every recipe the same four parts A cookbook is easier to read when every page has the same shape. Under each recipe's title, write: - **The story**: who made it, when, and why it mattered. Two or three sentences is plenty. - **Ingredients**, as a list. - **Method**, as numbered steps. - **What the card does not say**: the pan size, the oven temperature, the trick everyone knew. Ask your assistant for that shape on every finding, then open each one with **Edit** beside its photo. Fix the misreadings, fill the *[unclear]* gaps and write the story yourself; that part is the family's, not the assistant's. Title each recipe by its dish, "Buttermilk biscuits", not "Nana's favourite", and name the cook early in the story's first line: "Made by Nana Rose every Sunday from 1961." The index picks up names that recur in titles and first lines, so a recipe that names its cook at the top is filed under that cook. ### 4. Ask your assistant what the cards leave out Ask your assistant to read a chapter, naming it, for measurements that are not standard and steps that are missing. Ask it to put its list in a new finding rather than change the recipes: you want a checklist of questions, not a rewritten card. Take that list to the people who know. Relatives cannot write in your library, so this part happens on the phone, at the kitchen table or by email, and you file what you learn. Put the answer in the recipe itself, and where two people remember it differently, keep both: select the line and leave a **Note** — "Aunt Jo says lard, not butter; Uncle Pete says it was always butter by 1975." ### 5. Standardise without erasing Once the family has answered, add modern measurements *under* the originals rather than replacing them: "a coffee cup of flour (about 1 cup, 125 g)". Your assistant can draft these conversions for a whole chapter; check each one against a kitchen scale or a reliable conversion table, because an old coffee cup is not a measuring cup and the assistant can be wrong. Revisions show every line it changed. Add a last line to every recipe listing its allergens, and for meat and poultry, the safe internal temperature. The note at the end of this recipe lists both. ### 6. Let the index do its work Open the index and read it like a stranger would. The family should be there — *Rose*, *Walt*, *Jo*, *Pete* — with the places that mattered, like *Woolworth's*, each followed by the numbers of their recipes. If a cook is missing, their name is not near the top of any recipe yet. Ingredients are everyday words, and the index leaves those out; for them, press ⌘K and type *pecans*, and Look up finds every recipe that uses them. Mark the recipes the family cannot do without as **Key**, and highlight the lines people always get wrong. Highlighted recipes show their numbers in bold in the index, beside the cook who made them. ### 7. Publish a chapter at a time When a chapter reads well, press **Share** and make a public link. It is read-only and shows the overview and every recipe, without your notes or highlights. Copy it the moment it appears; know.sh shows the full link only once. Add a password if you would rather it stayed in the family. Links are made one document at a time, so a five-chapter cookbook is five links. Make a sixth document called *Read me first* with a paragraph of welcome and the five links, share that one, and send it to the family group chat. If a recipe includes a living relative's private story, leave that finding out of the link from its own page. ## Prompts to try Your assistant, connected to know.sh (Claude, ChatGPT or a local model): > I am giving you photos of recipe cards for the Sundays chapter. Using know.sh, on my shelf The Halloran kitchen, create a document called “Sundays” if it is not there, and add one finding per card, filed as an Observation, with four parts: The story (leave it blank for me), Ingredients, Method, and What the card does not say. Transcribe the card exactly, write [unclear] where you cannot read it, and do not convert any measurement. Your assistant, connected to know.sh (Claude, ChatGPT or a local model): > Using know.sh, read the document Sundays on my shelf The Halloran kitchen. List every measurement or instruction that is not standard today (a coffee cup, oleo, a slow oven, bake till done), what it most likely meant, and how sure you are. Do not change the recipes; put the list in a new finding called “Measurements to check with the family”. Your assistant, connected to know.sh (Claude, ChatGPT or a local model): > Using know.sh, go through every finding in the document Baking on my shelf The Halloran kitchen and add a last line to each recipe: “Allergens:” followed by which of the nine major US allergens it contains (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soy, sesame). If you are not sure, write the allergen with a question mark instead of guessing. ## Variations - Cooking for a whole congregation or school instead of one family? The [fundraiser cookbook](/cookbook/fundraiser-cookbook) collects recipes from dozens of cooks and gets them ready for a printer. - Make a single document, *The Christmas table*, and share it each December with an expiry date in January, so the link stops working once the tins are empty. - Give a wedding gift: a new shelf with the family recipes the couple will actually cook, and a *Read me first* written by the grandparents. - Pair it with the [family history](/cookbook/family-history): link each recipe to the person it came from, and the cookbook becomes a way into the family tree. ## Where it falls short - know.sh holds the words, not the cards. The photos go to your assistant, not into the library, so keep them in your photo library or a shared album, and mention in each recipe where the card is. - There is no printed or PDF edition. If the family wants a bound book, copy the text into a layout tool or a printer’s template when it is finished; the library remains the version you keep correcting. - Relatives read; they do not write. Public links are read-only, so stories and corrections come to you by phone or email, and you file them. - Links are one document each, so a cookbook in five chapters means five links, or a *Read me first* document that lists them. - Transcribing handwriting needs an assistant that can read images, as Claude and ChatGPT can; many local models cannot. Whichever you use, check every recipe against its card, since a misread 1 for a 7 changes a cake. ## A note on allergens, safety and other people’s recipes List the major allergens on every recipe: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame. Never describe a family recipe as free of an allergen; home kitchens share bowls and surfaces. Cook poultry to 165°F (74°C) and ground meat to 160°F (71°C), and check with a thermometer rather than a card that says "till done". For canning, pickling or preserving, use only tested recipes from the USDA or the National Center for Home Food Preservation, even when Grandma's card says otherwise. Some recipes in any family box were clipped from magazines and cookbooks. A list of ingredients is not protected by copyright, but the wording of a headnote or method can be: rewrite those in your own words and name the source, or keep them out of the public link. Indexed under: Family recipes, Recipe cards, Allergens, Measurements, old, Food safety, Headnotes, Oral history.