Places plugin migration to metaFields + zones
Phase 2 of SPEC-079. Migrates the places plugin's meta-bearing rune (Event) from the legacy slots + structure config shape to the new metaFields + zones + contentSlots model.
Phase 2 of SPEC-079. Migrates the places plugin's meta-bearing rune (Event) from the legacy slots + structure config shape to the new metaFields + zones + contentSlots model.
Tracking started Jun 1 — check back for trends.
plugins/places/src/config.ts Event entry rewritten.
date reads more naturally as an eyebrow than as a metadata cell). Metadata: all three fields, with date and endDate using tag: 'time' for proper <time datetime="…"> output.date — endDate rendered as a single visual unit in the legacy structure) needs the same effect via the new model. Options: (a) declare both fields in metadata and let the def-list render two rows; (b) keep them as a custom dateRange zone using chip-row to render side-by-side; (c) project them as an eyebrow with split (left: date, right: endDate).Itinerary / Map / MapPin untouched. Either no meta projection or container runes — stay on the existing path.
Per-rune CSS updated. Selectors in plugins/places/styles/event.css referencing __header-primary / __header-secondary rewritten.
Plugin tests updated. Tests in plugins/places/test/ reflect the new DOM shape.
Backwards-compat shim warning silent for places.
Docs. Event rune doc page (site/content/runes/places/event.md) — output-contract snippets updated.
Single-rune migration. The date-range visual is the only place that needs design judgement — try the simple two-row def-list first, escalate to a custom zone if it reads worse than today's side-by-side.
Completed: 2026-06-02
Superseded by WORK-319. Targeted the SPEC-079 zones model; places (Event) migrated straight to the SPEC-080 blocks/layout model instead on branch claude/definitions-list-styling-9nOGL.