About Recipes Lantern

It started with one sauce that kept falling apart

It was a summer in Chicago, and I was trying to make a simple tomato sauce for my grandmother’s empanadas. The recipe called for simmering crushed tomatoes with garlic, onion, and a pinch of oregano until it thickened enough to coat the back of a spoon.

The first batch split into two layers—the oil rose to the top like a greasy film, and the tomatoes settled below, watery and weak. I stirred it back together, but the moment I turned off the heat, it separated again.

The second time, I added flour as a thickener, but that just turned it into a gluey paste. The third time, I reduced it too long, and the flavor turned bitter, like overcooked ketchup.

Each attempt left me standing at the stove, tasting and adjusting, only to watch the sauce betray me again. The kitchen smelled like burnt garlic and regret.

That’s when I realised the problem wasn’t the recipe—it was the method. The sauce needed fat to emulsify it, but too much and it lost its brightness. Too little, and it broke.

My grandmother had done this a hundred times without thinking, but I was treating it like a science experiment, measuring and timing like it was a lab, not a kitchen.

Nine tries before it worked

The fourth attempt, I added a splash of olive oil at the end and emulsified it with an immersion blender. The sauce held—but it tasted flat. The fifth time, I used a roux instead of flour, and the sauce thickened beautifully, but the roux burned before the tomatoes were ready.

The sixth time, I added a pinch of sugar to balance the acidity, but the flavor became cloying, like a dessert sauce.

By the ninth try, I’d learned to add the oil gradually, whisking constantly, and to pull the sauce off the heat just before it looked done. The texture was velvety, the flavor bright and balanced. But the real lesson wasn’t just the technique—it was the patience.

Every failure had taught me something, even the ones that made things worse.

That sauce became the first one I ever wrote down with exact measurements, a timeline, and a note: *‘Emulsify at the end or it breaks.’* It wasn’t just a recipe anymore.

It was a lesson in trust—trusting the process, trusting the instinct, and trusting that even the failures were part of the story.

The mind behind these pages

That stubborn sauce was the first thing I ever made that *stayed* made. It’s also why I’m here now. My name is Vivian Ellsworth, and I’m the founder of *Recipes Lantern*.

My first kitchen was my grandmother’s tiny apartment in Chicago, where the stove was always on and the air smelled like garlic and cinnamon.

She’d let me stand on a stool, stirring pots of soup or rolling out dough for empanadas, and I learned that cooking isn’t about following rules—it’s about trusting your instincts.

I’m the kind of person who tries something nine times before giving up. It’s why I burned my first sourdough starter, why I over-salted every batch of cookies for a year, and why I still keep a notebook by the stove to jot down what went wrong.

My grandmother used to say I had ‘the patience of a saint and the stubbornness of a mule.’ It’s the same trait that makes me rewrite a recipe until it’s right, even when I know it should work.

Outside the kitchen, I’m the kind of person who forgets to charge my phone until it’s at 3%. I once tried to bake a cake using a kitchen scale that only measured in ounces, and I spent twenty minutes panicking before realising I’d misread the conversion.

But in the kitchen, I’m the one who notices when a sauce splits, when a crust cracks, or when a dish needs just one more pinch of salt.

This site exists because that sauce taught me something deeper than technique: that the best recipes aren’t just instructions—they’re stories of what didn’t work first.

Everything here is written the way that sauce was

Every recipe on *Recipes Lantern* starts with failure. Not dramatic, not glamorous—just the kind of failure that happens when you’re learning. The first version of a dish might be bland, or burnt, or so salty you can’t eat it.

But we keep making it, adjusting, and writing down what changed each time. That’s the real recipe: the notes in the margins, the ‘what if’ questions, and the moment something finally clicks.

You’ll never see a recipe here without a timeline, a troubleshooting section, or a note about what to do if things go wrong. That’s because we know how it feels to follow a recipe that assumes you already know what you’re doing.

Here, the method is as important as the ingredients. If a dish needs to be emulsified at the end, or pulled off the heat early, or rested before slicing, we’ll tell you why—and what happens if you don’t.

And if you’ve ever made a dish from here and it didn’t turn out, send us a message. We’ll add your notes to the recipe. Because the best recipes aren’t just about what works—they’re about what happens when they don’t.

What that means for you

You’ll find recipes here that are tested for real kitchens—not just the ones with perfect ovens or mandolines. Every dish has a ‘what went wrong’ section, because we know that’s where the real learning happens.

And if you’ve ever burned a roux, over-salted a dish, or ended up with a sauce that split, you’re in the right place.

What you won’t find are vague instructions, ‘adjust to taste’ without guidance, or photos that look nothing like the real thing. Because the flame’s first lick is the moment everything changes—and we’re here to make sure yours is the right one.