DessertCat
about

A field guide to global desserts

DessertCat is an independent, slowly grown catalogue of traditional desserts from around the world — a single place to learn what a sweet is, where it comes from, why its technique works and how to make it at home. This page explains how the site is written, where its information comes from and how we handle mistakes.

i. Why DessertCat exists

Most recipe sites treat desserts as interchangeable — a brownie is a brownie, a flan is a flan. DessertCat starts from a different premise: that every named sweet has a place it comes from, a reason for being made the way it is, and a method worth getting right.

We do not try to compete with the large recipe networks on volume. We try to be the place you come to when you have heard a name you do not know — kue lapis, chak-chak, kuzumochi, kremna rezina — and want a clear answer to what is it, where is it from, and how do I make it?

ii. Our editorial approach

Every dessert page on DessertCat follows the same structure, so you always know where to look:

  • A direct definition. The first sentence of each page says what the dessert is, where it is from and what it is made of.
  • Origin and history. Where and when the dessert appears, the occasions it belongs to, its regional names and how it differs from similar sweets.
  • Technique. A section on the one or two things that make the dessert work — why a syrup goes on cold, what tapioca starch does to a steamed cake, why suet behaves differently from butter.
  • A complete recipe. Metric quantities that scale with the servings control, oven temperatures in °C and °F, and visual cues for doneness rather than times alone.
  • Tips, variations, serving and storage, followed by answers to the questions readers most often ask about that dessert.

We write in a plain, specific voice and avoid filler. Where a page falls short of that standard, we rewrite it; many older pages on the site have been expanded this way.

iii. How recipes are researched

Each recipe is built by comparing several independent sources rather than adapting a single one: published cookbooks from the dessert's home region, established general references on pastry and confectionery, food-history writing, and recipes published by cooks from the tradition itself. Where those sources agree, we follow them. Where they differ, we choose the version that is most widely recognised in its home country and mention the main alternatives in the variations section.

Quantities are checked against the ratios that make each type of dessert work — sugar to liquid in a syrup or sorbet, flour to fat in a pastry, starch to liquid in a set pudding — so that the proportions are sound before a recipe is published. Where a traditional ingredient is hard to find outside its home region, we name it first and then suggest the substitution that gets closest, rather than quietly rewriting the dessert into something else.

History is the area where food writing is most often wrong, so we are deliberately careful with it. Legends and origin stories are presented as stories ("the tale goes…", "is often credited to…"), and we avoid precise dates, named inventors or figures unless they are well documented.

iv. Sources and independence

Our research draws on cookbooks, culinary reference works, food-history scholarship and the knowledge of cooks within each tradition. We do not copy recipes or text from other publishers; every page is written for DessertCat.

DessertCat is independent. We do not accept paid placements or sponsored recipes, and no brand pays to appear on a page.

v. Corrections policy

We want DessertCat to be accurate, and we know a catalogue this broad will sometimes be wrong. If you find a misattributed origin, an inaccurate history, an ingredient that would not actually be used, or a step that does not work as written, please contact us and tell us which page and what is wrong.

We review every correction we receive. When a correction is confirmed, we update the page itself rather than adding a note elsewhere, and substantive changes to a recipe — a quantity, a temperature, an attribution — are made to the text directly so that the page you read is always the current, corrected version.

vi. A note on cultural respect

Any catalogue of the world's desserts is mostly describing food that belongs to other people, and we try to credit it properly. That means naming places, techniques and traditions. Where there are genuine regional disagreements — is dodol Indonesian or Malaysian? who first made a particular pastry? — we describe the disagreement rather than declare a winner.

We also use a dessert's own name first and its translation second: topfenstrudel, not "Austrian quark strudel"; khanom chan, not "layered Thai cake". A name in its own language is the smallest possible respect for where a thing comes from.

vii. Where to go next