WORK-384
ID:WORK-384Status:ready

Typed page entities

SPEC-092 Layers 2 + 3 — let a page declare a registry type so collection/ aggregate can query it by domain (collection type="rune"), not just type:page.

Priority:mediumComplexity:moderateMilestone:v0.21.0Source:SPEC-092
claude/v0.21-work-breakdown View source

Criteria completion

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

Tracking started Jun 11 — check back for trends.

Relationships

Implements 1
Related 3
Branches 3
claude/v0.21-work-breakdown current ready
changeset-release/main doneclaude/work-383-frontmatter-indexing donemain done
History 1
  1. 5a2b530
    Created (ready)by bjornolofandersson

Decisions (locked)

  • A page with frontmatter type (and optional id) registers as that entity type in addition to its page registration; id defaults to the page URL. Duplicate (type, id) at site scope warns (as page/heading already do).
  • No parallel config block. The url-pattern → type rule reuses routeRules: add an optional entity field (it already maps a pattern → {layout}; now {layout, entity}). Frontmatter type overrides the rule. This deliberately avoids confusion with the inverse entityRoutes (entity → page, SPEC-069).

Acceptance Criteria

  • Frontmatter type (+ optional id) registers a typed entity alongside page, with the reserved-filtered frontmatter as data; explicit id honoured, else URL.
  • routeRules accepts an optional entity field mapping a url pattern → type; frontmatter type overrides; unmatched pages stay page-only.
  • Duplicate (type, id) warns; getById/getAll/collection resolve typed entities.
  • Tests cover frontmatter-declared, config-declared, override, and collision cases.

Dependencies

  • WORK-383 (frontmatter indexing — the typed entity reuses the same reserved-filtered data).

References

  • SPEC-092 · packages/types/src/theme.ts (routeRules) · packages/content/src/entity-routes.ts (the inverse, for contrast)