Clueless Cooks
A personal recipe blog with a chip on its shoulder — and a case study in treating dinner like documentation. The payoff says it all: if it’s listed, it’s tasted.
Taste the blog
One blog, three names — all of them rude about my cooking
IT
Ricette per Pippe
Affectionate Italian slang for people who are hopeless at the stove.
EN
Clueless Cooks
The English version that politely admits we have no idea what we’re doing.
FR
Recettes pour quiches
In French, une quiche is both a tart and a hopeless beginner. Couldn’t resist.
Right now the three languages are really just for friends — I have Italian-, French- and English-speaking ones, and it was nice to drop them the blog whenever a recipe came up in conversation. But the same joke landing in every language is also exactly the consistency a brand needs later: the voice is already locked.
Two universes of analysis
Same blog, two ways to read it. Pick your lens. ↓
The user persona was, embarrassingly, me
Every design decision here traces back to a real moment of me standing in my kitchen, defeated.
The crème caramel incident
Halfway through an online recipe, I found out — hidden in the final notes — that I needed a specific little pan I didn’t own. I’d already started. So there I was: caramel setting, dignity melting, and seven hours of failures later.
The endless scroll
I hated scrolling back up to the ingredients at every single step — then scrolling down and completely losing which step I was on. Hands dirty, place lost, soup over-salted.
Me, and everyone like me
The reader I write for is twenty-something and up, mostly a woman (but not only), with no idea what to do in a kitchen and often a little intimidated by it. No expertise, and not much confidence either. So the voice is cheerful and self-ironic, and the information underneath is built to guide and reassure.
So I did the only reasonable thing: I treated the recipe like a piece of technical documentation. Because a recipe is the oldest form of technical writing there is — a sequence of steps, with prerequisites, that has to produce the same result in anyone’s kitchen.
The goal: a recipe you can follow with a free mind and calm nerves
Enemy #1 · Mental load
What do I need? How much? Where was I? Everything the page can remember, you shouldn’t have to.
Enemy #2 · Performance anxiety
Am I doing it wrong? Is it ruined? Every step tells you what good looks like, and what to do if it doesn’t.
Nine years of technical communication, pointed squarely at dinner.
Designed to lighten the load, and the nerves
Every decision follows the cook’s journey, from the supermarket to the next recipe, and takes on one of the two enemies.
Before you shop
What to buy, and where
The supermarket can be intimidating too, especially the first time you go looking for plant-based products and don’t know what they’re called or which shelf they’re on. So the ingredient list tells you what I actually buy, down to the store and the brand: one less decision before you’ve even started.
Soy strips: 180g (6.3 oz), ready to cook (I use the ones from Eurospin or Garden Gourmet Sensational)
Before you start
Everything you need, up front
A Quick Info box up top — servings, prep, cook, and tools — so the special pan never ambushes you on step seven. No prerequisite hides in the footnotes.
No “to taste” or “as needed”
Both only help if you already know what the dish should taste or look like. Every ingredient gets a real amount, so nothing is left to a judgment you haven’t built yet.
While you cook
Amounts inside every step
Each step repeats the quantity it needs, so you never scroll back up to the ingredient list and lose your place: one less thing to hold in your head while your hands are busy.
A live, tap-to-check list
Every step has a “Done” check. One messy-thumbed tap marks it, so you never lose your place again. Your memory doesn’t have to track where you are, the page does: a checklist that survives interruptions.
Prescriptive on purpose
When it matters, a step says it: the flame level, how to handle an ingredient, what it should look like. Bossy for an expert, a lifeline for a beginner.
Stir well to coat them in the oil and keep tossing with a spatula — at this heat they can burn easily.
Reassurance, written in
The microcopy lowers the stakes. Where precision doesn’t matter, the recipe says so. Where something can go wrong, it says what to do next, so a mistake is a detour, not a disaster.
Carrots: about 100g (no need to be precise) … If they darken too fast, lower the heat slightly.
Finding the next one
Know where you are
Category pills sit at the top of every recipe, the active one filled in. Arrive from Google, see exactly where you landed, and step sideways into similar recipes without going back.
Localized for cultures, not just languages
Translating the words isn’t enough: what counts as obvious, and how a meal is organized, changes from one kitchen culture to the next. So the recipes and the site structure adapt too.
Cooking the pasta
To an Italian reader, “boil the water, salt it, drop the pasta” is noise: everyone knows it. For English and French readers it’s a natural part of the recipe, and leaving it out would make it feel incomplete. So the EN and FR versions spell it out.
Courses, the local way
Each culture organizes a meal its own way, and the categories follow. The Italian primi piatti becomes Pasta dishes in English, because “first course” doesn’t carry the pasta-based meaning primi has in Italian.
Grams and ounces
Italian and French cooks measure in grams, but many English-speaking ones, especially in the US, think in ounces. So every amount in the English version carries both, like 120g (4.2 oz): no calculator, no guessing.
A brand that doesn’t take itself seriously
The joke in the name sets the tone, so nobody feels judged. The type carries it through, and keeps the recipe easy to follow.
Type, and why
Three roles, three voices: a face that signs the brand, a face you actually read, and a face that disappears. The personality lives in the headings — everything else gets progressively quieter so the recipe stays legible.
--font-heading
Clueless Cooks
Pacifico
Playful, handmade, a personal signature — the right tone for a recipe blog that refuses to take itself seriously.
--font-body
If it’s listed, it’s tasted.
Fraunces
Warmth and an editorial feel — a soft modern serif, more characterful than a classic one but still easy to read through long steps.
--font-small
PREP 10’ · COOK 20’ · SERVES 2
Helvetica Neue
Neutral and clean for labels, timings and technical details — it steps back so the character stays in the headings and body.
The bones are in — the polish isn’t, yet
Live, but a work in progress
The blog is up and the automations are wired end-to-end — but the structure and pipelines are scaffolded, not finished. The design is where I keep iterating, and I’ve got a running list of things to push further.
The known limit: one domain, three languages
All three sites live under ricetteperpippe.com, so the English and French pages carry an Italian domain and Italian URLs (/en/chi-sono/). Doing it properly means buying a dedicated domain per language. For now the project stays Italian-first, but I keep investing in the translations, so the English and French sites are ready the day the domains are.
From personal blog to actual brand
Right now it’s just my blog, shared with friends. But if it takes off, the brand is ready to step out on its own: I’ve planned redirects onto dedicated domains — likely recettespourquiches.fr and cluelesscooksrecipes.com — alongside automated content pipelines that draft recipes in the house tone and post them across socials, turning clueless cooks into a community. To run it more professionally, two things come first: AI-generated videos built from my real dish photos, and navigation counters to measure what people actually read, the groundwork for a future growth-marketing step.
Get in touch
Let’s talk.
Got a project, a role, or just want to swap kitty pictures and plant-based recipes? I’d love to hear from you.