For experience pages, make sure that a cms user working on the experience page in the Channel Manager can manually trigger the creation of a new version. Thus NOT on every change in the preview (as opposed to CMS-13199). The reason is that if for example component parameters are changed or a new item is dragged on the page, this results in a preview change, but in general a user does not directly want a new version. This should be a manual step via a button (or something else....). Note that every change to the layout though does require a audit log

Implementation Detail:

To

o.o.c.channelmanager.content.workflows.WorkflowServiceImpl#executeDocumentWorkflowAction

add support for versioning (via the repository document workflow) the current version (branchId) in the Channel Manager if the currently rendered page is not from version history (if so, adding a new version does not add anything)

Note that

1. If the CM is rendering a versioned document from version history, the 'create version' option must be disabled : The FRONTEND should disable versioning then since there is nothing new to version (for that branch). jdegooijer if you want we can include in the html page comment whether or not the rendered primary document is from version history or not with a boolean, does that help you?
2. If another user started editing the document in content editor, then a user in the CM clicking 'create version' should get an error : Addition: this is not per se a requirement: if a user wishes to version, so be it if that is possible in the UI
3. If another workspace document has become for a different branchId than currently looked at in the CM, the 'create version' should fail : Addition : This is not true, since a version is always created of a specific branch