Changes

This article builds on the information at [https://en.wikipedia.org/wiki/Comparison_of_wiki_software Wikipedia] which is rather superficial but does allow you to dive into each product page. There is also the 'WikiMatrix' site that provides a more in-depth analysis and comparison of wikis (eg. [https://www.wikimatrix.org/compare/BlueSpice-MediaWiki+Confluence+MediaWiki BlueSpice vs MediaWiki vs Confluence]. ) But, that site is often incorrect, or at best stale.  == Comparing MediaWiki to Confluence == In comparing MediaWiki to Confluence, we're also looking at what other vendors or analysts say about their comparisons. BlueSpice, a MediaWiki distribution which is specifically aimed at the enterprise market, is built by the German company Hallo Welt!. They offer an [https://blog.bluespice.com/2017/05/17/bluespice-mediawiki-vs-confluence-the-wiki-alternatives-1/ in-depth point-by-point analysis of the MediaWiki platform compared with Confluence] (and give you the spreadsheet to see the details: 275 metrics in 18 categories!). == Executive Summary ==A simplistic conclusion when considering the origin of these products and their respective strengths would be that if your organization is a bunch of developers trying to push code out the door, then Confluence may be better because it does the essential "wiki" work; with integration into other tools needed in Software development. If you're an organization that has "Knowledge Workers" and you want to increase productivity, and revenue or decrease expenses around managing "company knowledge" then MediaWiki is probably the best solution. It excels at finding relevant information, collecting knowledge centrally, giving it context and structure, and curating its quality. Are you a MediaWiki expert or consultant? Discuss this topic over at the [https://discourse.equality-tech.com/t/confluence-v-mediawiki/191 QualityBox Discourse]. Edits, corrections and contributions here are welcome!!