The Cookdag Dialect
Cookdag extends Cooklang with explicit step-to-step dependency aliases so any recipe can be compiled into a Directed Acyclic Graph (DAG) and a Cooking For Engineers compact table.
Overview
Traditional recipes hide concurrency inside prose paragraphs. In Cookdag, each non-empty line (or step) describes a single unit of work. Ingredients, cookware, timers, and intermediate products are marked inline, letting the parser infer parallel branches and merge points automatically.
Metadata (>>)
Prefix key-value metadata lines at the top of a recipe with >>. In addition to standard fields like title, servings, and tags, Cookdag supports attribution via >> source: (auto-linking valid HTTP/HTTPS URLs with rel="noopener noreferrer", or displaying book/author text) and personal cooking notes/tips via repeated >> note: directives.
>> title: Strawberry Glazed Angel Food Cake
>> servings: 12
>> prep_time: 25 min
>> cook_time: 40 min
>> tags: dessert, cake, baking
>> source: https://example.com/angel-food-cake
>> note: Use room-temperature egg whites for maximum volume.
>> note: Store leftovers loosely covered at room temperature.Sections (==)
Group related steps under named sections using double equals signs. Sections organize the source view, group steps in the graph, and split the Engineering Table into compact, scannable sub-tables connected by clickable cross-section links. For multi-phase recipes with 6+ steps, split phases into named == Section == blocks (such as == Batter == and == Cooking & Caramelizing ==) so tables stay compact.
== Meringue ==
Whip @egg whites{12} with @cream of tartar{1%tsp} -> [stiff peaks]
== Strawberry Glaze ==
Simmer @strawberries{450%g} with @sugar{100%g} -> [glaze]Ingredients (@)
Mark ingredients with @. Use curly braces for quantities and % to separate quantity from unit. Multi-word ingredient names are terminated by the opening brace.
| Syntax | Parsed Result |
|---|---|
| @salt | Single-word ingredient, no quantity |
| @flour{250%g} | flour — 250 g |
| @olive oil{2%tbsp} | olive oil — 2 tbsp |
Cookware (#)
Highlight tools and vessels with #. For multi-word cookware, append empty braces {}. In the Engineering Table, cookware tags are folded into compact inline amber badges (for example, #Bowl or #Cast Iron Skillet) inside their step cell rather than taking up separate rows.
Sear in a #cast iron skillet{} or transfer to a #bowl.Timers (~)
Durations use ~{duration%unit} or a named timer ~bake{35%min}.
Step Dependencies (-> [alias] & [alias])
This is Cookdag's core extension to Cooklang. End a step with -> [alias] to declare its named output, then reference [alias] in any downstream step. In the Compact Table and Interactive Graph, the produced alias becomes a clickable link back to its source step.
When a single step yields multiple reusable outputs (for example, cooked pasta and reserved pasta water), declare them as a comma-separated list: -> [output a], [output b]. Each output alias can be consumed independently downstream while keeping the source step un-duplicated in the Compact Table.
Sift @cake flour{100%g} and @sugar{150%g} -> [dry mix]
Whip @egg whites{12} to soft peaks -> [foam]
Fold [dry mix] gently into [foam] -> [batter]
Bake [batter] in #tube pan{} for ~{40%min}
Boil @rigatoni{250%g} in @salted water{2%L} for ~{10%min}. -> [al dente pasta], [pasta water]
Mash [roasted feta] with 60 ml [pasta water] -> [feta sauce]
Toss [al dente pasta] with [feta sauce]Preheat & Prep Banners
Steps that begin with Preheat are automatically extracted as full-width preparation banners above the Compact Table so oven temperatures are visible before you start measuring ingredients.
Cooking For Engineers Layout Tips
- Keep each step focused on a single verb and output
-> [alias]so parallel prep branches stay crisp. - Always include units (
%g,%ml,%tsp) for clean left-column alignment. - Split multi-phase recipes (6+ steps) into named
== Section ==blocks (e.g.== Batter ==,== Cooking & Caramelizing ==) so each Engineering Table stays compact without wide horizontal trees. - Use the Compact / Full Prose toggle at the top of the Engineering Table: Compact condenses each step into scannable action verbs, timers, and inline
#cookwarebadges (with full prose on hover), while Full Prose shows complete instructions. - Use
-> [output a], [output b]or reuse a shared[alias]to render split-cell fan-out without duplicating upstream steps. - Use the Compact Table view when cooking (and for printing), and switch to Interactive Graph to inspect complex multi-branch dependencies.
Recipe Visibility & Friend Sharing
Recipes default to public and can be marked private via the editor or metadata header (>> visibility: private). Private recipes are hidden from public galleries and only visible to you. You can also connect with friends in Profile & Friends to browse each other's shared recipe boxes.
Credits & References
Cookdag builds directly upon two foundational projects in structured recipe authoring.
Cooklang
Alexey DubovskoyCookdag adopts Cooklang's inline markup for @ingredients, #cookware, ~timers, >> metadata, and == sections ==, and adds -> [alias] / [alias] step-dependency edges.
Cooking For Engineers
Michael ChuCookdag's Compact Table mode is directly inspired by Michael Chu's tabular recipe notation on Cooking For Engineers, where ingredients sit on the left and merge horizontally via rowSpan cells into finished components on the right.