Editorial standards

Chef recipes are built around well-established home techniques — cheela and chilla batters, bhurji-style paneer, blender batters, overnight soaking — adapted toward two compositional goals: more protein per serving and no added sugar. We start from the technique, choose ingredients that are practical to buy in India, and work out quantities that meet the nutrition target without making the dish worse to eat.

Recipes are written by the site’s editors under the byline "The Chef Kitchen". We do not claim professional culinary or clinical credentials, and no recipe on this site should be read as the product of either.

Every quantity is explicit and metric: weighed in grams, or measured in ml, teaspoons or tablespoons. There are no handfuls and no "some". Where a quantity is genuinely to taste (salt on a finished dish), the ingredient says "to taste" instead of pretending precision.

Quantities are set at the recipe’s stated servings, and the serving scaler multiplies them linearly. Ingredients that do not scale linearly in practice (raising agents, salt at large multiples) are flagged in the cook’s notes where it matters.

Nutrition values are computed from standard published ingredient composition data, summed across every listed ingredient at its stated quantity, divided by the stated servings, and rounded for readability. Optional ingredients are included unless a recipe’s notes say otherwise. Recommended sides and pairings are never included — combined figures appear only in pairing cards labelled "Estimated nutrition when paired with".

Before any recipe can be published, an automated check recomputes calories from its stated macros — 4 kcal per gram of protein and carbohydrate, 9 kcal per gram of fat — and fails the build if the result differs from the stated calories by more than 12%. The same suite rejects added sugar exceeding total sugar, saturated fat exceeding total fat, and any tag the numbers do not support: "High protein" requires at least 15 g of estimated protein per serving, "No added sugar" requires exactly 0 g of added sugar, and "Under 20 minutes" requires prep plus cook time of 20 minutes or less.

These checks run in the publishing pipeline itself. A recipe that fails them cannot reach the site, and the checks cannot be skipped for an individual recipe.

Composition tables describe average ingredients; your kitchen contains specific ones. Brands differ (two skyrs can differ meaningfully in protein), produce varies with ripeness and season, and cooking changes weight and water content. A calculated value is the honest ceiling of what a recipe website can offer — we publish it as an estimate and never present it as a measured or laboratory-analysed value.

Every recipe passes two kinds of review before publication. Automated: schema validity, the macro and tag checks above, and a language screen that rejects medical-claim wording. Editorial: the steps are read against the ingredient list for order, completeness and internal consistency — every listed ingredient must be used, every step must be possible with what came before it, and times and temperatures must be plausible for the technique.

We do not claim independent laboratory analysis of nutrition, and we do not publish testimonial-style claims about results.

Food composition is checkable; health outcomes in your body are not something a recipe website can promise. So recipes describe what is in the food — protein, added sugar, fibre, cost — and never what the food will do for you. Words like "cures", "detox", "burns fat" and "boosts immunity" are on a banned-language list enforced by the publishing pipeline: copy containing them cannot be published.

Tags such as "High protein" are compositional statements with published numeric definitions, not health advice.

"No added sugar" means exactly what it says: no sugar, jaggery, honey, syrup or other caloric sweetener is added at any stage. It does not mean the dish is low in sugar overall — fruit and dairy contribute their own sugars, and a banana-sweetened pancake carries real sugar from the banana.

That is why every nutrition panel shows total sugar separately from added sugar, in the full nutrition detail. If total sugar matters to you, read that number, not the tag.

When published content turns out to be wrong — a nutrition value, a quantity, a claim that reads stronger than the evidence — we correct the page and log the correction publicly instead of editing silently. The corrections page lists what changed, on which recipe, and when.

Every recipe and side carries a published date, an updated date and a version number, shown on the page. The version starts at 1.0 and increments only when published content actually changes; the updated date is set to the date of that change and is never invented or backdated. The publishing pipeline enforces the pairing — a version bump without an update date, or the reverse, fails the build.