Render the recipe notes sidecar
P1 priority Donep1-is-render-the-recipe-notes-sidecarnotes.md prose renders nowhere: nothing reads it
- Stage
- 03-done
- Author
- Ivan Hawkes
- Created
- Completed
- Depends on
- References
be-best/layouts/_partials/recipes/notes.htmlbe-best/layouts/recipe/page.html
notes.md prose renders nowhere: nothing reads it.
The split of 3d53ff4 moved the notes of five recipes out of index.md and
into a notes.md sidecar each. No layout read the file, so that prose stood in
the bundle and rendered nowhere: a recipe page ran its content, its steps, and
straight past its notes.
Work
- Notes partial -
be-best/layouts/_partials/recipes/notes.html, the sibling ofmethod.htmlandingredients.html: it reads the bundle’snotes.mdwith.Resources.GetMatchand emits the resource’s rendered.Content. - Leaf-bundle resource - Hugo makes a markdown file inside a leaf bundle
a resource of its page, of type
page, not a page in its own right: the five files build no URL, join no listing and add no page: the build gains none when they sit in the tree. The partial reads them as resources. - Placement - the partial is the last call in the recipe page’s second
column, after
method.html, so a page runs the prose ofindex.md, the steps ofmethod.yaml, then the prose ofnotes.md. - Prose wrapper -
recipe-notes prose w-full prose-neutral prose-custom dark:prose-invert, the classes the method’s wrapper sets, so the notes carry the prose and the scheme of the steps above them.recipe-notesis a hook: CSS not written (CNW). - Optional - a bundle with no
notes.mdprints nothing at all: 53 of the 58 recipe bundles carry none, and each of those pages renders exactly as it did before the sidecar existed. - Definition - the sidecar paragraph of
content/specification/technical/index.mdand the two recipe bullets ofAGENTS.mdname the file, the partial that renders it, and the resource rule that keeps it from building a page.
Acceptance Criteria
- Each bundle that carries the sidecar renders it under its steps -
lamb-rogahn-josh, murghi-korma, laksa, red-curry-paste, tom-yum-soup: one
recipe-notesdiv on each of the five pages, after the lastrecipe-method-stepslist. - A page with no
notes.mdrenders nothing of it: the other 53 recipe pages carry norecipe-notesdiv, and no placeholder line. - A note stays a section, not a page: the five files open their headings at
level two, each page keeps exactly one
h1, and the notes heading is the page’s onlyh2- red-curry-paste carries two,OptionalandNotes. - The file is rendered, not printed: its headings reach the page with their
anchor ids, as
id="notes"andid="optional-method". -
pnpm run testpasses: 425 pages with exactly oneh1, 45 pages carrying images with 59 placeholder classes against 59 rules, 50 cards valid, 58 method files valid and their 442 steps rendered, prettier setup intact.
Notes
- The notes reach a feed nowhere, and no listing: they are a resource, and the
page’s
.Contentand.Summaryare the prose ofindex.mdalone. The card of a recipe, and the section’s RSS, stay as they stood. notes.mdcarries no front matter. Hugo parses its absence, and.Contentis the whole file.- No content references the sidecar:
grep -rn notes.md content/post/recipe/finds nothing, so the file is read by the layout alone. - The leaf-bundle rule was measured, not remembered: a debug build of the laksa
bundle lists
notes.mdamong.Resourceswithrt=pageand reports.Pages: 0.
Not in scope
- A schema and a check for
notes.md, asassets/recipe-method.yamlgivesmethod.yaml: no validator reads the file, and no check reads its rendering. - Moving the notes out of the prose of the 53 recipes that keep them in
index.md. - A styling pass for the notes column: the prose sets them as they stand.