WORK-675
ID:WORK-675Status:ready

The content-boundaries guide documents the narrative field

The "Content boundaries" section of site/content/extend/rune-authoring/patterns.md puts "Story, editorial, famous quotes" outside recipe. ADR-047 adds a case: a rune may declare one narrative field that takes {% textblock %} and {% mediatext %}, so a template can place the story between the rune's parts. A site's own composed rune can declare one today.

Priority:lowComplexity:simpleMilestone:v0.46.0Source:ADR-047
claude/post-v0.43-roadmap-mf1ngx View source

Criteria completion

Criteria completion: 0 of 5 (0%) checked; tracking started on Oct 28, no incremental history yet0%25%50%75%100%Oct 28Nov 4

Tracking started Oct 28 — check back for trends.

Branches 3
History 2
  1. 0ec343f
    Content editedby bjornolofandersson
  2. 8c20651
    Created (ready)by bjornolofandersson

Acceptance Criteria

  • The section keeps its three tests and adds the narrative-field case, with the food-blog layout (name, image and times; the story; a card with ingredients and method) as its example
  • The "What goes where" table notes that a story may sit inside a rune that declares a narrative field, wrapped in an editorial rune
  • The guide states the two rules: one narrative field per rune, never mapped to structured data, and that loose prose inside the rune is still outside its content model
  • The composed-runes guide shows a definition with a story field and a template placing it
  • npm run format:md:check passes

References

  • ADR-047.
  • WORK-674: the checks the guide describes.