Saturday, October 18, 2008

Wiki vs CMS - the difference is psychological

When I started in EPiServer AB one of my first tasks was to "make a wiki plugin for EPiServer". Naturally, being new in my job, I enthusiastically started working. However, it pretty soon dawned on my that I didn't know what a Wiki really was. Sure, I use wikipedia daily and understand how it works, I know that "Wiki" means "fast" in Hawaiian, but it wasn't really that obvious to see what the difference is between a CMS like EPiServer CMS and a Wiki. I ended up writing an internal RFC on the subject, and awaited comments while I moved on to tons of other tasks, piling up on my brand new desk.
Around half a year later, I'm in a small but luxurious hotel in the Stockholm archipelago together with the rest of the EPiServer Research team, brainstorming on which new prototypes we should make for our big partner event in june. Again, the Wiki came in to play, and I spend a week or so making a working prototype of it, which I later demo'ed at the Partner Summit and hopefully soon will find time to finalize and ship as open source...but I digress. After reading Deane Barkers excellent blog post on the subject I figured I might share my views as well. So here goes:

 

"A wiki is a medium which can be edited by anyone with access to it, and provides an easy method for linking from one page to another." (Wikipedia)

"Contrary to their reputation, Wikis are content management systems that can be managed. They simply take a different approach to content management by choosing to emphasize speed and flexibility rather than strict controls." (CMSWatch)

So, what I really see initially is that a Wiki is a Content Management system focused on collaboration and knowledge sharing. A typical CMS has a some editors and many readers, where a Wiki has many editors and many readers. Not all that much of a feature. Just as Deane I've also looked at some of the key wiki features:

  1. The name of an article is embedded in the hyperlink.
  2. Articles can be created or edited at anytime by anyone (with certain limitations for protected articles).
  3. Articles are editable through the web browser.
  4. Each article provides one-click access to the history/versioning page, which also supports version differencing ("diff") and retrieving prior versions.
  5. The most recent additions/modifications of articles can be monitored actively or passively.
  6. Easy revert of changes is possible.
    On top of those features I would also include:
  7. Easy linking
  8. Easy creation of new pages

(Wikipedia's list of Wiki features)

All features that's either out-of-the-box or just a matter of configuration in any state-of-the-art CMS, like EPiServer CMS.
So, is a CMS = Wiki ? I didn't really see the difference until after I made a prototype and allowed my coworkers to start to use it.

The prototype I made was based on EPiServer CMS, and consisted of the following:

  • A UI that looks like wikipedia
  • View-mode editing of pages
  • Support for WikiSyntax ( like [[links]], etc.)
  • Ability to create a new page on-the-fly if there's a link to a page that doesn't exist.
  • Each page consists of X elements that can be edited independently
  • View-mode version control
  • Discussion Forum for each article
  • Handling of multiple concurrent edits
  • etc.

The moment I had a prototype up and running it didn't take me long to see the strength of these relatively small changes. It's addictive.
So, I realized that the difference between a CMS and a Wiki is really psychological. A Wiki's strength is fast and quick knowledge sharing - with everybody contributing to gather all their knowledge together. Why? A CMS is typically used for websites and/or intranets. Text-writers and editors use it to publish and structure their perfectly written articles. And here is the core of it all....A wiki doesn't need to contain perfect, complete articles. In the nature of a wiki anyone can add their knowledge instantly - either to existing articles or by beginning new ones - but without the obligation to finish them. And hence people are much more likely to start sharing their information. Still not with me? Here's an example: My knowledge of about the country of Norway is limited. If I were to write an article (or a blog post) on Norway I would have to do a lot of researching and then spend a lot of time writing and compiling all this knowledge. End result: I'd never get it done (mostly because I'm lazy, but also because I'm busy and not all that interested in the subject (sorry, Steve)). However, on a Wiki I wouldn't mind at all adding the few things I know about Norway to an existing (or non-existing) article. It would be something like this:

"Norway is a good place to go skiing. They have a lot of oil-money. Beers are rather expensive there. The capital is Oslo." 

But the point is, that I would share the little I know. And maybe someone else with access to the same wiki knows something else about Norway and will add it. Because they are not obliged to writing a complete, perfect article. That's why Wikis work efficiently for knowledge sharing - and that's the difference to typical websites built with a CMS (in my humble opinion).

But of course Wikis can be based on a CMS like EPiServer. Just wait for it :-)

30 comments:

RatX said...

