Skip to content
Documentation
Page blocksHero

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.

v0.1.0Page blockHero familySplit hero

Installation

npx payload-components add hero-split

What it installs

Copies 3 source files into your project:

  • src/blocks/shared/heroFields.tsshared
  • src/blocks/HeroSplit/config.ts
  • src/blocks/HeroSplit/Component.tsx

…and makes 4 edits to wire the block into your project:

Registers the blocksrc/collections/Pages/index.ts
Maps the renderersrc/blocks/RenderBlocks.tsx
Regenerates typessrc/payload-types.ts
Regenerates the admin import mapsrc/app/(payload)/admin/importMap.js
heroFields.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

Add the block to a page. In the Payload admin, open (or create) a Page and add the HeroSplit block to its layout.
Fill the content. Complete the fields from the content model above — the component ships sample content you can start from.
Publish. Save and publish the page; the block renders through 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