Concept for managing future versions of pages with release mechanism.
The Wiki itself has no workflow mechanism for release mechanism for new page versions.
A wiki page, which will be safed, instantly will be visible.
For new pages the editor can give the page an private right, so the page will not be visible until finished.
The worflow concept uses mechanism and processes from version control systems like CVS or SVN.
Before starting an workflow the editor has to decide to create a new branch, select an existant branch or edit the page in the head, so after save the page it will be visible immediatelly.
The branch will have a short name and a description and a right required to view and to edit the branch.
Inside the wiki a new branch will be started and will only be visible for people, which has the rights for this branch.
The branch is visible including all existant pages - modified inside the branch or not.
The branch can be reviewed and edited. Automatically if an existant page will be modified, a copy will be created inside the branch.
After creating the branch, it will be reviewed.
Each element inside the branch may be reviewed. The review itself will be stored in the properties of the element (who, when, version).
After review the branch has to be planed for going life.
A branch may have a time stamp, when brach should be merged into the head.
Branch description is a special element type holds information.
Create Branch with name and rights.
List of all items modified inside the branch.
/dir/File: Original file
/_branches/branchname/dir/File: Version of the file in Branch
/_branches/branchname/BranchDescription: Meta information about the branch
Alternativelly branches are outside the known file system, because this is only secure way not be confused branches and head.