Editorial Guidelines
Use these principles when proposing a new recipe or revising an existing one.
The Editorial Zen
- Clear is better than clever.
- Specific is better than implied.
- One action per step beats many actions at once.
- Useful detail beats decorative prose.
- Consistency across recipes builds trust.
- When in doubt, write for the beginner.
- If two interpretations are possible, rewrite.
- Strong recipes are testable, repeatable, and teachable.
Recipe Clarity Standards
- List exact ingredient amounts, clear units, and preparation notes (e.g., diced, softened, drained).
- Name the vessel and heat level for each cooking step whenever applicable.
- Write one action per step in chronological order so beginners can follow without inference.
- Include timing cues and doneness signals (color, texture, temperature), not timing alone.
- State servings and total time realistically for a home cook.
Technique Notes Standards
- Use canonical technique names where possible so similar ideas map to the same technique entry.
- Keep Why it works general and reusable; keep Why this recipe uses it specific to the dish.
- Avoid contradictory advice across recipes for the same technique unless clearly justified.
Revision Readiness Checklist
- Diffs should be easy to review: avoid unrelated rewrites in a single revision.
- If changing tools, ingredients, or technique rationale, ensure all dependent steps are updated.
- When linking related recipes, use links that are directly useful to execution of this recipe.
- Before submitting, verify the recipe can be cooked start-to-finish by someone new to the dish.