I work for a software company whose main product at any one time exists in 4 versions, each version a further evolution of the previous one, adding, removing or altering features.
This, among other things, present us with a challenge when documenting the product, and I am currently trying to figure out if Confluence is technically adequate to solve the challenge.
I would like to hear your take on the problem. How would you structure this kind of documentation?
I see the following options:
1) Create a space for each version. Whenever a new version is required, a copy is made of the previous.
This has the advantage of nicely encapsulating everything belonging to one version, and allowing for easy access-control and deletion upon obsoletion.
Drawbacks:
* No reuse of unchanged pages and such.
* Copying of spaces is, as far as I know not supported out-of-the box, but there exists hacks wich makes it possible.
* Checking for changes between versions requires you to browse far away (could be fixed by manually adding links i guess, however the should manually be deleted when linked versions are obsoleted).
2) Same as (1) but using Page hierachis instead of spaces. Each root page defining a version.
This solution is much the same as (1), except copying of Page hierachies is supported.
3) Using multiple sibling pages, one for each version. Whenever a new version is required, a new copy is made of the previous and added to the same parent.
This has the advantage of placing different versions close to one another, making it easy to detect differences.
Drawbacks:
* No reuse of unchanged pages and such.
* Difficult to administer when creating a new version: Each page must be copied seperately.
* Difficult to remove obsoleted versions: Each page must be removed seperately.
4) Using one page for all versions. Each page is segmentet into versions (collapsible regions?)
I can really find any reason for doing this ... just wanted to mention that the subject had been touched.
We dont really find any of the above options to be very good.
Ideally We would very much like a kind of In-Page versioning, much like books-online, where you switch between .NET og Sql Server version by selecting the version from a drop-down on the page.
It would be nice of some of the page-content could be reused in some versions, e.g. 10 line description which is the same for versions A,B, and C but not D.
Creation and deletion of versions should be relativer simple operations (like copying or deleting an entire page).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.