Without coming across as a mad man hating anything with graphics in it and without causing much offence; Tabs are 2002, as well as anything blue/verdana/small-caps are design elements that make up a horrible period of BLOCKED.jacmoe wrote:I'll see if I can apply it to the test installation without tainting it too much.
Our idea is to leave Tiki untouched as much as possible to easy upgrades.
Ogre3d.org has a great look as it is, I can't see why the new wiki can't be like that. It isn't that difficult to port the css over and all the images required - are already here.
You should focus on the showing content first, then anything else; related links, addons, links to other parts of the side should be put off to one-side (not literally). Everything else needs to be context sensitive; if your not logged in then you don't need to know the previous history of the page, or who edited it last, or what the source looks like - it clutters up the page, and any search engine bots will go through all that and will be part of the results in Google, Yahoo, Bing, etc.
Have a look at the Django and Pylons wiki, both of them incorporate the wiki into the overall design with the website really well. I believe if your user doesn't know he's gone to a forum post to a wiki page, without noticing any change - then you've done your job.
[Edit]
I downloaded the latest TikiWiki to have a look at. Are you sure that the Ogre3D.org server will be able to handle it?
I mean the latest MediaWiki source is 37.7MB and TikiWiki is 80.8mb.
MediaWiki has ~1,500 files (of that ~950 are php files), compared to TikiWiki's 8000 (~3000 are php).
Eek! For the sake of the server, I have to change my vote to a no.