Our Editorial Method
How a Chopzen recipe is researched, tested, translated and corrected.
The publishing pipeline
Our standard pipeline for new recipes: pick topics that answer real reader problems, verify the source and the rights to use it, test-cook and record what happened, rewrite editorially, review the facts and the translation, publish, then keep collecting feedback and corrections. We are rolling this pipeline out recipe by recipe — a step that has not happened is never marked as done.
Recipe testing
A “tested” label, where we show one, requires a real test record: a real kitchen, ordinary equipment, actual weights and timings, failures included. Records are bound to the exact recipe version they verified, so a core change — an ingredient, a quantity or a step — invalidates the earlier claim. We are building this record system now; until it covers a recipe, we show no such label.
Languages
Natural American English is our canonical content. The Spanish, French and German versions are reviewed translations of that same canonical text — not independent rewrites — and each is checked as a whole before publication.
Corrections and updates
Corrections are applied directly to the recipe, and every published change is versioned in our editing system. If a change affects the result — an ingredient, a quantity or a step — the previous version remains traceable internally. If you spot an error, the fastest route is our contact page.
Where AI helps — and where it doesn't
AI may help us organize notes, draft translations and find inconsistencies. It does not certify that a recipe was tested: a recipe is never labeled tested on the basis of AI output alone.