Thread:Project:Support desk/Should I use MediaWiki for my project?/reply

Hi!

MediaWiki has a broad user base, it is used in many places, has much software built around it and - compared to other wiki systems - it will be rather easy to extend it the way one wants and to get help should that be necessary. So if you say you want a wiki, then you should really use MediaWiki and not something else.

If you want to create an own skin, then you can start from scratch (hard) or take an existing skin (many are provided for download from their maintainers) and change this one the way you like.

As for the functionalities you mention: Sign up and so on are present in MediaWiki, but when it comes to access control you should read Manual:Preventing_access. Bottomline: MediaWiki is not made for access control.

What do you mean with "buttons"? The buttons "Page", "Edit", "History" and so on? Can be hidden with CSS. Own buttons can be added via hooks, here is a list of all available hooks.

The code of a certain page can be viewed using the "Edit" button. If you in contrast mean the template (which is used for every page), then you should have a look at the according skin file - with the default that's skins/Vector.php.

What exactly do you mean with "process components"? Some things and each one should have its own page with information, maybe this information should be displayed based on a template? Something like that?