About Cheese Recipes Melt

What changed, and what it changed for you

When *Cheese Recipes Melt* started, it was a collection of recipes pulled from other sites, rearranged with a few tweaks. The focus was on quantity—more recipes meant more traffic, and the assumption was that readers would figure out the rest.

The result was a site that felt hollow: no personality, no trust, and no reason to return beyond the next new post.

Now, every recipe is built from scratch, tested in the same conditions it’s written for, and written with the reader’s mistakes in mind.

The goal isn’t just to tell you how to make something, but to help you make it *right*—whether that’s fixing a burnt fondue or saving a failed brie bake.

The site still publishes new recipes, but the difference is in the details: the warnings, the troubleshooting, the stories behind why a dish matters.

The one that took years

The biggest mistake was trusting stock photos. For years, the site used images from libraries—bright, perfect, and completely unrealistic. The problem wasn’t just that they looked fake; it was that they set the wrong expectations.

A reader would see a flawless gratin dauphinois and try to replicate it with their own hands, only to end up with something lumpy or burnt. The photos lied, and the site lost credibility every time.

The reason it stayed this way for so long was laziness. Buying or licensing photos was expensive, and shooting your own required time, equipment, and a willingness to fail repeatedly.

The first attempts were disastrous: over-exposed cheese platters, blurry close-ups, and lighting that made everything look like it was shot in a cave.

But the real turning point came when a reader emailed to say they’d given up on a recipe because ‘the photo made it look impossible.’ That was the moment the site realized: if the images don’t help, they hurt.

Fixing it cost $2,400 for a used Canon R5 and a single speedlight, plus three months of shooting nothing but failed attempts. The rule now is simple: no recipe is published without a photo taken that day, in the same kitchen, with the same ingredients.

The lighting is adjusted for the dish’s temperature—warm and golden for a baked camembert, cool and sharp for a fresh mozzarella salad—and every shot is taken twice: once for the hero image, once for the ‘what it looks like mid-cook’ warning. It’s slower, more expensive, and far more honest.

Meet the author

I used to think recipes were just instructions. If you followed the steps, you’d get the result, and if you didn’t, it was your fault. So I wrote like a manual: cold, precise, and detached.

The first drafts of this site were full of passive voice (‘the cheese should be melted’) and no room for the reader’s failures.

I even avoided mentioning things like ‘this dish is tricky if your oven runs hot’ because I assumed people would figure it out—or blame themselves if they didn’t.

Readers would post frustrations like ‘My fondue curdled’ or ‘The quiche cracked,’ and I’d reply with generic fixes (‘Check your cheese temperature’).

It never occurred to me that the real issue was the site wasn’t *showing* them how to fail—and how to recover. The worst moment was when someone wrote, ‘I don’t know why I keep messing this up,’ and I realized I’d never actually *seen* them mess it up.

I’d only ever seen the perfect version.

What changed was the day I stopped writing for myself and started writing for the person holding a wooden spoon at 11 p.m., wondering if they’d ruined dinner.

Now, Perry Sandoval writes recipes as if the reader is standing in his kitchen, with all the mess and the lessons. Every warning (‘Don’t skip the blooming step—trust me’) and every aside (‘This part is where people panic’) is there because someone actually did panic.

The goal isn’t to sound like a chef; it’s to sound like someone who’s been there—and lived to tell the tale.

What did not change

The core belief—that food is more than fuel—hasn’t wavered. From the start, the site treated recipes as stories, not just steps.

The first posts included anecdotes about where a dish came from, like the time abuela’s *queso fundido* saved a family argument or how a burnt *soufflé* led to a late-night laugh. That hasn’t changed.

The difference now is that the stories are tighter, the lessons are clearer, and the humor is intentional.

The site still refuses to publish anything that hasn’t been tested at least twice. The early versions had recipes with typos, missing ingredients, and steps that didn’t make sense. Those mistakes aren’t just fixed now—they’re prevented. But the rule itself? That’s stayed the same.

If it hasn’t been made (and remade), it doesn’t go live.

What is still being fixed

The next big change is making every recipe adaptable for dietary restrictions without requiring a separate ‘vegan version’ or ‘gluten-free rewrite.’ Right now, the swaps are buried in footnotes, and the site knows that’s not enough.

The plan is to build a system where filters—like ‘nut-free,’ ‘dairy-free,’ or ‘one-pot only’—automatically adjust the recipe in real time, with visual cues showing how the dish might look or taste differently.

It’ll take another year of testing, and it’ll cost more in developer hours, but the goal is simple: no reader should ever feel like they can’t use a recipe because of what’s *not* in it.

If you’ve got ideas for what’s missing—or what’s still broken—there’s a contact page for that.