Pantheon P1 agency.
Websites your team can change without breaking.
We design and build P1 sites and the component systems that keep every page on brand. We spoke at Pantheon’s /GoLive 2026, and we are P1 Charter Partners.
What We Build
Four parts of a site that stays yours.
A governed system works when the components are right. We start there, with the blocks, the fields and the rules, and build the site on top.
The same team that designs the components builds the site and stays on after launch.
P1 component systems
The blocks your team builds every page from.
- Puck blocks with typed fields, sensible defaults and instructions for AI agents
- Brand rules built into the components, so pages stay on brand
- Accessible markup in every block, built to WCAG 2.2 AA
P1 site builds and migrations
A governed site on the Pantheon Platform.
- Content models and data sources shaped around your organization
- Next.js and React front ends on the P1 SDKs
- Content written in Google Docs or Word brought in through Pantheon Content Publisher
- Migration planning for the pages that should move first
P1 editor experience and governance
How your team builds pages in P1, day to day.
- An approved set of components and fields that editors and AI agents both build from
- Editor workflows in protected workstreams that merge into the live site
- Pre-publish checks for contrast, alt text and rich text on every page
Support after launch
A governed site still needs people who know it.
- New blocks as your pages call for them
- Training for the editors who will use the system
- Fixes and enhancements as P1 itself matures
What P1 is
A governed way to build the web.
P1 is Pantheon’s AI-native web composition layer, built on the Pantheon Platform. Marketers, developers and AI agents build pages from the same React components, in protected workstreams, with checks before anything goes live. It is in a limited beta.
P1 is not Pantheon Content Publisher. Content Publisher turns Google Docs and Word files into site content, and P1 brings it in as one part of a larger system for creating and governing the site itself.
Pantheon describes P1 as an AI harness for website creation and governance. Read Pantheon’s own account at p1.pantheon.io (opens in a new tab).
P1 Blocks
We built the parts library we wanted.
P1 Blocks is our library for P1. Every block comes as a Puck block for P1 projects and as a plain React and Tailwind component you can copy. A live editor lets you try them, and an llms.txt file lets coding agents install them.
It includes industry sets, dashboard widgets and WebGPU effects, with a CSS fallback. It is the clearest proof we can offer of how we think about components.
- Blocks
- 297
- Categories
- 23
- Editions: Puck and React with Tailwind
- 2
Charter Partner
Building on P1 from the start.
P1 Charter Partners
We are P1 Charter Partners, in Pantheon’s Charter Partner Program, the group of agencies building on P1 before it is generally available.
/GoLive 2026
We spoke at Pantheon’s /GoLive 2026 conference in Miami, October 6 and 7, where Pantheon introduced P1.
Pantheon partner
We are an accepted Pantheon partner.
How It Works
From first block to a site that holds.
Discover
We learn your organization, your editors and the pages that change most, then decide whether P1 fits and where.
Model the components
We define the blocks, fields and brand rules, so every page starts from parts that already belong together.
Build and migrate
We build the front end and move the content across, testing with assistive technology as we go.
Govern and support
We train your team, watch how the system is used, and add blocks as the site grows.
P1 checks contrast and alt text before a page publishes. We build the components to WCAG 2.2 AA, so those checks start from a sound base. See our accessibility services.
Questions
Pantheon and P1, answered.
P1 is Pantheon’s AI-native web composition layer, built on the Pantheon Platform. Marketers, developers and AI agents build pages from the same governed React components, in protected workstreams, with checks before anything goes live. Pantheon introduced it at its /GoLive conference in October 2026.
No. Content Publisher publishes content written in Google Docs or Microsoft Word to a website. P1 is a broader layer for creating and governing the site itself, and it brings Content Publisher in as one part of the whole.
Yes. We are an accepted Pantheon partner, and we are P1 Charter Partners, in Pantheon’s Charter Partner Program. We also spoke at Pantheon’s /GoLive 2026 conference in Miami.
It is Pantheon’s program for the first agencies building on P1. Pantheon describes it as training before general availability, early builds, and structured feedback from the agencies doing the work.
P1 is in a limited beta, and Pantheon reviews each application. Pantheon says participants pay their hosting and site fees plus a separate P1 fee. We can help you decide whether it fits and handle the build.
The front end is Next.js with React. Blocks are React components with typed fields, built on the Puck editor, and AI agents connect over MCP. Publishing updates the live page without a new deploy.
P1 Blocks is our library of 297 blocks in 23 categories, made for P1. Each block comes as a Puck block for P1 projects and as a plain React and Tailwind component. There is a live editor to try them, and an llms.txt file so coding agents can install them.
How a project runs
It’s a loop,
not a line.
After launch we measure, learn and start again.
We don’t launch and disappear.
- Discovery
- Design
- Development
- Delivery
Launch is the start.
Thinking about
P1?
Tell us about your site and your team. We’ll say whether P1 fits, and what the first build should be.