Documentation
Request access

Build on Pantheon P1 as a developer

Set up a site, build the blocks your team uses, and connect P1 to your stack.

Start a new projectAdd to an existing app

Set up

Get a P1 site running, deploy it to Pantheon, and bring your team in.

Migrate to P1

Bring an existing WordPress or Drupal site, or move a site between P1 accounts.

Build components

Your components become the blocks editors build pages with. Fields decide what they can change.

Model content

Give pages a shape: templates, content types, and content pulled from other sources.

Who does what

You
Set up the site, build blocks, and decide what editors can change. Code ships through Git.
Your editors
Build and publish pages with your blocks. Content ships through workstreams.
Editor docs
Your administrators
Create sites, issue tokens and keys, and choose who can do what.
Administrator docs

Maintain

Keep your site current as P1 ships new releases.

Configure your site

Wire up the site-wide features editors rely on.

APIs

Read and write P1 content from your own code.