WORK-712
ID:WORK-712Status:ready

A rune page has one shape, and the attribute table renders a rune's family

SPEC-193 D1. Rune pages have no fixed section order, and the attribute table sits under H2, H3 or H4, often nested under the example before it. About 20 pages include the attribute partial once per child rune, and two document only the child.

Priority:highComplexity:moderateMilestone:v0.49.0Source:SPEC-193
claude/composition-usage-rune-pages-c87ar6 View source

Criteria completion

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

Tracking started Nov 4 — check back for trends.

Relationships

Implements 1
Related 7
Branches 1
claude/composition-usage-rune-pages-c87ar6 current ready
main ready
History 1
  1. fc48b67
    Created (ready)by bjornolofandersson

Acceptance Criteria

  • The rune page template (D1: intro, opening paragraph, "Basic usage", "How Markdown is read", task sections, "Attributes", "See also") is written down in extend/rune-authoring/
  • The attribute partial, included once with the parent rune, renders the parent's table and then each child's under its own ###, from the child-to-parent mapping (PAGELESS)
  • Every rune page has exactly one attribute include, under ## Attributes, after its task sections; pricing and steps document their parent rune too
  • check-rune-docs fails on a rune page whose attribute include is missing, repeated, or not under ## Attributes
  • "See also" is the one name for related links; the two "Related" sections are renamed

Blocked by

  • WORK-711

References

  • SPEC-193: D1.
  • SPEC-128: the generated attribute tables.