Deploying changes to content and configuration between spaces is a common task that developers need to undertake in the lifetime of a project.
There are three types of changes to a Contentful space:
Each type of change has a method best suited to it and this guide will outline each one in detail.
If you want to follow along with the examples in this guide, then create a space with the 'product catalog' example content.
Deploying content changes requires using 1 editorial space managed by users with editorial roles, the Content Delivery API (CDA) and Content Preview API (CPA).
This method suits cases when you want to test how content changes will look when published, or experiment with how content will look on different delivery platforms you are testing.
Invite your collaborators to the editorial space, assigning them an appropriate role that doesn't allow them to publish content. In this screenshot, the invitee is an 'author', which means they can create content, but can't publish it.
If that new user creates or edits an item of content, these changes will stay in a draft state until a user with the appropriate editorial role publishes them.
For easy access you can use the Draft views shortcut.
Users with roles with appropriate permissions can now approve the changes, publish the entry and make it available to the Content delivery API.
The CPA works in a similar way to the CDA, but it returns the draft state of entries whenever available. So, assuming that another user did create a new post, then this API call:
1 2 3
curl -X GET -H "Content-Type: application/vnd.contentful.management.v1+json" "https://preview.contentful.com/spaces/<space-id>/entries?access_token=<content-delivery-api-key>"
Will return the 9 total entries present in the default example space, plus the new entry in a draft state.
Using Contentful's Snapshot feature, editors can revert entries to previous states and undo changes made by other contributors.
At this stage you should handle any inconsistencies or intentional changes that emerge between content changes before deploying them. This includes changing content type IDs, fixing broken references between entries and other bulk updates needed to content or configuration.
To enhance the editorial experience you can use webhooks to notify external systems, for example, when a contributor submits a draft entry, notify the editorial team via Slack to review it.
This method suits cases where users and developers want to experiment with changes to content structure or configuration.
The Contentful import and export tools offer a great way to export (most) of the data and structure from one space and import it into another.
There are limitations to the tools:
The Contentful export tool is a command line tool that helps you export the contents of a space.
Start by exporting the content of the current space:
1 2 3
contentful-export --space-id <space-id> --management-token <content-management-token>
You can see the results of the export of the test space here, it follows the typical return pattern of API calls.
As the space data is now a JSON text file, you can commit it to version control as a backup.
Create a new space with the Contentful web app or the API and note it's ID. Now use the Contentful import tool to import the JSON file into your new space.
1 2 3 4
contentful-import \ --space-id spaceID \ --management-token managementToken \ --content-file exported-file.json \
And now you should see the copied content in your new space.
But as noted above, if you switch to the Users and Roles section under Settings, you will see that none of this content has copied over.
The main issue with this approach is the constant switching of space IDs in your applications. Our recommended solutions for this are using a configuration or production space.
You can use an independent space to maintain a list of your spaces and their current IDs, with all apps served content via this space. You can then query this space to get the ID you need without needing to change your apps each time. You could also use this space for storing other configuration options for build and deployment processes. Below are screenshots to give you an idea, but you will likely want to create content types and entries that suit your specific use case.
At this point you have the original space, a cloned space, and a configuration space. Update the configuration space to direct production apps to the cloned space. You can now make changes to the configuration and content types in the original production space, using the options outlined above to preview the changes. When complete, use the configuration space to switch QA apps to the original production space and test the new changes. If this is successful, then you can switch all apps back to the production space and delete the cloned space. If the process fails at any point, then you can use contentful-import to rollback the production space to it's original state.