By me on Mar 07, 2007
As part of our CE 2.0 project we have deployed a large Wiki for our technical community called CEpedia.
In just a few month it got very popular and the contributed content is nearly doubling every month.
So why are Wikis dead ?
The main characteristics of a Wiki are:
|Objectives||How it is implemented |
|Easy to contribute||any user can contribute/edit a wiki page|
|Easy to edit||Wiki markup language |
|Easy to structure||Categories |
|Easy to manage ||versioning and easy rollback|
This looks all great but the technology is over 10 years old and the Internet technology has evolved quite dramatically.
It seems that some of the obvious advantages like "easy to edit" turns into the opposite direction AND we might create a certain legacy to maintain Wiki markup and HTML!
An example - I had the pleasure to train some of our management on how to use CEpedia and how to author a wiki page.
While it should be not a problem for a technical person to use the Wiki markup language - for a non technical person it is a night mare! Just try to explain how to create a table in the Wiki markup language.....
Today you would use a simple WYSIWYG editor and publish it to your Wiki system.
This is a nice thought but we have not yet found a WYSIWYG editor for a mediawiki which can properly scope with Wiki & HTML markup...
and is this the right approach ? Should we really support various markup languages to create/maintain web content?
o.k - here are my predictions:
|Objective|| Wiki ||Web 2.0+ |
| Easy to contribute||any user can contribute/edit a wiki page||Wiki or Web Content Management System (CMS) with ACL and ATOM feed|
|Easy to edit||wiki markup language ||HTML+ and ATOM feed |
| Easy to structure||Categories ||Tags, folksonomies, (Ontologies) |
| Easy to manage||versioning & rollback|
Wiki CMS, WEB CMS (like Drupal) & ATOM feed
Conclusion: The Wiki community model will stay - the technology will change