Feb 8, 2010 at 4:17:49 PM by Stephen Danelutti
- Tags: trenches tips wiki crowdflo confluence
- Comments (0)
NOTE: This is part of a "from the trenches" series of posts covering general work day items of noteworthiness (most often as a result of customer work) that I feel I can share and which hopefully add some value!
Our product
Crowdflo is at heart an enterprise wiki and we continue to sell, customise and support the leading enterprise wiki from Atlassian,
Confluence - see what some of
our customers have done with their wiki's. A wiki is essentially an editable website and with the right permissions (who can edit/read which page or section) and notifications (via email alerts or rss), it becomes a powerful collaborative platform. There are broadly two types of process when it comes to collaborative content creation (authoring) and sharing:
Free flow
- Here the creator/editor/manager of the page or site allows all visitors to edit a page freely
- The creator/editor/manager may start with a broad-based “straw man” at version 1
- The content/topic is progressed by contributors freely editing or adding to the page
- The creator/editor/manager then edits/refines additions until the latest version is satisfactory
- Versions can always be reverted to using the page restore function
Controlled
- Here the creator/editor/manager may start with a broad-based “straw man” at version 1 similar to the previous case, but…
- The creator/editor/manager limits page edits and allows only page commenting
- The creator/editor/manager asks for input via comments and adds input (or doesn’t, as relevant and appropriate), until satisfied with the final version