WORK-684
ID:WORK-684Status:done

The plugin hero accepts start and end for align, and the site content uses them

The composed hero takes align="start | center | end", which is section's vocabulary. The plugin hero takes left | center | right. The staging site renders the same content as main, so align="left" on the homepage and on the hero reference page would be invalid there (SPEC-181 D7). The plugin hero learns the new values first, and the content moves to them.

Priority:highComplexity:simpleMilestone:v0.44.0Source:SPEC-181
main View source

Criteria completion

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

Tracking started Oct 29 — check back for trends.

Relationships

Implements 1
Related 3
Branches 3
main current done
claude/milestone-v0-44-0-ism7ni donemain doneclaude/rune-compositions-staging-f9ouim ready

Acceptance Criteria

  • The plugin hero accepts start and end for align, rendering them exactly as left and right; left and right keep working
  • site/content/index.md and site/content/runes/marketing/hero.md use start / end, and nothing else in site/content writes left / right on a hero
  • The hero reference page documents start | center | end, and notes that left / right still work for now
  • main's rendered output for those pages, the contracts and the SEO baseline are unchanged, or any diff is explained
  • A changeset records the new values

Approach

  • Map the value at the attribute, before the modifier is read, so the root's data-align stays left / right and Lumina's hero.css needs no change.
  • Whether left / right raise a deprecation warning is left to the go-live item. While the plugin is live, both are valid.

Blocks

  • WORK-681

References

  • SPEC-181: D7, the rollout's gate 3.
  • WORK-665: the align difference.

Resolution

Completed: 2026-10-30

Branch: claude/milestone-v0-44-0-ism7ni

What was done

  • plugins/marketing/src/tags/hero.ts: align matches start | center | end | left | right; start / end are mapped to left / right before the modifier reads them, so data-align and hero.css are unchanged.
  • site/content/index.md and site/content/runes/marketing/hero.md use start; no hero in site/content writes left / right. The reference page documents start | center | end and notes left / right still work.
  • Test in plugins/marketing/test/hero.test.ts: start / end render a tree identical to left / right.
  • Changeset hero-align-start-end.

Notes

  • Rendered output is unchanged by construction (the identical-tree test); contracts and the SEO baseline are unchanged.