Payload Components contribution idea for dflow

[Ducksss]

Hi — I’m Chai, the maintainer of Payload Components.

I reviewed dflow-sh/dflow and found an active Payload v3 + Next.js 15/16 setup with a component-driven frontend, shadcn-compatible UI signals. 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 one appropriate component against this repository and propose the smallest useful integration diff.

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.

[pavanbhaskardev]

Hi @Ducksss 👋,

Thanks for raising issue, as per my understanding you're trying to integrate payload-components to dflow repository. Which's great!

But this is dflow application repository, It doesn't have any marketing-pages code.