The main business reason which made me to start the discussion about the necessity of having an Enterprise Wiki was to encourage many-to-many communication between the team’s members. But, there were others like:
- The necessity of having a central repository tool which hosts, in my case, technical knowledge and information accumulated during the IT projects;
- The necessity of categorizing the information (both as Taxonomy and “Folksonomy”) in order to access it faster;
- Search engine.
Having said that, the natural choice was to implement an Enterprise Wiki in SharePoint 2010. The other advantages gained by choosing it are: Versioning, Approval (at the end Enterprise Wiki is a publishing site, but for sharing technical resources I don’t think it’s necessary).
Before strating, I would suggest consulting the following TechNet articles:
In order to deploy an Enterprise Wiki we need the following:
- A site collection created based on one of the publishing site templates or another site collection where the SharePoint Server Publishing Infrastructure feature is activated at the site collection level;
- Managed Metadata Service and Search Services (if we want to search within the Wiki ) shared service applications up and running.
Basically what I have to do is to deploy a SharePoint 2010 built-in feature. I have a publishing site collection – Intranet where I will add an Enterprise Wiki as a child site which will host my content.