Versioning of content

The Contentor platform supports versioning of content where we keep track of only work on what has changed between two content requests.

Versioning is done by sending updates to previously sent content requests and when fulfilling the request Contentor will see the changes made between the update and its previous version.

Implementing

Our ready-made integrations support versioning out of the box and can be configured to either use versioning or to send full requests.

In the HTTP API you will need to keep track of identifier of the last sent content request for a product, page, or entity. For an update send all of the content as usual but mark the type and link to previous version as described in format of content requests.

It is not possible to add on new fields in an update. All fields should match the previous content request.

Versioning requests are meant to be small, incremental updates to previously translated content requests. Any request that requires big changes should be sent in as a new content request instead.