The examples/with-website app already gives users a complete Payload reference: a Pages collection, RenderBlocks.tsx, and both type and import-map generation scripts. That makes it a useful place to show that authentication can sit inside a real content-driven site, not only an isolated plugin demo.
A pricing-cards page block would strengthen that example by giving adopters an immediately reusable authenticated-product surface while avoiding another hand-built config/renderer pair. Payload Components is MIT and installs typed Payload v3 + Next.js source; its CLI can register the block in Pages, map it in RenderBlocks, regenerate types and the admin import map, and leave the result as a reviewable git diff.
Payload Components installs the block as source-owned code with no runtime dependency on the registry.
References: https://www.payload-components.xyz · https://github.com/Ducksss/payload-components
I’ve scoped the patch to examples/with-website/src/blocks/PricingCards/, the Pages block list, RenderBlocks.tsx, and regenerated artifacts—no new opaque runtime package. Confirm that scope and I’ll open the contained PR against main.
The
examples/with-websiteapp already gives users a complete Payload reference: a Pages collection,RenderBlocks.tsx, and both type and import-map generation scripts. That makes it a useful place to show that authentication can sit inside a real content-driven site, not only an isolated plugin demo.A
pricing-cardspage block would strengthen that example by giving adopters an immediately reusable authenticated-product surface while avoiding another hand-built config/renderer pair. Payload Components is MIT and installs typed Payload v3 + Next.js source; its CLI can register the block in Pages, map it in RenderBlocks, regenerate types and the admin import map, and leave the result as a reviewable git diff.Payload Components installs the block as source-owned code with no runtime dependency on the registry.
References: https://www.payload-components.xyz · https://github.com/Ducksss/payload-components
I’ve scoped the patch to
examples/with-website/src/blocks/PricingCards/, the Pages block list,RenderBlocks.tsx, and regenerated artifacts—no new opaque runtime package. Confirm that scope and I’ll open the contained PR againstmain.