Payload Components

Copying a Payload block into a project is the easy part. Making it live means registering it in the Pages collection, mapping it in RenderBlocks, regenerating Payload’s types and updating the admin import map, four edits that get forgotten, half-done, or repeated across every repo. Payload Components does all five artifacts in one pass, so npx payload-components add hero-basic lands source files plus two scoped patches and two regenerated outputs as a single reviewable git diff.

The catalogue runs to 82 components across heroes, features, pricing, comparators, testimonials, stats, FAQs, footers and more, each rendered live on the site rather than shown as a screenshot, so you can see what you’re installing before you run anything. Every component page documents its fields, files and patches up front, and a dry-run flag prints exactly what would change without touching the repo. Installs record their own state, so running the same command twice converges rather than duplicating, and partial installs stay visible instead of silently breaking.

The whole thing is MIT, the registry, the CLI, the components and the site are one repository, with no license key, no gated tier and no paid roadmap. What you install is plain source you own and can edit, not a locked runtime dependency, which is the argument for reviewing the installer before trusting it. Scope is deliberately narrow: Payload v3 with Next.js 15 or 16, structured like the official website starter, and the CLI checks your project against a published support matrix before it writes anything.