SharePoint Wikis Aren't Wack

Author by Pete Hurth

The Enterprise Wiki component of SharePoint 2010 grants users the ability to easily create a structure to share knowledge, manage projects, and collaborate across an Enterprise. With the options to enter information as rich text or html, users can create content ranging from simple text to leveraging html to create more substantial wiki pages. Links can easily be inserted to tie together other SharePoint pages or reference external content. The process of linking within a wiki is core to creating structure. Documents, tables, images, video and audio may also be added to enhance wiki pages. Web parts are now available for use in wiki pages to create dynamic interaction. These are the same fully featured Web parts that are used across SharePoint. A version of a wiki page that is rolled back will include the Web part(s) so the entire page and Web part settings are pulled back to the desired version. Sample SharePoint Wiki Page with an Image, Text, Link and Web Part SharePoint Wiki  SharePoint wikis can quickly add value as a collaboration tool but require structure and focus in order to be successful. The following guidance is focused towards addressing these items: 1)      Don’t use wikis for the sake of having a wiki. Enterprise wikis are a powerful tool for quickly sharing and organizing information. Enterprises may be tempted to use a wiki without understanding that structure and focus are critical to leveraging this feature. The purpose of a wiki must be clearly determined and a guideline as to what content will be entered is as important as maintain the structure of information the wiki will contain. Multiple wikis can be implemented as appropriate and linked to each other. Example: Multiple department wikis can be linked together for cross department collaboration. 2)      Leverage the use of links, tables, documents, images, rich media and Web parts. The ability to include internal and external links, documents, tables, rich media and Web parts should not be undervalued. Example: Internal and external links can provide key information and a repeatable navigation structure within a wiki as wiki pages can be linked to each other. A list of documents can be placed in a wiki page to provide on the spot supporting documentation for a project. A table could be implemented to more concisely display data. Images and rich media will provide a highly level of user engagement. Web parts can be dropped in to provide a list of project tasks and their status, query data from other areas of the SharePoint site, or provide access to a document library. This article was originally written by Kelly Rusk. It is moderated currently by Peter Hurth.
Author

Pete Hurth

Social Collaboration Solution Lead