Gaming
 

Wiki Editor Guidelines

From Kongregate Wiki

If you want to contribute to this wiki, thank you! Here's some guidelines and tips to help you get started writing for us.

Contents

[edit] General Wiki Editing

There's formatting tips in a sidebar to the left. Usually, that's all you need. The wiki accepts both wiki-style markup and HTML markups. CSS is also accepted, but it's preferred to send me a message so that the CSS you use can be reused. If you would like to add in special formatting and don't know how, please leave me a message User_talk:EsIeX3 and I'll take care of the formatting for you.

When taking any images at all, please store it in .png format, but if it is animated, store it in a .gif. PNGs have many advantages over alternative file formats. For example, JPGs leave nasty artifacts all over the image and make text hard to read. PNG uses lossless compression, which makes the image a much higher quality.

[edit] Taking Videos

Under Windows, go ahead and grab camstudio. When using Vista, there won't be any sound if you choose the "record from speakers" option. If you really need sound, go to the control panel -> hardware and sound -> sound -> manage audio devices -> recording -> enable the stereo mix. Then in camstudio, choose the "record from microphone" option under the audio.

Under Linux, you have lots of choices. There are some listed here: [1]

We prefer that you upload videos to Youtube, but any site which allows embeddable videos is fine.

[edit] Games

We have yet to establish any strict format for how game articles should look. However, every game article should at least have this information:

  • Author
  • Genre (shooter, RPG, multiplayer, etc.)
  • Basic Gameplay
  • Link to the game

Other material that is highly recommended:

  • Links to Guides
  • Critical Reception (along with links and current rating)
  • Recognition (why this game could be recognized among the Kongregate community. For example, Desktop Tower Defense could be mentioned on how long it was the highest rated game)
  • Trivia
  • Images of gameplay
    • When adding images of gameplay, please name it something like GameName_ImageName.png. This is to prevent image name conflicts between 2 games.

[edit] Badges

Like games, there is currently no standard way to make a badge article look. Badge pages require the following information:

  • Game
  • Objectives
  • Difficulty/points

The following is highly recommended

  • Guides/Links to Guides
  • image of badge
  • origins of name

[edit] Kongai Style

When making a character page, they must follow a similar formatting to our Tafari page. When you make a screenshot of the attacks, please save it as a .png file rather than a .jpg. PNG files use much better compression than JPG's, so there's less artifacts obscuring the texts.

If you wish to add large images, keep the image as a PNG file, but link to it using a thumbnail instead of inserting the whole image in the article. You can find a good example of this in Maneuver Phase

When making an item page, they must follow similar formatting to our Healing Salve page. Reinforced Breastplate is our testing grounds for item page layouts.

Whenever any characters or attacks are listed, please list them in the same order as you find on the Kongai Card Album on Kongregate.

When linking to a character's attack, keep to this style: Yoshiro's Rising Dragon This helps to emphasise that you're talking about the attack rather than the character, while allowing the viewer to understand who's attack is is. If the attack is shared e.g. Ninja-Port, link to the correct character's Ninja-Port directly. Rumiko's Ninja-Port.

All character, item and attacks should have a capital letter at the beginning of each word to help identify them, otherwise, stick to accurate grammar.

[edit] Developer Guides

As the developer guides section is fairly sparse, we have yet to decide on a layout for our articles. However, there's some formatting tricks that aren't listed to the left that you will need, especially when you list code.

When you want things to appear in a box like this:

foo bar

Add a space after each new line. To make sure that things get formatted correctly, please add in <nowiki></nowiki> tags.