Put MediaWiki to Work for You
NewsForge (Also owned by VA) is running a short writeup on how to put MediaWiki to work for your organization. The writeup includes several addition tools that could be helpful in rounding out the overall package. From the article: " Imagine how useful it would be to have an online knowledge base that can easily be updated created by key people within your organization. That's the promise of a wiki -- a Web application that 'allows users to easily add, remove, or otherwise edit all content, very quickly and easily,' as Wikipedia, perhaps the best-known wiki, puts it. Why not bring the benefits of a wiki to your organization?"
What a thoroughly useless article! It makes some vague assertions about what a MediaWiki good for, and than just regurgitates installation instructions. How about comparing this Wiki software with its many alternatives? Or even explaining why Wikis are so big?
Learning how to successfully edit a wiki page can be quite easy, however learning to completely manage a wiki and learn all of its editing and layout syntax is another matter altogether.
"To err is human, to mod Funny divine."
I work for a large visual effects company, and we have been using this resource for a while now. It is especially helpful when dealing with frequently changing pipelines and procedures, because it provides an easily modifiable up to date resource that can be accessed remotely from any machine on the lot.
I'm not a MW guru, but does the article's idea of <PHP> tag really do what I think it does?
As in "raw code in a a place where people can edit it?"
Doesn't matter they are trying to limit the wiki's edit access only to registered users - this is wrong.
Ugh. You know, one of the reasons why I like MediaWiki is that it does well with separating the page code from the HTML. And now these people want to sprinkle random PHP crap in the pages again. Argh.
And as an additional bonus, you get to store your mysql_connect() parameters to the page source. Whee. Realllly smart.
Somebody please submit this to TheDailyWTF...
The real way to do this is to write a MediaWiki extension, of course (look at ParseFunctions for an example of something simple), which is then accessed through the usual hooks, like {{foo:...}}, but don't ask me, I don't know that much about MW's internal structure. I just know bad ideas when I see them. =)