Digital Paint Wiki

[jitspoe]

Here's a more official thread about the new wiki.  While I had so me cool ideas for creating a wiki from scratch, I don't really have the time to do it.  At least, I felt my time would be better spent doing something that hasn't already been done.

The old wiki got messed up in the site move, but it's still viewable here: http://digitalpaint.planetquake.gamespy.com/testwiki1/pb2wiki.php

The new wiki is here: http://digitalpaint.planetquake.gamespy.com/wiki/ -- go ahead and tinker around in the playground if you want to.  That section is currently open to everyone.

Before we start going all out, though, we need to come up with a good structure to it.  I was thinking something along the lines of:

- console
-- client commands and settings
-- server commands and settings
-- example scripts and configs
- community
-- clans
-- biographies (or perhaps "player profiles" or just "players")
- development
-- mapping
-- coding
-- sounds

There are a few other things I need to figure out how to organize: admin area, help/support/troubleshooting, maps, faq, guides, servers

[jitspoe]

No feedback? 

[P!nk]

Post removed

[jitspoe]

After dealing with dokuwiki a bit, I'm thinking it may be better for me to just finish up the one I started.  Dokuwiki seems to be really slow, doesn't match the theme of the site, and is lacking some features I want.

[MrRiblets]

Yah I find it very slow.

[lekky]

i think if it matched the site theme it would be a whole lot better. to me that one looks like it could be one of thousands exactly the same. out-of-the-box model.

[jitspoe]

It is the out-of-the box model.   I haven't gotten around to making a new theme for it.  I think I may keep working on my own wiki, though, and just ditch this one.  It's too slow to be practical, and it doesn't have an "include" feature.  There's a plugin, but it seems rather limited, and it's not installed by default.  For things like console commands, I want to be able to break them up into smaller groups, then be able to include those on different pages.  Once I get build 16 wrapped up, maybe I'll focus back on the wiki again, as I'm tired of answering the same questions over and over.

[lekky]

well, if you can handle the work jits, i think it would be much better to create on of your own.

but maybe its just that dokuwiki isn't very good in itself. Are there other's that could be used?

at the end of the day bespoke is always better, just requires alot more effort

[jitspoe]

bespoke?

There are others, but I don't care for most of them.  Many run on perl, which gamespy doesn't support.  They also tend to be case-sensitive, which is a pain in the butt from a user standpoint.  Most of them are slow, and pretty much all of them aren't tailored to our needs.

[lekky]

bespoke, i didn't know that was just an english term?

means tailor made, or custom made for a specific purpose or specific requirements. but yeah like i said, if you can give us a tailor made one that would be by far the best approach

[KnacK]

So Jit, which one will it be??

We have 2 huge additions to the wiki:
The mapping tutorials
The server/client commands guide.

DO I need to go in and back all of that up and save it somewhere first??

[jitspoe]

Dokuwiki saves backups each time a page is edited, so that won't be necessary, unless you want to do it, "just in case."

[Burt_Gummer]

If dokuwiki is too slow, have you thought about MediaWiki (http://www.mediawiki.org/)?

[KnacK]

I don't care what we use, as long as it isn't sticki-wiki

[y00tz]

Edit: My bad.. this dokuwiki isn't the same wiki i was referring to... umm is there two paintball wikis?