Tag Archives: TWiki

Challenges of migrating a company wiki to Confluence and why it is worth overcoming them (part 2)

Companies that want to convert from their current company wiki system to Confluence must overcome a few challenges: existing users are used to working with the platform, changing systems always involves trade-offs, and transferring existing content is complex and painful. In the previous article, we described these common challenges in detail. In this article, we will explain why the switch to Confluence is still a good idea and why the exhausting migration process is still worth the effort.

Enterprise Wikis: Criteria and important topics in the evaluation of wiki software

Wikis for intra-company usage are becoming well established as both commercial and open source applications. This article gives an overview of criteria and requirements involved in the decision making process, along with a comparison of our proprietary Wiki Confluence System and its open source competitors, Foswiki and MediaWiki.

Confluence and Foswiki Plugins – A Comparison

All wiki systems have the same basic functions: opening, editing and saving documents. These functions can be covered in a single Wikipedia paragraph. The functions of a more advanced business wiki, however, are more complex. A business wiki is not simply a web lexicon, but rather is intended to systematically handle a variety of processes in the company.

Wikis in an Intranet Part 2: TWiki in Actual Company Practice

In general, the establishing of a wiki must be supported through a series of measures. If these activities are successful, the system – as I know from my own experience – will quickly be accepted and used by employees. At //SEIBERT/MEDIA, TWiki has been used since June 2007, now containing a total of eight Webs. The main Web alone grew to contain more than 1000 topics within just a few months.

Texts should be created, shared, and edited in a Wiki, not in Word or within e-mails

Within a company there can be many approaches for the development of texts as well as the sharing of texts for further revision. We could, for example, write a text in Word and then load the final version into the enterprise wiki. We could also send around texts by e-mail, asking colleagues to read them and, if necessary, to make changes. But we could also develop a text directly within a wiki. What should we think of this particular work process?

66 Use Cases for an Enterprise Wiki (1 – 22)

We have summarized in our weblog 111 good reasons for using an enterprise wiki. But how can such a system blossom and show its’ added value and Return on Investment? What are some concrete examples of how companies can implement an enterprise wiki? Which possible uses make sense? Which of them are truly useful? And which of them can actually improve your efficiency? We have collected 66 ways to use wikis in organizations. Here are the first 22.

111 Reasons why you need an Enterprise Wiki

At //SEIBERT/MEDIA, we’ve been working on a wiki for years. Through our day-to-day work as well as through dozens of enterprise wiki projects, we have experienced – thanks to innumerable different cases – how useful and valuable a wiki can be on a number of levels. Therefore, we believe it is high time to compress the arguments for a wiki into the limited space offered by tweets to make our points as efficiently as possible.