MekiaWiki for enterprise, possible builds and solutions?

Question

PHP

Good afternoon.
The question is the following, we were faced with the task of deploying the MediaWiki engine at our enterprise. The main functionality of which is conceived to store the base of accumulated experience in the enterprise, and the contingent using this product will be very diverse - from programmers to engineers and the design department.
Of the main requirements set out before us are:
- transparent authorization (transparent if possible) of users from the domain (Windows Active Directory);
- attaching various files to articles, from msword to video archives;
- organization of a clear structure;
- a search module that examines both articles and documents attached to them.
- optional, full WYSYWIG editor
- optionally, the ability to document the source code of applications (CSharp, PHP, Git, TFS).
Plugin for generating class documentation from sources.. something like phpDocumentor.
Faced with what, there are a large number of assemblies on the network, it will not be possible to fully test all of them. Therefore, the question is for you, who will advise what? You need a build with a full set of already built-in plugins, constantly maintained, and having normal support and community. Paid solutions are a priority. Thank you!

Answer 1

Good afternoon!
After reading the list of requirements, I see that it is possible to offer the Atlassian Confluence product for a solution. This is a corporate wiki, https://www.atlassian.com/software/confluence .
Designed for organizing a corporate knowledge base, intranet and even Internet sites, collective creation of documents.
About the implementation of the requirements:
- support for authorization with storing users in AD, NT_logon authorization is available after installing the plugin, there are several options
- you can attach files to articles, and MS Office files can simply be attached, or you can import them, with markup preserved and online editing possible;
- there are concepts of "space" and "page", you build the structure of each space as needed;
- WYSYWIG page editor, page template editor, "themes" spaces;
- a very advanced search engine, based on the Lucene engine;
- for commenting on the source code, you can connect the Crucible application from the Atlassian Development Tools - https://www.atlassian.com/software#devTools .
About formation of the documentation on classes from sources - explain please.
Yes, the product is written in Java and therefore multi-platform and scalable, commercial, the cost is not high.
There is a REST interface, API plugins.
Send questions to atlassian @lionsoft .ru

Answer 2

No matter how much I heard about the introduction of wiki systems, everything merged into the account that no one writes anything. Decentralized seeding is a tricky thing, requiring everyone to have minimal wiki knowledge. If EVERYONE really wants it, then it will work.
For me, you will have author articles, and with them it seems to me easier to organize blogs and make publications in different categories. Without a host, admins, it seems to me that it will be lazy to fill in all this for the people.

Answer 3

PS Any introduction of such products begins with the question "why do I need this and already lived well" and ends with the question "why didn't you think of using it earlier?".
If we expand this idea, then it all depends on how users will feel their comfort and benefits from using a corporate wiki or knowledge base. Many simply do not understand the benefits of co-editing documents until a project is encountered, for the delivery of which on time it is necessary to make, for example, a document of the "technical project" type by several employees in a short time.
We have it organized like this: JIRA for assigning tasks and managing release versions, all current work and planning is carried out in JIRA. And the results of the work are in Confluence and in SVN and Git (Atlassian Stash product).