WORK-716
ID:WORK-716Status:ready

Rune pages say how Markdown is read and when to use the rune, in place of the Section header boilerplate

SPEC-193 D6 and D1.2, D1.4. The "Section header" paragraph is repeated on 20 rune pages (twelve with a typo), and almost no page says when to use the rune rather than its neighbour.

Priority:mediumComplexity:moderateMilestone:v0.49.0Source:SPEC-193
main View source

Criteria completion

Criteria completion: 0 of 4 (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 3
Branches 2
main current ready
main readyclaude/composition-usage-rune-pages-c87ar6 ready

Acceptance Criteria

  • The 20 "Section header" sections are removed
  • Each rune that reinterprets Markdown has a short "How Markdown is read" table, one row covering the eyebrow, headline and blurb where it reads them, linking to Page sections
  • Each rune with a neighbour a reader could mistake it for has a "when to use this" line in its opening (the pairs in SPEC-193 F7)
  • xref.md says that {% ref %} is the same rune

Blocked by

  • WORK-712

References

  • SPEC-193: D1, D6, F5, F7.