Can WordonWiki be compared to MS SharePoint?
March 17th, 2010
In a blog post of Martin Seibert called MS SharePoint as a Wiki: Few Functions, less Compatibility the author gives his view if MS SharePoint could be used as a Wiki.
His answer is simply "No".
Being this Microsoft Word dependent webservice, we looked closely to see if any of his arguments could be applied to WordonWiki. Let's run down the main reasons the author gives to justify his view.
Speed
MS SharePoint's architecture allows for a multi-server setup, forcing libraries and documents to be downloaded from one server to another. As there is no preview function, the document needs to be opened before it is viewable.
Thankfully, WordonWiki operates slightly different. It only requires you to download the page in case you need to edit it.Further optimizations will buffer pages on the user's machine to speed up even further the edit operation.
User Productivity
We were surprised to know MS SharePoint does not have a full-text search feature. This was foreseen in WordonWiki right from day1, requiring us to foresee special full text tables that can be indexed by mySQL text indexes. Not only for the current version of the page, but across revisions as well.
Lack of compatibility
Clearly you need MS Office on your machine if you want to work with MS SharePoint or WordonWiki. However unlike MS SharePoint, WordonWiki works on all major browsers like IE, FF, Safari and Chrome.You wouldn't settle for less. Nor would we.
Hide or Share
By default, MS SharePoint's documents are hidden, you need to flag them as public to make them visible. Indeed the exact opposite of what we expect from a wiki.
Origin of the product
MS SharePoint originally was a 'portal' solution. It has some data centric features added and the recent addition is the wiki feature. I've been at customer workshops where people actually believe that SharePoint's Wiki solution is as good as any. Clearly a big hooray for Microsoft's marketing departments.
Another big nono that Microsoft faces is the fact that MS SharePoint is very 'document' centric. This document centric strategy is what made Microsoft great in the 90ties. However, a wiki is basically 'page' centric. Microsoft has become big on this document adagio, but it doesn't translate it well to wikis.
Usability
Overall, SharePoint has a considerable learning curve. It has too many bells and whistles. Granted, it can do everything from making coffee to walking the dog, but that is not always what you need. There is a definitive need for simplicity.
The conclusion
There are many more points the author makes, but we covered those relevant to WordonWiki. The view of the article is critical but offers many insights on the nature of how and why people use a wiki. We feel that we live up to that challenge with WordonWiki. However, the last word is always with the user. Please comment to give us feedback.
The original article seems to trigger quite some debate, you can follow the comments to get a moderated view on Sharepoint's abilities.
Some readers have pointed me to more interesting articles on how to implement sharepoint as a wiki:
http://www.wikisym.org/ws2008/index.php/How_good_is_MS_Sharepoint_as_a_w...
Post new comment