Semantic. Presentations. Create a PBwiki account. DokuWiki] DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database.
![DokuWiki]](http://cdn.pearltrees.com/s/pic/th/dokuwiki-43130103)
It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki. Get started: Why DokuWiki? DokuWiki is a popular choice when choosing a Wiki software and has many advantages over similar software. Easy to install and use Low system requirements Built-in Access Control Lists Large variety of extensions Over 50 languages supported Device independent Open Source Learn more about DokuWiki features Use Cases Wikis are quick to update and new pages are easily added.
Corporate Knowledge Base Private notebook Software manual Project workspace Customizing DokuWiki Our Community. Haiti/2010 Earthquake - CrisisCommons Wiki. Wikit. Wikis, surveys, and webwhompers. Continuing on the thread of when have I seen wikis work the best...
In my last post I answered that I have seen wikis work quite well when they are tightly controlled. I described the LeaderNetwork wiki, which only allows editing by Claire Reinelt and me. Another good way of controlling a wiki is not by limiting the number of editors (as in the previous example) but by limiting the contributions asked of each editor. Used in this way, a wiki is quite similar to an online survey. The wiki begins with a clear list of questions and a well-defined framework to hold each response contributed by each wiki editor --- just like SurveyMonkey. Transparent sharing of all wiki-survey responses is a given. Wikis in SharePoint 2007. The Firm has taken its second step into Enterprise 2.0 with the launch of our first wikis in SharePoint 2007: Our first wiki was an import of our existing knowledge management wiki into the SharePoint platform.
I wrote about that wiki in a previous post on Making Wikis Work - Success Factors. That wiki had been very successful on the external platform and I expect it will continue to be successful on the SharePoint wiki platform. There have already been several edits. The downside to moving the wiki was that all of the links in the wiki broke. We had debated on whether to move the wiki. We also launched a second wiki for managing HotDocs and our HotDocs templates. We found one great feature of wikis in SharePoint is their ability to combine structured and unstructured information on the wiki page. By adding the structured content we can also create views of the wiki page library to expose content, rather than having to rely solely on links in the wiki pages. Making Wikis Work - Success Factors.
I have been using wikis at the firm for the past few months.
Here are three case studies that I hope will shed some light on factors that help wikis work or help them to fail within the enterprise. Since we are still working on our deployment of Sharepoint 2007 and its wiki capability, I decided to host these three wikis with an external provider (PBwiki.com). Client Team Site. For one of my client teams, I had started a practices and procedures memo. Initially, I converted the practice and procedures memo into pages on the wiki site. The client team site was imposed by me, as the team leader, by fiat. The team is coming along, but coming along slowly. Practices and Procedures Memo. I stumbled upon a practices and procedures memo for another client that I am supporting on the knowledge management front. There are links to key documents in our document management system (the links only work if you access the wiki from inside our firewall.)
Edits to the wiki are few and far between. Edgewall Software: Home. The Trac Project.