Workflows

The dashboard UI talks about “workstreams” and a “Live” site. Underneath, P1 runs on a real branch/version/checkpoint model, closer to Git than to WordPress’s post-status system. This section documents that model directly from @pantheon-systems/css-client’s API surface (the actual HTTP client the SDK is built on), not just from what’s visible in the dashboard.

Everything in this section was verified by reading the installed @pantheon-systems/css-client and @pantheon-systems/puck-css source directly: endpoint method signatures, the editor’s publish flow, the template migration API. It’s more reliable than what we could infer from the dashboard UI alone, and it’s how we resolved a rendering mystery documented in Known Issues.

The hierarchy


Site
└── Branch  ("main" is the default; the dashboard calls a non-main branch a "Workstream")
    └── Document  (a page, template, or redirect, identified by path + ID)
        └── Version  (every save creates one, like a Git commit or a WP revision)

Checkpoint  (a named snapshot of a branch, what "Publish" actually creates)

What’s on each page

Branches: workstreams as branches, merging a workstream into main, and the merge-request review flow.
Publishing: draft autosave vs. the explicit Publish step, branch-wide checkpoints and rollback, and soft-deleting a document.
Templates: Templates as content types, self-serve schema migration, whether a template’s layout can be defined in code, and dynamic (templated) routes.