About Recipes Velvet

About Recipes Velvet

What changed, and what it changed for you

This site started as a series of scribbled notes on napkins—recipes I’d tweaked over and over, passed between friends until they stopped falling apart. The first version had no structure, no consistency, and no way to trust what you’d read.

If a recipe failed, there was no way to know why.

Now, every recipe is built to survive the things that break others: an oven that runs hot, a pan that’s seen better days, or a kitchen where the only measuring spoon is a tablespoon from the silverware drawer.

The photos aren’t staged—they’re what the dish actually looks like when it’s done right.

It used to beNow it is
Recipes written once, with no testing beyond the first attempt.Every recipe is tested at least twice, with adjustments for real cooking conditions.
No structure—steps were added or skipped as needed.A strict, repeatable format so every recipe works the same way.
Photos were stock images or poorly lit snapshots.Every photo shows the dish as it comes out of your kitchen, not a professional’s.
No explanation for why a method worked (or didn’t).Every recipe includes the reasoning behind each step—so you can adapt it.
Four things you can check yourself by comparing old and new recipes.

The one that took years

The biggest problem was time. Recipes were added as fast as I could write them, with no way to verify if they’d work for someone else.

A dish that turned out perfect in my kitchen—with a specific brand of flour, a precise oven temp, and a cast-iron pan that had been seasoned for years—often failed for anyone else.

The fixes were obvious: test more, document everything, and accept that some recipes would take weeks to get right.

What kept it wrong for so long was laziness. I’d write a recipe, post it, and move on.

The feedback came in dribs and drabs—‘This didn’t work,’ ‘The texture was off’—but I’d file it away as ‘their problem, not mine.’ It wasn’t until a reader sent a photo of a cake that had collapsed into a dense brick that I realised: if I didn’t care enough to fix it, why should they?

The fix cost money, time, and a lot of ruined pans. Now, every recipe is tested in three different ovens—mine, a borrowed one with a faulty thermostat, and a rental kitchen with no preheating. Some dishes take months to perfect.

But the alternative was worse: a site where recipes worked *for me* but not for anyone else. The cost was worth it.

Meet the author

Desmond Hollis

I grew up in a house where cooking was a chore, not a skill. My first attempts at baking ended with singed edges and a kitchen that smelled like regret. I learned early that recipes were more like suggestions than rules—adjust, improvise, and hope for the best.

For years, I wrote recipes the way I cooked: fast, loose, and with the assumption that if it worked for me, it would work for you.

The worst thing I did was assume my kitchen was average. It wasn’t. My stove was old but reliable; my measuring cups were precise; my oven heated evenly. When recipes failed for others, I’d blame their equipment or their technique, never my own instructions.

It took a friend burning a batch of cookies in a rental apartment to make me realise: if a recipe doesn’t work in a *bad* kitchen, it’s not a good recipe.

What changed was the realisation that a recipe isn’t just a list of ingredients—it’s a promise. And promises only work if they’re kept.

Now, I run this site to make sure those promises hold. Every recipe is written by Desmond Hollis, tested in kitchens that aren’t mine, and designed to work whether you’re a first-timer or a seasoned cook.

The goal is simple: no more excuses, no more guesswork, just food that brings people together.

What did not change

The core belief hasn’t shifted: good food should be accessible, not intimidating. Whether it’s a weeknight dinner or a holiday centerpiece, the best meals are the ones that make cooking feel like a joy, not a test. That hasn’t changed since the first napkin note.

Neither has the rule about patience. Rushing a recipe—skipping steps, eyeballing measurements, or rushing the oven—rarely ends well. The site still assumes you’ll take your time, because that’s when the magic happens.

The only thing that’s faster now is the feedback loop: if a recipe isn’t working, you’ll know why before you’ve even finished reading.

What is still being fixed

The next big change is making every recipe adaptable for dietary restrictions without sacrificing flavour. Right now, we’re testing substitutions for gluten, dairy, and common allergens—but the real work is ensuring those swaps don’t turn a great dish into a compromise.

It’s slow, because flavour is fragile, and we’re not done yet.

If you’ve got a kitchen quirk—an oven that runs hot, a pan that doesn’t distribute heat evenly, or a family tradition that refuses to die—tell us about it. The contact page is the best place to start.

Things that would help

  • Your oven’s quirks (does it run hot? Does it cool down when you open the door?)
  • A recipe that worked for you but failed for someone else—and why
  • A dietary restriction you’ve successfully navigated in a dish you love

The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.

Read our recipes