What cookbook readers expect
Home cooks expect recipes that work with supermarket ingredients and normal equipment, a consistent format they can follow with floury hands, and headnotes that tell them why a dish is worth making and what it goes with. They also buy cookbooks for the person behind them: the family stories, the regional knowledge, the voice.
Recipes have to be tested. A language model can write a recipe that reads perfectly and fails: wrong ratios, missing steps, oven times that are off. Cook every recipe before publishing, and check allergens and dietary claims yourself.
Length and structure
Cookbooks are measured in recipes more than words. A family cookbook might hold anywhere from a few dozen to over a hundred recipes. With three to six recipes per chapter, a 12-chapter book holds roughly 36 to 72; set the chapter count to the number of themed sections you want.
Common organisations are by meal (breakfasts, weeknight dinners, weekend cooking, sweets), by main ingredient or by season. An introduction about your kitchen and a pantry chapter help readers trust the rest.
How Inkora writes a cookbook
Every recipe follows one template: the recipe name, a two-to-three-sentence headnote, a line with servings, prep time and cook time, an ingredients list with quantities, a numbered method and an optional tip. Because the format is fixed, the print interior and the ebook lay out every recipe the same way.
Planning turns your brief into themed chapters, each listing three to six recipes with a short note, and checks that no dish appears twice. Edit the list before writing to add family recipes; describe them in the chapter plan and put exact quantities in the brief. Interiors are text only, so food photos need to be added afterwards in the DOCX.
What to put in your brief
The brief is the “Your book idea & instructions” box in the new-book wizard. The more specific it is, the less generic the book. Here is an example, with the settings that go with it:
Home cooking cookbook: the recipes my Filipino-American family actually cooks in Chicago, adapted to US supermarkets. Chapters by occasion: weeknight rice bowls, Sunday cooking, food for a crowd, snacks (merienda), sweets, and a pantry chapter. Family recipes to include: my mother's chicken adobo (soy, cane vinegar, garlic, bay, black peppercorns, braised then pan-crisped), lumpia for parties, and my grandmother's ube halaya. Use US cups and ounces with grams in brackets. Headnotes warm, short, with family memories I'll edit in. Flag any ingredient that's a common allergen. I will test every recipe.
Other wizard settings
- Genre
- Home Cooking
- Audience
- Home cooks in the US
- Tone
- Warm & conversational
- Length
- Standard (30,000 words), 10 chapters
Example outline: Rice at Every Table: A Filipino-American Kitchen
A brief like the one above gives a plan along these lines. You can rename, reorder, add or delete chapters before any writing starts.
- 1
Our Pantry
Soy, cane vinegar, fish sauce, bagoong and where to find them in a US supermarket.
- 2
Rice, Every Way
Steamed rice, garlic fried rice and leftover-rice breakfasts.
- 3
Weeknight Bowls
Fast dinners over rice, starting with Mom's adobo.
- 4
Soups for Cold Nights
Sinigang, tinola and a quick chicken arroz caldo.
- 5
Sunday Cooking
Slow braises and the dishes worth the afternoon.
- 6
Food for a Crowd
Party lumpia, pancit and trays for family gatherings.
- 7
Grill and Barbecue
Skewers, marinades and backyard cooking.
- 8
Merienda
Afternoon snacks from turon to cheese ensaymada.
- 9
Sweets
Leche flan, Lola's ube halaya and other desserts.
- 10
Sauces and Dips
Vinegar dips, atchara and the condiments on our table.
Common mistakes
- Publishing recipes you haven't cooked.
- Mixing measurement systems without saying which is primary.
- Headnotes that only describe the recipe instead of telling readers why it matters.
- Missing allergen warnings or unchecked dietary claims (vegan, gluten-free).
- Chapters of uneven size: one with two recipes, one with twelve.