Install

Two packages, installed into a Payload 3 site on Next.js. Neither depends on next, and neither ships a page: the site owns its routes, its page measure and its image and link elements.

pnpm

pnpm add @bison-lab/payload-blocks @bison-lab/payload-core @bison-lab/ui @payloadcms/plugin-seo

npm

npm install @bison-lab/payload-blocks @bison-lab/payload-core @bison-lab/ui @payloadcms/plugin-seo

Peers

Package	Required	Optional, by entry
@bison-lab/payload-blocks	payload	react, react-dom, @bison-lab/ui for ./react; @payloadcms/richtext-lexical for ./rich-text; @payloadcms/ui for ./admin (every Payload site already has it)
@bison-lab/payload-core	payload, @payloadcms/plugin-seo	none

Pin @payloadcms/plugin-seo and @payloadcms/richtext-lexical to the same version as payload. Payload releases them in lockstep.

@bison-lab/ui needs the library’s tokens and Tailwind preset on the page. If the site already renders @bison-lab/ui components it has them; if not, the component library README covers the theme file and the preset import.

What each package is for

• @bison-lab/payload-blocks puts the marketing sections behind the CMS. A Payload Block config per section, a renderer per config, and RenderBlocks to place them. See Wire a site.
• @bison-lab/payload-core is the site-agnostic Payload configuration: today the SEO tab and the metadata reader a page route calls.

Next: Wire a site.