Documentation
Page blocksPricing

Pricing Cards

A three-up pricing table of editable plan cards with one plan highlighted in emerald — the base of the Pricing family.

v0.1.0Page blockPricing familyPricing section
import type { Block } from 'payload'import { planFields, pricingFields } from '@/blocks/shared/pricingFields'export const PricingCards: Block = {  slug: 'pricingCards',  interfaceName: 'PricingCardsBlock',  fields: [    // Shared pricing heading (eyebrow, title, description). Variant-specific    // fields follow; edit the shared shape in @/blocks/shared/pricingFields.    ...pricingFields,    {      name: 'plans',      type: 'array',      required: true,      minRows: 2,      maxRows: 4,      admin: {        initCollapsed: true,      },      fields: planFields,    },  ],  labels: {    plural: 'Pricing Cards Blocks',    singular: 'Pricing Cards',  },}

Installation

npx payload-components add pricing-cards

Copy the files straight from the registry, then wire the Payload fragments by hand:

pnpm dlx shadcn@latest add https://www.payload-components.xyz/r/pricing-cards.json

What it installs

Copies 3 source files into your project:

  • src/blocks/shared/pricingFields.tsshared
  • src/blocks/PricingCards/config.ts
  • src/blocks/PricingCards/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
pricingFields.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 three fields come from the shared pricingFields base; plans is built from the shared planFields and is specific to this variant. Mark one plan featured to highlight it in emerald.

Prop

Type

Each item in plans carries:

Prop

Type

Usage

Add the block to a page. In the Payload admin, open (or create) a Page and add the PricingCards 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
v3
Next.js
15 / 16
shadcn UI
badge, card

Your project must already expose components.json, src/payload.config.ts, src/blocks/RenderBlocks.tsx, src/collections/Pages/index.ts — the surfaces payload-components add patches. The CLI verifies this against the support matrix before touching anything.

In this family


Layout adapted from tailark/blocks (MIT), retokenized onto the Payload Components design system.