WORK-064
ID:WORK-064Status:done

Section Anatomy Dimension

Priority:highComplexity:moderateMilestone:v0.9.0Source:SPEC-025
claude/file-naming-convention-LJdwR View source

Criteria completion

No incremental history — criteria tracking started on Apr 21.

Relationships

Implements 1
Branches 2
claude/file-naming-convention-LJdwR current done
main donechangeset-release/main done
History 2
  1. bbbb94c
    Created (done)by bjornolofandersson
  2. f2b3512
    Content editedby Claude
    Add {ID}-{slug}.md filename convention + migrate filenames subcommand

Summary

Add a section anatomy mapping to rune configs and the identity transform. Runes declare a sections map that associates each structural ref with a standard section role (header, title, description, body, footer, media). The transform emits data-section attributes alongside existing BEM classes, enabling themes to style structural anatomy generically across all runes.

Acceptance Criteria

  • RuneConfig in packages/transform/src/types.ts gains sections?: Record<string, 'header' | 'title' | 'description' | 'body' | 'footer' | 'media'>
  • Identity transform emits data-section on elements whose ref maps to a section role
  • Existing BEM classes and data-name attributes are preserved (additive only)
  • All container-level rune configs annotated with sections per SPEC-025 Table 1
  • refrakt inspect output shows data-section attributes on structural elements
  • Unit tests verify section attribute emission for a sample of runes

Approach

  1. Add sections to RuneConfig interface
  2. In the engine's applyBemClasses or structure injection code, when a ref matches a key in the sections map, emit data-section with the mapped role value
  3. Work through SPEC-025 Table 1 to annotate all rune configs

References

  • SPEC-025 (Universal Theming Dimensions — Section Anatomy, Table 1: Section Anatomy Map)