Sfdwhf

I'm a chef. I'm also a writer. It's inevitable that I would want to write a cookbook. In fact I've probably started a dozen that I just never got around to finishing. Partly because I'm not sure how to.

Before I even get to my question I think it important to distinguish between two types of cookbooks. One is sorta a how to cook tutorial with a few recipes sprinkled in. There other is a reference book. It's mostly recipes with very little superfluous writing. I want to write the second.

And that's the problem. There's very little room for any creative flair. Surely, I can inject a little personality into it, but I'm not sure when the best way to do it is.

During the introduction that most people won't read and those that do read once? During the recipes themselves? That seems unlikely to work well. Should I write a description of each dish before each recipes. Will this be to much reading for people who just want to jump straight to the technical details? It's there perhaps something I haven't considered.

Your cookbook's primary function is being a reference book: providing clear recipes. My personal preference is to always have a picture of the final product, and preferably also intermediary stages, especially if the process is complicated. Everything else, every bit of writing creativity, is secondary to the cookbook's primary function.

Now, secondary doesn't mean it has no place at all. That introduction, which you treat with disdain, you can do quite a lot with it. The introduction is in fact the part that should make people want to cook from your book. Not just in the general sense of "I might find a recipe from here useful", but in the immediate way of "I want to make something from here now".

How do you do that? Tell your reader, in the introduction, what your book is all about. It's not just a random selection of recipes, is it? If it's the food of a particular region, tell about that region, about the part that food plays in local culture, about local flavours. If it's all about one particular kind of food (meat, or bread, or whatever) - talk about that. If it's about recipes being easy, talk about how everyone can cook and what a delight it is. Cooking is something you love, and you love this particular selection of recipes, right? Show that.

If there are sections to your book, you can treat the introduction to each section just as you treat the general introduction, only briefer.

And then, there are the recipes. To each, you can add a note about what makes it special for you: "my mother used to make this for special occasions", "my children love helping me with the making of those, as much as with the eating", etc. Add a personal touch, help people see themselves making the thing. Encourage people to make new things - stepping outside one's comfort zone is not easy, make people feel you're right there with them.

Just don't let the creative part overwhelm your cookbook. If I'm being sold more "talk" than actual recipes, I feel I'm being swindled. I bought the book for the recipes, after all - the rest is a bonus.

I recall "Two Meatballs In The Italian Kitchen", by Pino Luongo and Mark Straussman. It was two chefs with different styles of Italian restaurants that got together for a cookbook.

The basic premise is they told a 1/4 to one page personal story or anecdote about a dish. Where they first had it, who taught it to them, a celebrity that eats it every time they come to the restaurant, where it originated or how it became famous or where in Italy it is most popular, something like that. Sometimes its just a fond memory of a trip, or finding an unexpectedly good version in a town where you wouldn't expect it.

Anyway, nearly every recipe has a little story with it, always on the even-numbered page. If the story it short, the recipe and any special instruction starts on the same page with a large-type heading, if there isn't much room, it starts on the facing page.

People interested in just the recipe can skip the human-interest story pretty easily. But you are left some room for creativity. You don't have to follow their formula, exactly, your writing can be additional ideas or flairs with the dish, or what you have seen people do with it, convert it from an entreé into an appetizer, etc.

I think its an approach that gives you the best of both worlds.

Here's a recipe that I use often. It's brief, directly and clearly written, but it still includes some background and history about the recipe, as well as some minimal commentary that allows the writer's personality to come through:

http://cremebrulee.com/creme.htm

What sort of creativity would you like to add?

Yes, most reference-style cookbooks are pretty straightforward: Here are the ingredients, here's how to put them together, cook for this long, etc.

I suppose you could add rambling discussions on your philosophy of life or your difficult childhood, but I suspect most readers would find something like that distracting and annoying.

More seriously, you certainly could add discussion of cooking techniques, helpful hints, etc. Maybe you could think of hopefully-interesting things to say about each dish? I'm not sure what that would be. Lots of cookbooks say things like, "goes well with a red wine" or "people with high cholesterol might want to substitute ..." and that sort of thing, but that doesn't sound all that creative either. ChrisSunami mentioned saying something about the history of the dish. I suppose it might be amusing to read, "this recipe goes back to the 1500s" or "this was served at the first White House dinner with Thomas Jefferson" or that sort of tidbit.

I'm very much an amateur at cooking myself. When I read a recipe, I'm looking for the hard facts: here are the ingredients and here's how to make the dish. If the cookbook writer included a lot of discussion about his life or philosophy of cooking or whatever, I suspect I'd just skim over it. Maybe you could make it interesting enough that people would really want to read it.

Every now and then I see a cookbook that includes rambling philosophical discussions, and my thought is usually, "yeah, whatever, get to the recipe". But maybe I'm not typical or not your target audience.