Footer Centered
A centred brand, tagline, and navigation above a rule carrying copyright and policy links.
v0.2.0Page blockpayload-website-starter
import type { Block } from 'payload'
import { footerFields, footerLinkFields } from '@/blocks/shared/footerFields'
export const FooterCentered: Block = {
slug: 'footerCentered',
// Existing apps must migrate stored data before adopting this identifier:
// https://www.payload-components.xyz/docs/registry#installed-source-and-migrationsInstallation
npx payload-components add footer-centerednpx shadcn@latest add https://www.payload-components.xyz/r/footer-centered.jsonThe registry copy brings the source files only; register the block and map its renderer yourself, or let the CLI command above do both.
Usage
Editors add Footer Centered from a Page layout's block picker. This is the form they fill.
Footer Centered
Block- Brand Label
- Acme
- Tagline
- One governed metric layer for every team in the company.
- Copyright
- © Acme 2026
- Links
- FeaturesPricingAboutBlogContact
- Legal Links
- 01Privacy policy/privacy
- 02Terms of service/terms
- 03Cookies/cookies
- 01
- 1Add the block to a Page from the layout block picker.
- 2Fill the fields as above.
- 3Publish. RenderBlocks renders the block, fully typed.
Footer blocks render inside the Pages layout like every other block. To use one as site-wide chrome instead, render the component directly in your root layout and pass it content from a global.
Content model
logo, brandLabel, and copyright come from the shared footerFields base that every Footer
variant spreads; tagline, links, and legalLinks are specific to this variant. legalLinks is
optional — leave it empty and the bottom rule carries the copyright alone.
Prop
Type
Each item in links and legalLinks carries:
Prop
Type
What it installs
Composition
How the block hangs together in Payload
Pageslayout[]FooterCenteredbrandLabeltaglinecopyrightlinks[] linklegalLinks[]labelhref
- Fields
src/blocks/FooterCentered/config.ts- Render
src/blocks/FooterCentered/Component.tsx
Files
Copies 5 files into your project. Files tagged shared are reused across the family.
Edits
Wires FooterCentered into the project in 4 places.
| Registers the block | src/collections/Pages/index.ts |
| Maps the renderer | src/blocks/RenderBlocks.tsx |
| Regenerates types | src/payload-types.ts |
| Regenerates the admin import map | src/app/(payload)/admin/importMap.js |
- Registers the block
src/collections/Pages/index.ts - Maps the renderer
src/blocks/RenderBlocks.tsx - Regenerates types
src/payload-types.ts - Regenerates the admin import map
src/app/(payload)/admin/importMap.js
safeUrls.ts and footerUrls.ts and footerFields.ts are shared source for this component family. Components that install the same path reuse your local copy, and re-running an install never overwrites a copy you have changed.Re-running the install detects existing source and wiring, then records install state in .payload-components/state.json.
Requirements
- Target
- payload-website-starter, payload-blocks-app
- Payload
- v3 (3.25 or newer) / v4 (experimental)
- Next.js
- 15 / 16 with v316 (16.4 or newer) with v4
- shadcn UI
- None
Payload v4 support is experimental: it needs Next.js 16 (16.4 or newer) and Node.js 24.22.1 or newer. Payload v3 (3.25 or newer) stays fully supported.
Your project must already expose components.json, src/payload.config.ts, the surfaces patched by payload-components add. The CLI verifies this against the support matrix before touching anything.
Layout adapted from tailark/blocks (MIT), retokenized onto the Payload Components design system.