Workflow for releasing documentation

Gerben Wierda

I have the following use case.

1. There is a documentation that is the current valid version
2. People need to work on an update, as long as the update is being worked on, the old one is the valid one
3. At some point, the new one is accepted and should replace the old one
4. The creation and acceptance process require that a large number of people have access to the draft and can comment on it

I have looked at collaborative editing, but only editors can see the proposed changes and there is a maximum of 12 editors for a page if I understand the documentation correctly, which is not enough by far.

I have been looking at cloning the documentation to a new version and working one that, publishing the clone for review purposes, but links to the old one should survive when the new version is accepted (we do not want broken links).

Is there a way to do this?

Dominic Lagger

Hi @Gerben Wierda 

Do I understand it correct: On the new version, only the editors should have access, not everyone? 

In your case, I think the best way would be to copy the old version and edit the copy. When it's released, delete or move the old version to an archiv page tree.

Perhaps an app could be a solution. We use scroll versions. There, you can edit a page in multiple versions. But you can't restrict the versions itself (I think, I'm not sure)

I hope I could help or give a little hint. 

Regards, Dominic