Creighton Students
Manual Home  >  Typo3 assistance  >  Workspaces
Document Life Cycle - Versioning & Workspaces


Typo3, document lifecycle, the way they envisioned.


The versioning/workspaces of Typo3 was set up to encourage a workflow process as seen in the image to the left.  

This process utilizes  2 to 3 groups of people:

  1. the user/ editor (s) who creates new content/page in the draft or custom workspace OR changes existing content/page(s) in  a new version of the old.
  2. the reviewer (s) who proof reads the new content/page and approves it for publishing
  3. the owner (s) who publishes the new content/page

 Numbers 2 & 3 could be the same person.

This is done in a custom workspace specifically set up for that site or subsite and for those specific groups, the users, the reviewers and the owners.

Creighton flavored Versioning and Workspaces

When workspaces/versioning was introduced into Typo3, the documentation just wasn't available, at least in English.  So Creighton didn't adopt this work process.  Even now I can find only general documentation, there are lots of features that I can't find covered, or at least covered in any depth. 

As illustrated above the concept is easy enough.   Even the idea of a "Live" and "Draft" workarea is easily understandable. However, I believe, in an effort to make the versioning/workspaces flexible and comprehensive, the execution of these modules became complex and a difficult to understand.  That lead to a lot of fumbling on my part to make all of this easy (or at least as painless as I can) for readers to grasp, as I am still trying to grasp it all.  Most manuals, and Typo3 manuals are no exception, are written as if there are no problems.  Everything is set up perfectly, and everything runs smoothly.  Oh don't we wish this were only true.  So if anyone reading this catches me in an error or finds my explanation deficient please let me know

I do not know of anyone at Creighton who uses the edit/review/publish process as it was intended.  We use a basic versioning, keeping track of the versions and what needs to be reviewed/published ourselves.  It's simple but it seems to work for us.

That doesn't mean the tools aren't there, and more notably that the errors aren't there either, they are.  So we'll go over the tools and the process the way we tend to use it and cover as many of the errors as I can figure out.

And hopefully as we learn more about the process, at the least custom workspaces can become more common, increasing the functionality and ease of use of Typo3. 

Because the documentation on workspaces is scarce some of the reasons for the errors are best guesses only. 

Any reader with a better knowledge of workspace, please let me know.

Creighton University