Sample post for reference fields
Used by the all-fields showcase to demonstrate the post-object and relationship controls.
Learn moreReal sites running typed-field Gutenberg blocks rendered through a React frontend. Same component in the editor and on the live page.
Frontend engineers and editors talking about the editor-frontend parity story and the typed-field workflow.
“The typed field system is what hooked me. We declare an Inspector control in JSON and the React frontend reads it back via REST as a real number, a real URL object, not a stringly-typed mess.”
“My editors author in Gutenberg, our frontend is Next.js. Before GCB those were two codebases that drifted. Now they're one component, and the team finally trusts the preview.”
“Editor preview and the live site are the same React component. The bug-spotting loop collapsed from hours to seconds — we ship a block, our editors see exactly what readers will see.”

Marketing sites, SaaS dashboards, editorial publications — all rendering from the same typed Gutenberg blocks.

WordPress as a typed-field CMS for a React frontend. One component renders both the editor preview and the public site u2014 no edit.js to maintain in parallel with your real frontend.
nAuthor rich content in the block editor you already know. Ship it to a Next.js / Astro / Remix frontend without rebuilding any of it.
Five reasons developers and editors actually agree.
Tips, patterns, and release notes from the team building GCB and the headless Gutenberg stack around it.
Used by the all-fields showcase to demonstrate the post-object and relationship controls.
Learn moreWelcome to WordPress. This is your first post. Edit or delete it, then start writing!
Learn more












