About Bread Recipes Jar

What changed, and what it changed for you

When *Bread Recipes Jar* began, it was a scrapbook of half-remembered techniques and borrowed instructions. Recipes were long lists of ingredients and steps, with no explanation of why a pinch of salt mattered or how to tell when dough was ready.

The site looked like every other recipe blog: a mix of screenshots, vague measurements, and no real structure.

Now, every recipe is built to answer *one* question first: *What’s the problem this solves?* A sourdough starter that fails? We tell you how to fix it. A crust too thick? We show you how to adjust it.

The steps are still there, but they’re wrapped in the reasoning behind them—so you don’t just follow, you understand.

The one that took years

The biggest mistake was treating recipes like instructions, not conversations. For years, we published steps without context—no warnings about common pitfalls, no troubleshooting, no sense that the kitchen was a place where things could go wrong.

* and we’d reply with generic advice, if we replied at all.

The problem stayed wrong for so long because we assumed home cooks already knew the basics. We thought if someone couldn’t bake a loaf of bread, they’d just look up another recipe. But the truth was simpler: most people *want* to learn, but they don’t want to feel stupid asking.

So we kept writing the same way, and the comments kept asking the same questions.

It finally changed when we realized the real job of a recipe wasn’t to tell you *what* to do, but to show you *how* to do it—even the parts that could go wrong.

That meant rewriting every recipe to include a ‘what could go wrong’ section, testing failures as carefully as successes, and admitting when we’d messed up (like the time a batch of focaccia collapsed because we forgot to proof it long enough).

Keeping it this way costs time. A single recipe now takes *at least* a full day to develop, test, and rewrite—photography, troubleshooting, and writing the notes all add up.

But the alternative was worse: a site full of recipes that worked in theory but failed in practice, and readers who trusted us less every time they had to guess why their dish didn’t turn out.

Meet the author

I used to think recipes were just a list of ingredients and steps, like a math problem where the answer was always the same if you followed the rules. So I wrote them that way—straightforward, no frills, and definitely no excuses for when things went wrong.

If your bread didn’t rise, I’d say *‘check your yeast’* and move on. The truth was, I didn’t want to admit I’d ever failed, so I never talked about it.

I also believed that if you couldn’t bake a decent loaf of bread with the instructions I gave, you just weren’t cut out for it. That’s why I never included troubleshooting or alternative methods—because I thought it would make the recipe seem too complicated. The result?

A site that felt rigid, unhelpful, and a little bit judgmental. And worse, it was all wrong.

What changed was realizing that the best recipes aren’t about perfection—they’re about problem-solving. One day, I burned a batch of brioche because I rushed the proofing, and instead of pretending it never happened, I wrote about it. Then I tested how to fix it.

That’s when I understood: the real value of a recipe isn’t in the steps, but in the lessons.

Now, *Gordon Delgado* is the name behind every recipe here. I’m the one who tests each one until it works—not just once, but in different kitchens, with different ingredients, and with the mistakes home cooks actually make.

My goal isn’t to write a flawless recipe; it’s to write one that helps you avoid the flaws *you’ll* run into.

What did not change

The core idea hasn’t wavered since day one: this site exists to make baking feel less intimidating. Whether it’s a no-knead loaf for beginners or a challenging sourdough for experts, the goal is the same—help you turn simple ingredients into something extraordinary.

That’s why we’ve never gone overboard on fancy techniques or obscure ingredients, even when trends suggested we should.

Another thing that stayed the same is the focus on *real* kitchens—not just the ones in cookbooks or on TV. That means no recipe here assumes you have a stand mixer, a proofing box, or even a perfectly calibrated oven.

If a step requires a special tool, we’ll tell you how to do it without one. The only rule? No shortcuts that sacrifice flavor or texture.

What is still being fixed

Right now, we’re working on making the site even more useful for people with dietary restrictions—like recipes that work with common pantry staples for gluten-free or dairy-free bakers, or options for those who can’t tolerate nuts or eggs.

The challenge isn’t just finding recipes that fit; it’s making sure they still taste great without feeling like compromises.

If you’ve got ideas for how we can improve—whether it’s a recipe you’d love to see, a way to organize the site better, or even a mistake you’ve made (and how we could’ve helped you avoid it)—we’d love to hear from you.

The contact page is the best place to share your thoughts.