The story of my acquaintance with this engine began very simply - the bosses demanded a corporate website, and preferably on the Wiki engine.
MediaWiki did not pass on access rights,
DokuWiki is too simple,
JSPWiki was very close, but something could not be found to cross it with domain accounts. Then more important tasks came up and we had to postpone the whole project for a couple of months.

And then one day I come across an opennet on the
news about open projects that may be of interest to the business. Among them was the
MindTouch Deki Wiki . A quick inspection revealed the engine's suitability. What surprised me most was that I had not yet stumbled upon it. Installation using the finished image of the virtual machine was quick and painless. The interface is nice, the pages are edited in the WISIWIG editor. Images are inserted with thumbnails, you can hang tags, but this is not the main thing. The best thing about this project is documentation.
FAQ detailed and complete, considered the necessary and useful things. English is not difficult, Linux teams are international. With the help of this very FAQ I connected the wiki with the domain and gave the default rights to domain users in 30 minutes with a break for tea. In addition to the login username loads the full username. The engine supports extensions, but they were not useful to me. Those who wish can connect their wiki with flickr, diggom or google maps.
Among the shortcomings, I can note that the user name is used as an identifier, respectively, a name change - while the laborious manual process of updating tables is required. It is good that it is described in the same FAQ. And he constantly swears at the opera, they say, it is not supported, etc., but it looks normal and works fine in it.
Summary: If you want a corporate wiki, look at the Deki Wiki.
')
images taken from wiki.opengarden.org/Deki_Wiki