Article

Why good recipes need a home (and when they don't)

A recipe scattered across a caption, three comments and a video isn't quite a recipe yet. On giving your best dishes one complete page, and when a group chat will do.

By Crumb EditorsUpdated 4 min read

Somewhere, someone is thinking about your beans.

They saw them months ago: white beans, lemon, a shallow pan, something crisp on top. They meant to make them. Now it's a rainy Tuesday, the beans are in the cupboard, and they can't remember what you called the dish, when you posted it, or where the instructions went. So they make something else.

That small, quiet loss happens all the time, and it's the best argument there is for giving good recipes a home.

A recipe is a letter to someone you can't see

When you cook, you know everything. You know the beans go in drained, that the pan is the old 8 × 12 one, that "until golden" means a good 30 minutes. A recipe is your attempt to hand all of that to someone who isn't in the room.

Social media is a wonderful place to show food. It's a harder place to hand over a recipe. The quantities sit in the caption, the correction sits in a reply to a comment, and the one step that matters (leave the lid off so the sauce reduces) only exists in second 14 of the video. Each piece is there. The cook just has to assemble them, and most won't.

So when someone asks "recipe please?", sending them the post only solves half the problem. They've found the dish. They still have to rebuild the recipe.

What a home actually is

It isn't a fancy website. It's three plain things:

  • One complete page per dish, with every ingredient, amount, step and cue in one place, so nobody has to dig through comments.
  • An address that keeps working, so the link someone saved in March still opens in November.
  • A way back for the reader who only remembers "beans, lemon, dinner."

That last one is easy to underrate. Smitten Kitchen's recipe index is a lovely example: you can browse by ingredient (Beans), by meal (Dinner), by season (Summer) or by mood (Weeknight Favorite). Nobody has to remember a title or a date. They start from what they remember about the food.

A collection can also be built around a need. Courtney Gordon's "WTF to Feed Your Kids After School" series, which she talks about in our interview with her, gives a tired parent a reason to come looking even when they can't name a single dish.

When you don't need one

Say you share a dozen recipes with friends in a group chat or a shared folder. Everyone knows where they are, the files open, and nobody has ever texted you to ask what happens between steps three and four.

Keep doing that. A website wouldn't fix anything, because nothing's broken. Plenty of good cooks share wonderful recipes for years without one, and that's a perfectly good way to cook for people.

There's a middle ground, too. If your recipes are already complete but hard to find, a simple list of links might be all they need. Fix the signpost before you rebuild the house.

The upkeep is real, and smaller than you think

A recipe home asks for a little ongoing care. When someone points out that the beans need more salt, you fix the page, and everyone who opens it from then on gets the better version. That's a big improvement on a correction buried under 200 comments. Links need to keep working. Categories need a tidy now and then.

It doesn't need a posting schedule. Keeping one older recipe useful is worth more than publishing a new one nobody can find.

It's also worth keeping your own copies of your recipes and photos, wherever you publish. Owning your content and being able to pick it up and move it are different things, and every platform handles exports differently. Check what you can take with you before your collection gets big.

Try the reader's route

Here's a small experiment. Pick a recipe of yours from six months ago, one people liked. Now try to cook it the way a reader would: no dashboard, no memory of where you put the correction, just whatever's public.

Can you find it? Can you follow it all the way through?

If you can, lovely. Your recipes are already at home. If you get stuck, the place you got stuck tells you what to fix: the instructions, the route to them, or where they live. When it's the last one, our guide on how to create a recipe website is a good place to start.

publishingrecipe archivessocial media
← Back to the blog