Very interesting writeup, totally agree. I found your article when Googling for "wiki vs cms". I have always been a fan of the quick and dynamic nature of wikis, and have been campaigning for a formal install of MediaWiki at my office for some time. After several false starts, I've got daily backups and AD integration waxed, and it is ready for primetime.

The plan is for the wiki to act as a dynamic knowledgebase, without the rigid structure of plugging things into formally defined .doc files. These always end up stored in multiple locations, without any decent control mechanisms by default, which defeats the point entirely. Don't even get me started on the many "joys" of Sharepoint and/or Outlook public folders...

This is within the context of a single department, where I can trust my colleagues to manage and maintain the content between themselves.

Taking this view to a broader organisational level, however, I can also understand the role of the CMS. Here we need people in control of publishing and editing for the wider audience. I currently have a separate requirement to deploy an Intranet for one of my organisation's divisions, where the more formal control of a CMS would be required.

Thanks for your article, it helped me to clarify what I suspected was the case.

Vitaly said...

I agree with you. Actually a good wiki is a better CMS then CMS itself.

cms design said...

Thanks for the posts we are the professional web design and development company offering an array of services like template customization,web designing, CMS solutions, eCommerce solutions, Search engine optimization and Internet marketing.
WEBSITE CMS

fundoo said...

Thanks for the information, we will add this story to our blog, as we have a audience in this sector that loves reading like this” cms services

Julio said...

nice post

vlc said...

I think the point you made...
"Ability to create a new page on-the-fly if there's a link to a page that doesn't exist."
is THE key functional difference.

David bone said...

It was really nice to study your post. I collect some good points here. I would like to be appreciative you with the hard work you have made in skill this is great article.Content management system

saransays seo said...

informative post.. :) Mediawiki Tutorial For Beginners

Web Design Company said...

Its a great explanation about Wiki and CMS.
Website Design Company Bangalore | Bangalore Web Development Company

Website Designers Bangalore said...

Its really nice technology. Thanks for sharing truthful post. Web Development Company Bangalore

Joomkb said...

Learned lot from your post.
Magento Designing Company Bangalore

Jhon peter said...

Excellent comments with interesting topics and very useful resources. Thanks for sharing, Stansted Airport Parking

alex xavier said...

Fantastic blog . Lots of great information and inspiration, both of which we all need. Thankx...

Stone Sales

Web Developing Services said...

This is really nice blog to know about the difference between the CMS and WIKI.
Web Development Companies | Website Design Company

Swarupa Zinavo said...

It is always important to find out about the market standing of the company. The work of the web design company makes and breaks your business reputation in the market.
Web Designing Bangalore | Magento Developer

Web Designer in Bangalore said...

nice post. thanks for sharing this post...
Web Designing Company Bangalore

Rohini Rakte said...

WOW nice article about wiki vs CMS, Thanks to share!!!
Web Design Paradise

BangaloreWeb Guru said...

CMS is the best open source platform to develop the website to present in online.
Web Designing Companies in Bangalore | Web Development Company in Bangalore

Web Design Company said...

CMS is the best open source web development platform that offers more number of templates and plugins integrate into website.

Web Development Company in Bangalore | Website Development Bangalore

sunny sherry said...

The blog is useful and more informatics. Its an Excellent article…..,….
web content management system

divya chirsty said...

Its really nice technology. Thanks for sharing Useful post..

Web Design Company Bangalore

francy said...

Great job here. I really enjoyed what you had to say. Keep going..
Web Design Company Bangalore
Web Designing Bangalore
Web Designer Bangalore

Mykiddy tracker said...

Thanks for the information
gps child locator india

Manjot kaur said...

It is really interesting for me to read this article. Thanks for it. I like such topics and everything connected to them.

Web Development in Leicester
PHP Services in Leicester
Website Development Company in Leicester

Joomkb said...

Excellent post and wonderful blog!!!!
Ecommerce Development Bangalore | Magento Development Bangalore

Meenakshi Vyallur said...

Its really nice technology. Thanks for sharing Useful post..
Web Designing Company Bangalore | Web Development Company Bangalore

John Peter said...

This is very nice I really like it so much thank you for the post..

Best Hosting | Best Hosting 2016 | Web Hosting Reviews

Akshay Kumbhar said...

Hostgator India Coupon & Discount Hostgator India Coupon & Discount 2016

Moorthy Machendran said...

Nice thought..Your Expressive idea is good..
Best Web Hosting in India |
Top 5 VPS Hosting in India |
Top 5 Shared Hosting in India

APJ Cabs said...

Thanks For The Information, Nice Blog.

Rental Cars In Chennai