Hey Product Hunt - I built Payload Components because every Payload project repeats the same block setup. Copying a component is only the first step. Making it usable means registering the block in the Pages collection, mapping the frontend renderer, regenerating Payload types, and updating the admin import map. Payload Components wraps a shadcn-compatible registry with Payload-specific wiring, so: npx payload-components add hero-basic lands a working block as a normal git diff. It is MIT and community-first: no pricing tiers, no license keys, no gated component catalog. The current alpha has 38 installable page blocks for Payload v3 + Next.js 15/16 projects shaped like the official website starter. I would love feedback from Payload and Next.js teams on two things: 1. Which repeated blocks should be added next? 2. Which Payload repo shapes should the installer support after website-starter? Repo: https://github.com/Ducksss/paylo... Docs: https://www.payload-components.x...

Payload Components

Payload CMS blocks installed wired, not pasted

Payload CMS blocks installed wired, not pasted