Ship the change. Skip the ticket.
P1 lets marketers and editors build and update pages directly, using components your team has already approved. You move at campaign speed. The brand, accessibility, and review rules come with you.
The problem
A page change shouldn't take weeks.
A headline fix waits behind a redesign. A campaign needs ten pages and a developer's calendar. A launch goes live, and someone spots an off-brand layout the next morning. The work is simple. The process around it isn't.
What P1 unlocks for you
Edit right on the page.
Click the headline, change it, and see the page as visitors will. No admin forms, no handoff, no waiting for a developer to make the edit.

Build from approved parts.
Add components from your brand library. Choose something outside your palette and P1 brings it back in line. You get the freedom to build, and the system keeps it on brand.

Or, vibe code it with Zappy.
Zappy, Pantheon's AI agent, drafts campaign pages from your brief using your approved components. You review the first pass, refine it, and decide what goes forward. People stay in control of consequential changes.

Developers set the system. You work inside it.
Your developers define the components, fields, and rules. That is what makes it safe to give marketers and editors more control. You are not editing code, and you are not working around your team. You are working on top of what they built.
The site is easier to work with—just drag, drop and configure a component. However, we're able to do that and stay on brand.
Work in a safe copy of the live site.
Open a campaign workspace, make changes freely, and compare them with the live site. Several campaigns can move at once without stepping on each other, and nothing reaches the live site until you merge it.

Review, publish, and undo.
Every change is visible, attributable, and reviewable. Move from brief to approval to release in one workflow, and roll back a change if something goes wrong — confirm rollback details with Product.

How a campaign moves through P1
From brief to live in four steps.
Brief.
Describe the campaign, or hand it to Zappy.
Build.
Create pages in a protected workspace using approved components.
Review.
Compare your changes with the live site and route them for approval.
Publish.
Merge to live when everything looks right.
Governance is not optional.
If an inaccessible page, an off-brand launch, or an unapproved claim would cause real consequences, governance is not optional. P1 checks contrast, alt text, and rich-text safety before anything publishes, and keeps a clear record of who changed what.
Strong-fit signals
The people closest to the content can build and update within the boundaries we establish to avoid brand drift.
Questions marketers ask first.
Do I need to know code?
No. You edit on the page and build with ready-made components. Developers create and maintain the components.
Can I break the brand?
You can only use the components and fields your team has approved, and pre-publish checks flag issues such as low contrast and missing alt text before anything goes live.
Will Zappy publish on its own?
No. Zappy drafts, and a person reviews and executes any change. Agents work on a content branch, not directly on the live site.
Who approves changes?
Your team decides. Consequential changes go through review before they reach the live site.
Can I work on several campaigns at once?
Yes. Each campaign gets its own protected workspace, so work moves in parallel.
Is it available now?
P1 is in paid beta. Request early access and the team will review your request and reach out to selected teams to discuss fit, scope, and timing.
Bring a real campaign. See how fast it moves.
Request early access and the P1 team will review your request.