Duplicate ID — this entity is also defined in plan/work/WORK-667-a-stack-layout-for-blocks.md. Only one definition per ID is supported; edits may target the wrong file. Remove the duplicate to resolve.

A lead layout for blocks

A blocks entry renders through bar (a row) or definition-list (a label/value grid). Neither draws a byline, a lead value with secondary values beneath, which testimonial and cast each hand-roll in their CSS (SPEC-161 D6).

claude/post-v0.43-roadmap-mf1ngx View source

Criteria completion

Tracking started Oct 26 — check back for trends.

Relationships

ID:SPEC-161Status:draft

Marketing runes on section: what each needs to compose

ID:BUG-023Status:confirmed

data-meta-rank is styled and specified but emitted by nothing

Severity:minor

ID:v0.44.0Status:planning

v0.44.0 — Hero, cta and testimonial compose

ID:WORK-668Status:ready

testimonial is a composition over section, with a codemod for its byline

Priority:mediumComplexity:complexMilestone:v0.44.0

Oct 27, 06:30 AM3c2340b
Content editedby bjornolofandersson
Oct 26, 08:16 PM07d27ce
Created (ready)by bjornolofandersson

Acceptance Criteria

LayoutPrimitive gains lead; a block in it renders its fields in a column as data-zone-layout="lead", with the first field marked data-lead
Skeleton and Lumina style the lead as emphasised and the rest, by :not([data-lead]), as smaller and muted
Nothing in the layout sets or reads data-meta-rank, so a compact container does not hide the non-lead values (BUG-023)
The theme-authoring docs list lead beside bar and definition-list
The CSS coverage test passes and contracts are regenerated on both copies

References

SPEC-161: D6.