Prismic MCP is now in the Claude and ChatGPT plugin stores. Connect to create and edit pages with your preferred AI.Install it now
Environments

Test content model changes in a staging environment

Clone your production repository, try new page types and slices on copies of your real pages, and push them live once they work. Your production website stays untouched while you test.

Page Builder preview of the Verdello homepage with the environment menu open and Staging selected

Test model changes against real content

An environment is a copy of your production repository, with its page types, slices, custom types, pages, and media files. Change your models there without touching what your visitors see.

  • Create an environment from your repository settings

  • Test new slices and fields on copies of your pages

  • Resync from production at the start of each development cycle

Environments settings with Production and Staging, a Resync button, and a preview of the Verdello flavours section on the staging site

Switch environments from the Prismic CLI

Set an active environment and the Prismic CLI points your model pulls and pushes at it. Your local website fetches that environment’s content, and production keeps using your production repository.

  • Select an environment with one CLI command

  • Pull, change, and push your models in that environment

  • Switch back to production and push the tested changes

Terminal setting the Prismic CLI to the verdello-staging environment and pushing model changes, next to the changed slices and page type

Test your next model change in staging

Talk to our team about adding environments to your Prismic plan.

Questions about environments

Features that work alongside environments