If we're going to move towards a wiki, I think that incrementally adding wiki-like features here would be a lot more work (and be a lot more bug-ridden) than simply taking existing free wiki software and adapting it to our purposes, to be used alongside the blogging/messageboard software.
The most frequently used wiki software out there is MediaWiki
, which would probably not be too difficult to rebrand with the MaplePrimes look-and-feel; see Wikipedia
for an example of MediaWiki in use.
What would go in a MaplePrimes wiki? The basic idea of a wiki is centred around the idea of a web page that can be edited by anyone. A simple idea, but it has implications that require a bit of thought.
One issue is that wiki pages should not be owned by any one user. For example, one could have "Steve's Top 10 Maple Tips", but since the page name implies that only one person could edit it, this is rather contrary to the wiki spirit and might as well be a static webpage.
A slightly subtler issue is that, even if they're not formally owned by anyone, pages should not exhibit the personalities of their creators excessively: the idea is to work collaboratively towards a useful result, and avoid a tug-of-war over the page in question. Wikipedia solves this with their Neutral Point of View
policy. MaplePrimes could have a similar policy focused towards being constructive in discussions about Maple.
Some ideas for what could evolve on a MaplePrimes wiki:
- "recipes" of code for specific tasks
- unofficial, community-provided "help pages" for Maple functions or other components of Maple
- pages about using Maple written by and targeted towards members of specific communities (e.g. engineers, computational biologists, high-performance computing types, etc.)
- code fragments for people new to the language
- a good explanation of Maple's nondeterministic behaviour
I'm fairly familiar with the MediaWiki system from my edits on Wikipedia, so feel free to ask me any questions you might have about that.