About Chocolate Recipes Box

It started with a batch of chocolate that seized up

It was a Tuesday in October, and I’d just tempered a kilo of dark chocolate for a ganache. The first pour into the cream looked perfect—smooth, glossy, the kind of sheen that promised silkiness. But when I tried to fold it in, the mixture thickened instantly, then locked solid.

The bowl felt warm to the touch, and the chocolate had turned from liquid gold to a dull, grainy paste. The thermometer read 32°C, right where it should have been, but something had gone wrong in the seconds between melting and mixing.

I’d done this a dozen times before, but that day, the air in the kitchen was thick with humidity after a morning of baking bread. The chocolate had seized—not burned, not under-tempered, but *stuck*, as if the moisture in the air had crept into the mixture without me noticing.

I scraped it out of the bowl and started over, but the second batch did the same thing. By the third attempt, I’d ruined half a block of chocolate and had a bowl full of useless sludge.

The recipe itself wasn’t the problem. It was the conditions. The kitchen, the tools, even the way I’d measured the cream—none of it accounted for what had just happened. And yet, every guide I’d read said tempering was about precision, not guesswork. So why had mine failed?

Nine tries before it worked

I spent the next three days trying to isolate what had gone wrong. The first five batches all seized, no matter how carefully I worked. I adjusted the temperature of the water bath by half a degree, but the chocolate still grainated.

Then I realised the issue wasn’t the heat—it was the humidity. I moved the bowl to the counter, far from the bread dough, and let the mixture sit for ten minutes before folding. Still no luck.

On the sixth try, I added a pinch of salt to the cream, thinking it might draw out moisture. The chocolate seized *harder*.

By the seventh attempt, I’d given up on theory and started tracking everything. I wrote down the exact time the chocolate hit 45°C, the temperature of the room, even the brand of the mixing spoon.

That’s when I noticed the bowl itself—it was ceramic, porous, and had absorbed moisture from the previous night’s risotto. I switched to stainless steel, and for the first time, the ganache came together without a hitch. But the texture was still off.

The chocolate had a waxy finish, not the velvety one I wanted.

The final fix came on the ninth try. I’d read somewhere that a splash of cold water could reset seized chocolate, so I added a teaspoon to the mixture while it was still warm. The ganache smoothed out instantly, and the texture was perfect—rich, glossy, and stable.

But the real lesson wasn’t the fix. It was that I’d never have known any of this if I’d stopped after the first failure. Or the second. Or even the fifth.

The mind behind these pages

That was me, Delia Faulkner, the one who kept trying. I’m the founder and editor here, and my job isn’t just to write recipes—it’s to make sure they work when *you* try them. I grew up in a kitchen where meals were made by feel, not by rules.

My mom’s chili relied on a spice blend she measured by taste, and my dad’s perfect grill marks came from years of watching the smoke curl just right. Neither of them had a thermometer or a scale, but their food never failed.

I’ve spent years doing the opposite—measuring, timing, and testing until something works. It’s a habit that drives my family crazy. My sister once told me I was ‘obsessed with failure’ because I’d rather ruin a batch of cookies than skip a step.

My dad, though, was the first to notice it. He’d hand me a recipe and say, ‘If it doesn’t work, try it again—but this time, write down what went wrong.’ That’s how I learned to turn mistakes into lessons.

Outside the kitchen, I’m the kind of person who brings a notebook to the movies to jot down plot holes. I once spent an hour rewriting the ending of a book mid-flight because the author’s logic didn’t add up.

It’s not that I’m picky—I just can’t stand things that don’t make sense. If a recipe promises something but doesn’t deliver, I’ll keep trying until it does.

This site exists because of that batch of seized chocolate. Not because it was a disaster, but because it taught me that the best recipes aren’t the ones that work the first time—they’re the ones that work *every* time, no matter what.

Everything here is written the way that was

Every recipe on this site is tested the same way—that batch of ganache was. We don’t just follow a recipe once and call it done. We make it in different kitchens, with different tools, and in different weather. If the chocolate seizes in a humid room, we write that down.

If the caramel crystallises when the pan isn’t perfectly clean, we note it. The notes don’t always make it into the final recipe, but they shape it. That’s why you’ll never see vague instructions like ‘fold until smooth’—because we’ve already tried it, and we know exactly what ‘smooth’ looks like.

The process starts with a blank page and ends with a recipe that accounts for the things most guides ignore.

That’s why some of our methods seem unusual—a splash of cold water to reset chocolate, a specific type of bowl for tempering, or a reminder to let the kitchen air out after baking bread. These aren’t gimmicks. They’re the lessons learned from the batches that failed.

And if a recipe changes after six months, it’s not because we’re ‘updating’ it—it’s because we’ve found a better way.

The thread that ties everything together is that same batch of chocolate. It’s why we test in real kitchens, not just ideal ones. It’s why we write about the tools we use—and the ones we avoid.

And it’s why every recipe here is built on the same principle: if it doesn’t work nine times, we keep trying until it does.

What that means for you

You’ll find recipes that don’t just tell you *what* to do, but *why* it matters. If a step seems odd—like adding salt to cream or letting chocolate rest before folding—it’s because we’ve tested it, and it works.

You won’t see shortcuts that skip the details, because we know those are the things that turn a good recipe into a disaster. And if something goes wrong, you’ll have the notes to fix it.

What you won’t find here are perfect results guaranteed. Cooking is about adapting, not following rules. But you *will* find recipes that account for the things most guides leave out—the humidity in your kitchen, the quirks of your tools, and the way heat behaves differently in summer than in winter.

That’s the difference between a recipe and a lesson.