Jump to content

Recommended Posts

Posted (edited)

Been messing a bit with Wikis at work, and I was just wondering if having a Corolla wiki would be a good idea?

 

I mean, great as good a repository for information rollaclub is, vBulletin is a discussion forum. A wiki would be more like a traditional website, meaning that information could be organised and access in the same manner as one would a normal website. And it still has some rudimentary features for discussion.

 

I'm not saying get rit of vBulletin, just that a wiki might complement what we already have here.

Edited by wyldephyre
Members dont see this ad
  • Replies 39
  • Created
  • Last Reply

Top Posters In This Topic

Posted

A wiki is, in essense, a website which anyone can edit. That's what wikipedia is; and encyclopedia that is editable by anyone. Of course, it keeps track of changes, and you can customise it so that only registered users can edit.

 

The idea is, that like minded people, can come together and and create content quickly.

 

We're testing one at work, to maintain system documentation. It would be interesting to see how many of the team will actively engage in using this.

Posted

Nick, please tell me that you're going to break that engine list down into engine families (eg. A-series, S-series, K-series, etc). It's fairly hard to read at the moment. Of course, I do realise that you are just beginning to work the thing out, I'm just making a suggestion. I'd suggest the same for the Toyota models when you get around to it.

Posted

Oh, before you all go crazy, best read the wikipedia manual of style:

 

http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style

and the wikimedia markup reference from the mozilla people.

 

http://developer-test.mozilla.org/docs/Hel...arkup_Reference

 

The correct way to create a link in a wiki is : [[Page Title | Link Text]]. [http:// something] style links are supposed to be links to outside sides.

 

Wiki also has this concept of namespaces, which are like top level sections, if you will. So you could have things like drivetrain: suspension: etc. To customise them, you'll have to edit your configuration file a little. I can't find the link that describes them anymore, but the docco by the mozilla people is good.

 

It also might be worthwhile thinking how we want to organise the information, and what sort of information we are going to have. All the bits you have on the frontpage come to mind, possible subcategories could include things like diagnostics, maintenance, and upgrades. Lik Ancullen said, it is also probably worth splitting things like the engine series into separate subcategories.

 

Each user also gets his own page. Mine is at http://www.rollaclub.com/wiki/index.php?ti...User:Wyldephyre

 

Jamie's is at http://www.rollaclub.com/wiki/index.php?ti...ser:Super_Jamie and so on.

 

Might see if I can put up some pics and stuff after applying another layer bog on my front guard.

Posted (edited)

I've started a Tech: Namespace. (Edit the front page to see)

 

Of course, to be useful, you need to define a Tech namespace in the config file, but we can worry about that later.

Edited by wyldephyre

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...