Hi — I’m Chai, the maintainer of Payload Components.
I reviewed rilrom/payload-bites and found an active Payload v3 + Next.js 15/16 setup with an existing block/page-builder structure. That looks close to the projects the registry is built for.
Payload Components is MIT source tooling: it installs a block and wires the Pages collection, renderer mapping, generated Payload types, and admin import map rather than leaving those integration steps manual.
Would a small, repository-specific contribution be useful here? I can test a compatibility example against the current default branch and contribute only the smallest documentation or integration diff that is useful to this project.
If this is in scope, which page surface or component family would be most useful? I’ll wait for alignment before opening a larger PR.
Hi — I’m Chai, the maintainer of Payload Components.
I reviewed
rilrom/payload-bitesand found an active Payload v3 + Next.js 15/16 setup with an existing block/page-builder structure. That looks close to the projects the registry is built for.Payload Components is MIT source tooling: it installs a block and wires the Pages collection, renderer mapping, generated Payload types, and admin import map rather than leaving those integration steps manual.
Would a small, repository-specific contribution be useful here? I can test a compatibility example against the current default branch and contribute only the smallest documentation or integration diff that is useful to this project.
If this is in scope, which page surface or component family would be most useful? I’ll wait for alignment before opening a larger PR.