
What changed, and what it changed for you
When I started, I just wanted to share the recipes I loved. I’d find something online, tweak it a little, and post it without a second thought. The site was a mess—no consistent formatting, no real photos, just words on a page. I was copying, not creating. And honestly?
Most of the time, I didn’t even use the recipes myself before publishing. That’s not how you build trust.
Now, every recipe is tested at least three times. I bake, I taste, I adjust, and I take photos that show exactly what you’ll get. The steps are broken down so you can follow along without guessing. And the writing? It’s not just instructions—it’s the *why* behind the dish.
Because cooking isn’t just about following steps; it’s about the moments those recipes help you create.
| It used to be | Now it is |
|---|---|
| Recipes copied from other sites with no original testing. | Every recipe is tested in my kitchen, with adjustments made for real home cooks. |
| Photos were often stock images or blurry phone snaps. | Every photo is taken by me, with clear lighting and angles that match the steps. |
| No consistent structure—some posts had 5 steps, others had 20. | Every recipe follows the same format: ingredients, steps, tips, and a note on where it came from. |
| The writing focused only on instructions, no context or stories. | Recipes include the history, the people, or the memories tied to the dish. |
The one that took years

For years, I avoided taking my own photos. I told myself I didn’t have the right camera, the right lighting, or the right skills. So I used stock images or borrowed photos from other sites. The problem? They never matched the recipe.
A stock photo of a cake looked nothing like the dense, fudgy brownie I’d just described. Readers would follow my steps, expect one thing, and get something else. It was frustrating for them—and it made me look unreliable.
The real blocker wasn’t skill. It was fear. I was afraid my photos wouldn’t be good enough, so I’d rather just copy someone else’s work. But that meant I was never truly sharing *my* version of the dish.
It took a broken camera and a borrowed light setup to force me to start. I ruined at least 12 pans of cookies before I got the hang of it. Now, every photo is mine, even if it’s just my phone on a tripod with natural light.
It cost me time, patience, and a few burnt batches—but it fixed the one thing that made the site feel dishonest.
Keeping it up costs money now—better equipment, sometimes a helper to taste-test, and the time to edit photos properly. But the alternative was worse: a site that promised one thing and delivered another. At least this way, you know exactly what you’re getting.
Meet the author

I used to think cooking was about precision—measuring everything to the gram, following recipes like they were science experiments. My grandmother’s kitchen was always messy, but I’d roll my eyes at the way she’d ‘eyeball’ the flour or taste the sauce before adding salt. I believed in rules, not intuition.
And when I started writing, I treated recipes the same way: cold, exact, with no room for the chaos of real life. The result? Recipes that felt more like homework than joy.
I also used to write in silence. No stories, no memories—just instructions. I thought people only cared about the end result, not how it got there. That changed the day my son asked why we were making his favorite cake.
I realized then that food isn’t just fuel; it’s the reason we gather, the thing we pass down, the memory we hold onto. If I wasn’t sharing *that*, what was the point?
What changed: I started writing like I cook—with my hands in the dough, my mind on the people who’ll eat it.
Now, I’m Ramona Mensah, and this is my kitchen, my stories, and my recipes. I test everything myself, I write about the people who inspired the dishes, and I make sure every photo shows you exactly what you’ll get.
The site isn’t just about food; it’s about the moments those recipes help you create—and the way they connect us all.
What did not change
From the start, this site was always about real food—no shortcuts, no gimmicks. I’ve never believed in ‘foolproof’ recipes that hide the work. If a dish takes time, I’ll tell you upfront. If it’s tricky, I’ll walk you through it.
And if it’s a family recipe with a story, you’ll hear it. That hasn’t changed. The way I talk about food might have gotten clearer, but the core belief—that cooking should be honest, rewarding, and full of heart—has stayed the same.
Another thing that’s never wavered? The focus on home cooks. I don’t write for chefs or food professionals.
I write for the person who’s standing in their kitchen, wondering if they can pull off a dish for dinner guests, or the parent who’s trying to get their kid to eat something green. That’s always been the point, and it always will be.
What is still being fixed
Right now, I’m working on making the site even faster. Some of the older recipes load slowly, and I know that’s frustrating.
I’m also testing new ways to organize the archive so you can find what you’re looking for quicker—whether it’s a dessert for a last-minute party or a weeknight dinner that won’t take all evening.
And I’m still learning how to tell stories better: not just *what* to make, but *why* it matters.
If you’ve got ideas—recipes you’d love to see, ways to improve the site, or even just a dish that brought you joy—I’d love to hear from you. The contact page is the best place to share.
Things that would help
- A recipe you’ve made (or failed at) that you’d love to see here—tell me why it’s special.
- Suggestions for organizing the site so it’s easier to find what you need.
- Photos or tips from your own kitchen that could make a recipe even better.
The recipes are grouped by category: Desserts.
