Show and tell: Payload Components, wired block installs for Payload v3 + Next.js

[Ducksss]

Hi Payload community — I built Payload Components, an MIT registry + CLI for installing reusable Payload v3 + Next.js blocks wired, not pasted.

Repo: https://github.com/Ducksss/payload-components
Docs/catalog: https://www.payload-components.xyz

The problem it solves: a shadcn registry can copy block files, but a Payload block is not usable until it is registered in the Pages collection, mapped in RenderBlocks, regenerated into payload-types.ts, and added to the admin import map. payload-components add <block> wraps that whole install into one reviewable git diff.

Current shape:

• 38 installable page blocks
• Payload v3 + Next.js 15/16 starter-shaped projects
• shadcn-compatible public registry at /r/registry.json
• install state, recovery checks, and a doctor command
• open-source / MIT / no paid tier

This is intentionally not a Payload plugin, so I am not trying to present it as one. It is closer to a block registry plus installer for common website surfaces.

Clear ask: does this belong in any existing Payload ecosystem resource/channel, or is “community project / awesome list / Discord showcase” the right path for now? I’d also appreciate feedback on the install contract before wider launch.