Pipelines

The Pipelines app moves content through a one-way chain of stages inside a single space. Content stays editable in the Preview stage, and every stage after it is frozen, so what a team reviews is what deploys. Each stage has its own access token, which the matching frontend environment uses.

A space has one pipeline with at least two stages. Stories keep their UUID across stages.

Features

• Define the stages content passes through.
• Edit content in Preview and freeze it in every later stage.
• Give each stage its own preview URL for the Visual Editor.
• Set the stage each stage syncs from.
• Issue an access token per stage.
• Deploy content from the source stage through the context menu in the Content section.
• Coordinate a deployment with the Releases app.

Setup

1. Open Settings → Pipelines, enter a name for each stage, and add it.
2. For each stage, set an optional preview URL and the stage it syncs from.
3. Generate the access token of each stage under Settings → Access Tokens.

To deploy, select the target stage in the Content section and choose Deploy from source. Repeat the deployment whenever the source stage changes.

Further resources

Pipelines in the app directory