Hero Split
A two-column hero — shared hero copy on one side, an editor-managed visual on the other, with the side chosen per block.
Installation
npx payload-components add hero-splitWhat it installs
Copies 3 source files into your project:
src/blocks/shared/heroFields.tssharedsrc/blocks/HeroSplit/config.tssrc/blocks/HeroSplit/Component.tsx
…and makes 4 edits to wire the block into your project:
| Registers the block | src/collections/Pages/index.ts |
| Maps the renderer | src/blocks/RenderBlocks.tsx |
| Regenerates types | src/payload-types.ts |
| Regenerates the admin import map | src/app/(payload)/admin/importMap.js |
src/collections/Pages/index.tssrc/blocks/RenderBlocks.tsxsrc/payload-types.tssrc/app/(payload)/admin/importMap.jsheroFields.ts is the shared field core for this family — every variant composes it. Editing it updates each installed block at once, and re-running an install never overwrites a copy you have changed.Re-running the install converges: it detects existing wiring, skips it, and records install state in .payload-components/state.json.
Content model
The first four fields come from the shared heroFields base. image, imagePosition, and
highlights are specific to this variant.
Prop
Type
imagePosition is a field rather than a second component, because alternating sides down a
page is a layout decision an editor makes per block — not a different kind of hero. On small
screens the visual always leads, since a stacked hero that opens with prose pushes the image
below the fold for no gain.
Usage
HeroSplit block to its layout.RenderBlocks on the frontend, fully typed — no extra wiring.Requirements
- Target
- payload-website-starter, payload-blocks-app
- Payload
- v3
- Next.js
- 15 / 16
- shadcn UI
- badge
Your project must already expose components.json, src/payload.config.ts — the surfaces payload-components add patches. The CLI verifies this against the support matrix before touching anything.
In this family
hero-basichero-splitcurrenthero-videohero-product-tilthero-aurorahero-kinetic