Mediawiki is a fine engine to build public encyclopedias; it is very strong on what it is built for. IMHO it is not really suited for company internal use.

TWiki is specifically build for the enterprise, from the beginning. Key advantages over plain wiki engines:

* Fine grained access control: Define groups in TWiki, or pull groups from LDAP; restrict access to view/edit/create content on page level, web level and site level)
* Version control / complete audit trail, even for file attachements and meta data such as access control
* Authenticate via LDAP, AD or SSO
* Solid WYSIWYG editor (with TinyMCEPlugin [1], pre-installed in upcoming TWiki 4.2 release)
* 400 extensions to enhance/customize the functionality of the wiki engine, such as action tracking, barcode generation, blogging, calendaring, charting, conditional text, database access, Extreme Programming tracking, global search & replace, image gallery, LaTeX support, mail into wiki pages, page hierarchy, sectional editing, slideshow presentations, spreadsheet calculations, table editor, tagging, word alias support, XML and XSL transformations
* Mature plugin API: Developers can extend the functionality of TWiki with plugins
* Application platform to build wiki applications without programming (such as employee databases, inventory systems, blog applications, CRM systems, status boards, outage trackers)
* Per page namespace for attachments
* Commercial support available through TWIKI.NET [2]; large number of consultants [3] available to customize/enhance TWiki.


-- peter.thoeny.public AT twiki DOT net - http://www.twiki.net/ - http://twiki.org/

[1]: http://twiki.org/cgi-bin/view/Plugins/TinyMCEPlugin
[2]: http://www.twiki.net/
[3]: http://twiki.org/cgi-bin/view/Codev/ConsultantsForHire