In previous posts, I’ve discussed the use of a wiki for information sharing in an intranet. The main idea is having a central repository where each user can provide its insight and discuss the presented information. The posts discussed the requirements and possible alternatives.
The finalists were:
First TikiWiki was tried, as it was heavily recommended for CMS and wiki. The installation was a breeze, because a Linux server was available for testing with the required prerequisites already installed.
During the testing some things became clearer.
- The wiki needs to support well Microsoft word documents, for importing and exporting.
- Wiki management is a difficult task, specially for configuring the first settings.
- Selling the idea of a wiki is way easier than making others use it. The wiki should be designed to solve real problems and have a compelling reason to be used.
After having the insights, the whole strategy changed. The software options were limited to software supporting easy import and export of Microsoft documents. At the same time, I’m looking for people that are willing to give the wiki a try and create content with it.
The wiki software I’m going to try is:
My hope is people finding the wiki as helpful as I think it can be and easy to use so it can help everybody. After using xwiki I’ll update on next steps.
If you read this far, you should follow me on twitter here.