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.
If you take a closer look at the various company wiki systems available on the market and objectively evaluate them, you will likely come to the conclusion that Confluence by Atlassian is the best and most sophisticated solution out there. Often, such comparisons are made when a company already uses another wiki – a system that grew organically beyond a department, an open-source system introduced as a trial run, or consciously chose the Wikipedia system MediaWiki because it’s the most successful software of its kind.
A crucial step in the implementation of a wiki within a company is the selection of the right wiki software. One must assess the major pros and cons of each system in order to make the best choice. In this article, we evaluate the open source software MediaWiki, and draw the conclusion that there is a better option.
In our article, “Enterprise Wikis: Criteria and important topics in the evaluation of wiki software” we discussed the diverse and unique requirements an enterprise wiki needs to meet. Decisions about choosing the right wiki system cannot be made using generalizations, but rather only by taking into account the specific needs of the company. In this article, we will draw a concrete comparison between the approaches of the Atlasssian Confluence commercial system and the open source systems Foswiki and MediaWiki. What are the strengths of Confluence compared to Foswiki and MediaWiki?
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.
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.
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.
Wikis for enterprise use, both those available commercially as well as those available in open-source contexts, have become quite sophisticated. This article introduces and evaluates possible requirements as well as decision-making criteria.