Context
post-hero is listed in src/lib/site.ts as an upcoming post component. It is the post header surface: title, summary, date, category, author, and optional image.
This should be shadcn-native/file-only. It should not patch Pages or RenderBlocks.
Scope
Add post-hero as an installable post component.
Suggested props/content shape
titledescription or excerptpublishedAtcategoriesauthor- optional
image
- optional
backHref only if it stays simple
Acceptance
- Registry item exists for
post-hero and installs files under consumer ~/src/... paths.
- No Payload page-block fragments are added.
- Docs describe this as a post surface, not a page block.
- Catalog metadata moves
post-hero from upcoming to installable only after the install path works.
- Tests prove registry build/check and direct shadcn delivery for the component.
Out of scope
- Table of contents.
- Share buttons.
- Related posts.
Context
post-herois listed insrc/lib/site.tsas an upcoming post component. It is the post header surface: title, summary, date, category, author, and optional image.This should be shadcn-native/file-only. It should not patch Pages or
RenderBlocks.Scope
Add
post-heroas an installable post component.Suggested props/content shape
titledescriptionorexcerptpublishedAtcategoriesauthorimagebackHrefonly if it stays simpleAcceptance
post-heroand installs files under consumer~/src/...paths.post-herofrom upcoming to installable only after the install path works.Out of scope