The Wiki format is far more akin to "documentation of knowledge", and the first step for it to work is for someone with an understanding of where that document is headed to first lay out a framework. Only from there can you really start getting community support for the page/project as individuals add their own information to augment the existing content (or correct it, which starts a whole new series of issues).
My basic idea behind the TFSA wiki was to try to document some of the useful information that the TFSA forum area produces (with the emphasis on
some). The goal isn't to duplicate the work done in the forum, but there are some instances where the more formally structured, editable nature of the wiki could produce better results than the forum discussion format.
Examples of instances off the top of my head would be:
- Where the content is dynamic and needs fairly regular updating,
- A subject is a compilation of multiple "threads", aimed to give a better overall understanding,
- It's a document that would benefit from having multiple contributors to the finished product,
- Updatable lists.
Ultimately I think we should recognise that the wiki format is nowhere near as engaging as the forum format, and is unlikely to ever see the same level of participation as the forum area does.
At times I've even thought of dropping the wiki addition entirely (normally when dealing with a vBulletin update that messes up the integration, which is pretty challenging

). However, I've ended up keeping it as there are scenarios where it could prove a
very useful tool to have handy one day.
In the mean time it remains available as an area for members to add to as time and passion may provide.
The
TFSA general disclaimer should deal fairly well with the liability concerns raised. (Of course and as always, I'm open to any suggested improvements).
Did you like this article? Share it with your favourite social network.