Team Fortress 2

Team Fortress 2

55 ratings
A (semi-) complete guide to the TF Wiki
By Faghetti | RSP and 1 collaborators
Got a writer, translator or media wizard hidden in you? Ever wanted to contribute to the game, but didn't know how to? Ever felt annoyed about not having your language available for anything?

Then this guide is for you!

This will be a thorough walkthrough of the TF Wiki which is so frequently used and how YOU (yes, you!) can become an important asset and help to the entire playerbase!

The guide will include the following interesting points: How to begin, finding your way around, how to edit/translate/etc., important things to note and the different types of work you can contribute with.

Hope you'll be interested!
(Warning: If you are allergic to bad paint pictures and illustrations then do not read further).
 
Rate  
Favorite
Favorited
Unfavorite
1. Welcome! (Introduction)
You are a curious individual who clicked on this guide for wisdom! For knowledge! To become an inhuman machine! A wiki activist!.... or you just misclicked and is looking for the local guide for using cat meme sprays efficiently on ctf_2fort. If you are the first person I bid you welcome and happy reading, if you are the second.. person?.. I question your sanity.

As the only other piece of text on this forum related to the TF2 Wiki is a 4-5 year old guide called "The Ultimate Guide For Obtaining A Wiki Cap in Team Fortress 2." I thought I'd update it as it is incorrect, too focused on one thing and doesn't go in-depth at all about anything (not even the thing it is advertising), so I hope I will do an acceptable job at explaining this to all of you who are legitimately interested in becoming part of the team!

This is what you can expect to get out of this, and it is already time for our first topic which issssssssss *drum roll*

1.1 CREATING AN ACCOUNT
Most of you are probably confused as to why this even needs to be a topic at all: "Making an account is literally easier and more automatic than breathing - why would you even waste time on such an easy thing?"

While I can't deny how easy it is I thought it would be nice to start at the beginning so everyone was on board and ready to take about the more "complicated" and "interesting" subjects later on... Plus it is a nice springboard for the next subject, so just skip it if you are familiar with how to use the internet (which you should be if you could find your way on this subhub on Steam anyways).

So here is the process in steps:

Step 1: Find your way to the Tf2 wiki front page

Not a whole lot to add to this, but if your front page looks like this


Then you went to far.. you can still work for that one if you want to, though - I am not gonna stop you (for you people the guide ends here pretty much, thanks for reading this far).

Step 2: Click on one of these buttons


Step 3: Enter your username and other stuff


If you want to you can also gawk at all the amazing info on the right, or add your real name and an optional question to make it easier to get your account back if you should forget your password... I'd advice you to just remember your password and not forget it like some idiots would. (I certainly never did that! (I totally did :C)).

Step 4: Done
You now have an account - congratulations.

While that was insanely complicated, just hold on because it will get even wilder in a second, but until then you will have to know a little about your very own page!

1.2 YOUR PAGE

Everyone who makes it to the other side of the account creation screen gets their very own page which can be found by using the search bar and writing "User:[account name]" (you can of course also find other users by the same mean).

It is also accessible by clicking on your name in the top right corner:

That is my name, though, expect something else for you ;)

Your page is your own little hub where you can share information about yourself including your goals, your "history" and what you have already done for the wiki thus far. It doesn't have to colorful or flashy, but with time most editors find ways (and by that I mean they stea.. I mean lend from those who have kick @ss pages) to create a page they like with all kinds of cool functions.

Here is an example of a page in the beginning and in the end:

The beginning:


The end:


Both are mine at different times, but a lot of people, a lot better at coding, have pages that crush mine into the core of the Earth :P It is fine as an example though (I hope).

Just as an example my page contains:
A link to my translation list (what I have done thus far made into lists on a list).
A link to my wiki.tf page (statistics etc.)
A link to my sandbox page (a page for creating what you want)
An infobox with a picture, self-chosen color, and some links to mention a few
An user info box -the little red square under notes- (we got million of these, so go nuts)
A milestone/goal check off box thingy
A bar showing the total progress of the language I'm translating for
Two self-made items with my own info, desc, etc
And a list showing my wikichievements (yes, we have self-made achievements, too)

And that's just some of the thing you can have!
If you want to explore my page (or others) click on this link here:
https://wiki.teamfortress.com/wiki/User:Faghetti_V.2

It should be noted that editing anyone else's personal page is against the rules and will lead to some irritations... so remember to ask the person first!

1.3 THE IRC CHANNEL

The last thing I want to mention in the introduction is the IRC channel which is located here on the wiki:

The irc is a place where you can communicate with the other members of the Wiki and ask for help with anything you might have trouble with. You can also see the things other people add to the wiki at all times, which makes it easier to track what people are doing (and catch those who are doing it very wrong).

This is what it looks like:

The names on the right are people there and the names with the prefix "+" are the administrators or moderators.

You can use any name you'd like, but most people just go with the name of their account to avoid confusion.

This will be it for the first part, now for the second one (hopefully a more interesting one!)
2. Finding your way around
IMPORTANT NOTE
You will find out about most of this by just being on the Wiki for a while, but it can still be useful information. If you do not wish to get dragged through all these pages I'd advice just to skip ahead to the part about the dictionary (if you're a translator) and continue from there. :3 Happy reading!
/IMPORTANT NOTE OVER

Welcome to part 2!

In the last part we went through all the basics of account creating, your own page and the communication channel (the IRC), but now it is time for finding helpful and important stuff.

And that is all - let's get to it shall we? So the first point:

2.1 THE MAIN PAGE
Here is what is accesible through the main page:




You will also a notice a sidebar. On that one you can find:


And when on actual pages you can also find:


That shows you all the available languages for the page. If yours isn't on there (and if it is compatible with/has been added to Tf2) then you can make a new translated page for it.

And lastly all the stuff next to your name in the top right corner:


Now for some small search things about the search bar.
As I have already told you in the previous part, "User:" is used when wanting to find an user/account, but we have more words like that for general things, for example:
Template: - is used when wanting to find a template (I'll get more into those in the next part)
Category: - is used when searching for a category page.
Help: - is used to find all the help: pages that gives you advice on how to do things.
File: - is used for finding photos stored on the site.
Team Fortress Wiki: - is used for finding pages related to the wiki itself.
Special: - is used for finding special pages. (Like the one where you add photos)

This should be it for the main stuff, next I want to show the more helpful and important pages for starting out, for questions and for actual translating purposes.

let's start with the former: for questions, guidence and factual information.

2.2 THE HELP PAGES AND THE NAVBAR
So when you are stranded and stuck on this island of knowledge you can sometimes forget how to do things properly and need some guidence, but you do not feel like asking - what do you do?
Well fear not my friend because there is a solution: Help pages!

First how to get to them:
As stated above use the Help: prefix on the search bar, but one help: page is really important and linked to the main page so I feel like exploring it a little more - that is the "Help:Language translation" page. If you're not a translator, you can skip this obviously.

To watch/read it yourself go here: https://wiki.teamfortress.com/wiki/Help:Language_translation

If already on the main page you can find it here:


The page you end up on should look something like this:


Everything written on that page is important, so if you are interested in working on the wiki you might as well read either that or the next part of my guide to insure better quality edits.

But you'll notice at the top there is a box with a lot of options: That is called a Navigation bar and, as the name implies, they are used for connecting related pages to each other. Every update page gets their own, tools got one, all classes have one and (probably the most used) all cosmetics have a humongous one.

That navigation bar (or Navbar for short) is the TF Wiki navbar and is the same one you can find on the bottom of the front page, and everything on there is pretty useful, so I'll go through it:


Under Guidelines you'll find everything you need to know about rules, page styles and stuff related to that, but more specifically we got:

Terms of Use - This page documents the Wiki's policies with legal considerations. (I have personally never read it, but if you want to then be my guest).

Policies - A little more helpful for the general user, this page documents all the accepted policies and guidelines the TF Wiki has. A quick look through this should give you an idea of what is accepted.

Update Checklist - Basically a list of things that needs to be done everytime an update gets released. Look through it if you wanna help updating the wiki after an update (believe me a lot of stuff can be forgotten).

Images (or Guidelines as it links it) - Helps you with adding pictures to the wiki. Helpful for when you need a profile picture or something for your page, so give it a read-through if necessary!

Licensing - Again in the law stuff, but it is important so make sure the picture you add is stepping over anyone's toes - especially the wiki's ;).

A-Z - A help page about general grammatical use when writing in the English language. Things like "a or an", "affect/effect" the use of apostrophes, "as or since" and a lot more. Use it if your English isn't the strongest or when in doubt about certain grammatical quirks.

Maps - A help page on how to set up map pages. Give it a read if you want to add a map (or just look through other map pages and see what they have done).

Trivia - A help page on how to add the most often deleted thing on TF Wiki - trivia! Just ask Ashes if he is tired of deleting irrelevant and bad trivia from pages and I'm sure he'll reply with a resounding "yes". Anyways look it through before adding some trivia, so you are sure the choosen trivia is not trivialized and terminated by tempted and tired "TF2 tyrants" ;).

Weapons - A help page on how to set up weapon pages. Weapon pages are generally in the high end of short to the high end of medium in terms of page length and text, and there are often a lot of things to link to and from it, so make sure you get everything in there when adding a page.

Quotes - A help page on how to set up the quotes... you know those things on the top of most cosmetic pages that everyone likes with a quote from a class and a sound file attached? Yeah, they have rules too... Not many, but a few to keep in mind.

Bugs - A help page on what bugs to add. You might think to yourself that we accept all and all bugs, but that is not the case. To give an example: We do not want clipping issues on cosmetic pages since it is so easy to make with a lot of items and not really too interesting, so refrain from adding those.

Strategy - A help page for the style of community strategy pages.. Don't even bother with those unless you are an insane man. After the voice line pages they are some of the huges pages and in terms of text they are probably THE biggest blocks you'll ever sit through. There is probably more important pages to tend to first, so let them be for a while. (Plus they change so often anyways).

That is it for the "Guidelines" now on to the Discussion related pages.

(Continued in part 2.... of part 2)
2. Finding your way around (pt. 2)
Welcome! Last time we just got done looking through the "guidelines" on the Navbar for the Tf2 wiki and just got ready to talk about the Discussion pages - so let's continue:

Communication is key on any wiki to insure everyone can help/talk to each other so we can work as a team, the pages linked here are for asking questions, getting help and helping others:

Main discussion page - Every page (and I do mean every page) on the wiki has a talk page for discussing things relevant to the page in question, but for things related to the wiki itself or bigger "thoughts" it can be taken here. (Right now it only has 6 "discussions", though).

Technical requests - If you have any proposals or requests for changing the technical stuff on the wiki this is your place to go.

Talk:Main Page - A link to the talk page for the main/front page of the Tf2 wiki. You can also find it by just clicking on the "DISCUSSION" button/tab next to the "MAIN PAGE" button on the front page. Go here to complain about the outdated blog posts.

Translators' noticeboard - If you want to ask a question about translation (whether for your language specifically or just in general) then this is the place to go - just remember that it is often for more 'complex' questions since all question to the technicalities can be found on the "Help:Language translation" page. There is also a place to go for discussions about only your language, but I'll get to that soon.

IRC - Takes you to the same place as the "IRC channel" button on the sidebar. From there you have acess to the IRC channel, an instructual video and some more rules/guidence for communication on the channels.

The #tfwiki button seems to be broken or outdated - don't click on it... I SAID DON'T CLICK ON IT ୧ʕ•̀ᴥ•́ʔ୨

webchat - Just takes you directly to the chat channel.

Now for those who want to translate we come to the most important of the TF Wiki pages! (The ones I've used the most anyways) - the Languages pages. So let's see what they have to offer:

Language translation guide - This page explains how to translate pages. What to keep in mind and some guidelines.

Translation progress - This page shows how far each language is in its full translation of the wiki. For example: The Danish progression is at 52%, so 52% of the pages have a Danish translation page associated with them. It doesn't say anything about the size of the pages, or how updated they are - just if they have been made at one time or not. On the same page you can also see the shortcut name for all languages (and all available languages for that matter) and three links:
The first link "Discussion" takes you to that language's "translation progress" page where you can see the active contributors for the language and discuss things related to the translation of the language or whatever (one of the few pages where you should use your own language for communication - elsewhere you should use English).
The second link "recent edits" takes you to a page where you can see what has recently been changed/added/deleted/whatever on the translated pages within your community.
The third link "more stats" is a little more interesting: It shows you how many pages are left and within what categories ("classes", "Achievements", "Primary weapons", etc.). Should be noted that not all pages fit within a category, so only about half of the total pages are showcased under these categories.

Translation switching - Basically explains how languages work on templates. Give it a read through if you want to change a template or maybe even add one yourself.

Most wanted translations - When I first started I thought it actually showed the pages people looked for the most (eg. searched for it or something), but in reality it is just a list that shows what pages (that do not exist yet) have the most links connected to it. That is why a lot of cosmetic items often are at the top, because every other cosmetic item (of that language ofc) links to them. Give it a look through if you feel like it.

Missing translations - A page showing the untranslated pages of each language. It also has a link for "Users by edit count" that shows the amount of edits done in total, how many new users came that month and the all time top 100 for edits (I'm on the 60th spot :D). Other than that it shows maintenance of pages already created so we can avoid duplicates, broken links, typos, etc.

Now for the last category being "Help center". It, as the name implies, is where to go 90% of the time if you have any questions .

Contents - An overview page for pages on how to "Edit articles", "Gudelines", "TF2-specific Guides" and "Other".

FAQ - As this name also implies it contains answers to the most freuqently asked questions. If you're in doubt about anything wiki related take a look at the list and see if you can find your question hidden somewhere on there.

Editing - A short and sweet showcase for the most important and most used functions during editing. Definitely take a look! (I still use it from time to time :P).

Colors - Shows the color codes for several color schemes seen throughout the wiki.

Placing images - Everything you'd ever need to know about picture formats for the wiki. If you are ever required to use photos on a page I'd suggest giving it a look so you know what you are doing.

Staff members - Shows you a list of all the current Valve members, Admins, Mods and Bots. If you want to complain about everything moving at a snail's pace that's where you'll find them ;).

Moderator guidelines - Will probably never be important to you unless you 1) want to be a moderator 2) Get harassed by a moderator or 3) Actually are a moderator already (but in that case you'd probably already know all this or know where to find it, so ¯\_(ツ)_/¯).
I guess read it if you are preparing for an unofficial court case against a moderator or want to know what a moderator even does/is/whatever.

Using Maintenance templates - Maintenance templates are those things you see on a lot of pages (especially after an update), indicating there's something wrong with them (too short, outdated etc.)

Example of a maintenance template

This page basically shows you which exist, their shortcut and why/when/how to use them.

Wiki Cap - Everything relevant to the sparkly cap of justice.

Model Viewer - A guide for the HLMV (Half Life Model Viewer) which is used to manipulate Source Engine models. We use it for pictures like the ones you see in infoboxes, painted variants and galleries on cosmetic pages. If that is what you want to do you should give it a read.

Paint preview images - Documents the process of painting hats using the above mentioned HLMV:

And last, but not least:

Demo recording - How to record a demo file. Yup, nothing more, nothing less.

That was it for the TF Wiki Navbar, but before I move on to editing I have to discuss another important page: The dictionary.

(To be continued... in part 3!)
2. Finding your way around (pt. 3) - The Dictionary
Note
This is only important if you are a translator - if you want to make pictures or videos or whatevs then you will probably never have any reason to go here - just so you know!
/Note

THE DICTIONARY
So everybody who knows what the STS is raise your hand.. Now, I can't see whether you raised your hand or not, but it has a huge impact on what is written in the dictionary and why it is so essential to go there. For the uninformed: STS stands for
Steam Translation Server
and it is where all the tokens for the games are contained for translation. What is a token you ask? (Or not), well if you have ever seen the notorius "Updated Localization files" from the TF2 patch notes page and wondered what that is then I'm about to blow your mind.

A token is basically a amount of text related to either a name, description, etc. and, just like transition switching on the wiki, it allows Valve to take the translated tokens and add them to the game so players can play the game in the language they prefer (as long as that language is supported by the STS).
Here is an example of a Token for "Capo's Capper" (a cosmetic item in TF2) with 2 suggestions:

Once one of those suggestions has been accepted it will await an update to the Localization files (which follows pretty much every minor TF2 update) and once that comes it will be implemented into the game for real.

When adding translated cosmetic pages to the Tf2 wiki it is always important to keep in mind whether or not the item has gotten an official name or not (especially for languages that are really grammatically dependent on it) and so I advice to go to the dictionary where every token can be seen and added.

You can find the Dictionary by writing "Template:Dictionary" into the search bar and when you do, you should arrive at a page looking something like this:


On this page you can scroll down and find the notorious Localization files for each language:


Once you've clicked on the file for your language you should end up on a page with "recent changes" and "file history" with a ton of files under it. For standard use you should always click on the one at the top:


And that will take you to a page only consisting of text:

On this page you can see all English tokens and their respective translated Token (if it exists, if not it will only display the English one). So if you are unsure whether an item (or anything for that matter) got an official translation or not you can always come here, use Ctrl+F and search for the English token to see. (Like I do in the picture - the translated token will always be right above it).

That's the first important use of the Dictionary, but there is more. Translation Switching (which was briefly mentioned in the overview of the TF2 Navbar) utilizes strings and those strings are translated in the Dictionary.

Back on the front page of the "Template:Dictionary" page you can see two lists "List of translatable strings" and "(List of) Non-translatable strings" - the bottom ones are not too important/interesting for us translators and relate to things such as item prices, Steam IDs, item set pieces, and so on.

The translatable strings are things such as achievements, items, ranks/tiers and common words/sentences used for a lot of templates such as navbars. These are important to update regularly and considering most of the most important strings probably already have been translated for your language the ones to keep an eye out for are the "Template:Dictionary/items" and "Template:Dictionary/common_strings" tabs.

When the Localization files get an update it doesn't automatically or magically translate the item names on the site, you see... that is our job... or rather the job of the bot we've programmed to do that for us when we have added the strings.

Let me give an example on how to do this:

1. Searching
Let's say a melee weapon for the Engineer gets a new translated name from the STS and I want to add that name to TF Wiki Dictionary. First I find my way to the "Template:Dictionary/items" page and start my search for a tab that could contain the item in question:

It is important to know that "Weapons", "Engineer Weapons" and "Engineer Melee" all contain the string you will be looking for, but the more specific one (Engineer Melee) will only contain strings from the Engineer's melee weapons and therefore a lot less laggy which is really helpful (especially if you have to add more than one thing).


2. Finding and adding
Once you've found the tab click on "edit" and you will be taken to the place where you can add the strings:

Just use Ctrl+F to find the string you are looking for and add your language by using the method referred to on the page: "[Language shortcut letters]: [The translated token]". Once you've made the edits I'd advice to write a little message about what things you have added or changed in the "summary" (unless you added a ♥♥♥♥ton then just write that you added some strings for /da for example) and to click on the box to call it a "minor edit".
Then you simply click on "save page" and make the bots do their work and change the strings in all instances they appear on the site.

And you are done!

That was it for finding your way around the wiki. Now it is time for the most important stuff - editing pages, which will probably be the largest of these. Hope you're interested in continuing to read.
3. Editing - Translation
Welcome to part 3 where we'll get into the real meat of things: Editing actual pages!

Editing is the bread and butter of all translators and is an important asset to have in general.

Let's start with the basics:

3.1 TRANSLATING

One of the biggest mistakes often seen by newcomers is that they haven't read any guides beforehand which makes them unable to make satisfying edits. I myself wasn't that good at editing when I began, but quickly learned the ropes which I am here to show right now.

I will use a cosmetic item page (The Lo-Fi Longwave) as a reference and to show what the different edits do and lastly go through some shortcuts you may want to know when translating:

The first thing to do when translating is actually creating the page on which the translation will be contained. There are a lot of ways to go about this:

1. Use the language shortcut in the search bar or URL bar



2. (When already on another page of your language) click on a red link


3. Find it on the "missing translations" page we saw during the TF Wiki tour

Obviously not the most practical way if you know what you want to translate

And many more. They will all lead to a page looking like this:


And this is where the fun begins.

So to start off we need something we can actually translate; copy and paste everything from the English page onto the page you just created. If you are unsure on how to do that just follow these easy steps:

1. Go to the English page for the item and click on edit


2. Copy everything on the page


3. Paste it onto your new page


Now the translation can begin!

So right now we pretty much have an exact copy of the English page and that's no good. While you probably (or hopefully) know better than I how to translate everything to your own language there are a few things to look out for when translating like:

Links
Links are important for connecting pages and creating a more dynamic and fluid experience, but come in a few ways you gotta keep in mind. First and foremost are the links to the other pages on the wiki that looks like this in textform:



Double brackets [[ symbolize something linking to either this wiki or the normal Wikipedia. If you want to link to the normal Wikipedia you use the format:
[[w:*name of page on the Wikipedia*|*text you want to display on the wiki*]]
- Like the one in the bottom for Hard hat.

The way you translate each of these is very simple:



The Wikipedia link only works if the page it links to on the Wikipedia actually has been translated to your language. I usually just go to the page to check whether or not (mostly not in my case) the page exists in Danish. If it does I use the translation format:
[[w:*language abbreviation*:*name of the article in the translated language*|*what I want it to say on the page*]]
and if it doesn't I simply translate what it says on the page and add a {{lang icon|en}} template behind it so the reader knows the link takes them to an English page- simple as that!

This is what the template looks like on the page:

FYI: Should ONLY be done for links to other Wikipedias - links to other pages on the TF Wiki should always be in your language unless it's a English written page only (like the Help pages). It's better to have a red link than linking to an English page!

But we also have single [ links like this one:


As the text may imply single [ are for linking to pretty much everything which isn't a page on the TF Wiki or a Wikipedia article. These normally can't be "translated" as the page they link to often are websites that only displays English text, so normally you just translate the displayed text (the text after the link) and add the abovementioned template {{lang icon|en}} behind it for good measure:





The last kind of link I want to mention is the category link. Sometimes at the end of a page you'll run into a group of text looking like this:


The {{ format symbolizes templates or in this case Navbars. The [[category: format is for linking the page to a category page manually (some templates/Navbars automatically add a page to a specific category). To translate these you simply do this:



Add a /*language abbreviation* to the end of the category and leave the Navbars alone - they are automatically translated if you have updated the dictionary and/or template page.


You can see the categories at the bottom.

The next thing to mention is the Quotation system:




When translating a quotation you should do the following:





The only exception is some languages like French and German that actually do have dubbed voice lines. In their case they have to switch the sound file at the end with one from their own language.
Most voice lines can be found on the voice line pages, if those pages are not translated then just search for it via the "File:" prefix.

The last thing I want to discuss is the infoboxes:



As you can see on the picture some things are already auto-translated for you (more specifically stuff related to the dictionary), but some is not. These are the things on cosmetic pages you have to manually translate:



More generally:
  • Classes that can wear/use it.
  • Descriptions
  • Flags (mostly halloween cosmetics and untradeable items)
  • Attributes (weapons)
  • Update page links (will be under "released" if its release was with an update)
  • Availability
  • Item kind
  • 3d_viewname (on weapon pages with 3d models)
  • Reload (also on some weapon pages)

Sometimes the Availability utilizes templates (the double { format) in which case you shouldn't translate it. Sometimes it also does this:


This is mostly seen on cosmetic pages for items no longer available.

On weapon pages you can also run into this:





Auto-translated = don't worry 'bout it. Follow me to the next page :D
3. Editing (pt. 2) - Translation and adding special pages
And now to round off the translation guide I'll just briefly go over the 3 last things:

Page title:
For cosmetic pages, weapon pages or pretty much any page with a direct link to the dictionary you do not need to translate the page's title as it is automatically done, but for other pages you need to use the format:


It is easy to forget (especially since it does not show up doing preview), but try to remember it.

Main articles and See Also:
Sometimes you just know that another page on the wiki already contains tons of detail on specific subjects briefly mentioned in others, so sometimes to link those two pages together you use the main article template:





To translate those you use this formatation:





These sort of things are mostly seen on Update pages and some bigger pages with aspects from different parts of the game such as Particle Effects.

Tips and Tricks:
So lastly I want to go over a few tricks you can use. Everytime you see an update mentioned as [[*update name*]] utilize the {{update link|*update name*}} and it will automcatically translate the name to whatever it says in the dictionary and link it to the page. If you just need to update the name use {{update name|*update name*}} instead.
This is smart since you don't have to go back and change them all everytime the name gets changed in the dictionary - the bots will do all the work!

The same goes for the {{item link|*item name*}} or {{item name|*item name*}} templates which automatically translates and links item pages (which on the wiki include taunt names, weapon names, cosmetics and a wholeee lot more). I usually use it when I translate so I rarely have to go back and change anything when a new name gets added from the STS, or to the dictionary.

Examples:






That is it for the tricks, now for some tips:

  • ALWAYS use the preview button before you save a page so you are sure you didn't miss anything



  • Try to condense your edits as much as possible as to not flood the "Recent update", "page history" and "IRC chat" with unnecessary filler.
  • Don't worry about your first edits as every edit you make will be evaluated in (nearly) real time by a committeeJunta …. Cabalsitting councilof Elders Not of Zionof Administrators ... Engineers … group of people with too much free time, and they will correct it and guide you to do it correctly next time.
  • Do not let yourself get down by some constructive critisicism - we have all gotten it at some point!
  • It is a good idea to write a little text in the "summary" when you are done, so everyone can see what changed without too much effort.
  • When in doubt about what to do you can always look at the page translated to another language to see how they did it, or ask someone on the IRC channel.
  • When someone writes on your page you are adviced to keep the conversation contained to that page - do not write back on his page!

That was some tips I could think of - now it is time to move on to the next part:

3.2 ADDING
Translation is one thing, but a lot of times it is necessary to add something like pictures, videos or special pages that help with rubrication and linking associated words. Let's start with the special pages:

3.2.1 REDIRECTS, DISAMBIGUATION AND CATEGORIES

First let us discuss the redirect pages. Sometimes when you search for a word and end up a page it might say something like this in the corner:



That means "Effects" lead to a redirect page which redirected it to "Particle effects". If you click on it you can see what it looks like:


Not a lot of text as you can see.

To translate a redirect page you use this format:


All the places with /da you of course have to put in your own language's abbreviation instead.

To add a new redirect you simply have to type something into the search bar which doesn't exist



And then write the normal redirect format



Now "Piggy" will redirect to "Strange Bacon Grease". Of course you shouldn't make a million redirects for no reason, but it can still be practical to have if you want to add all your language's translated item names as redirects to the translated item page (as an example).

Another thing to note is if you see a link containing a # like this:



Then you need to put the language link in before the # and translate everything behind the #. The stuff after the # symbolizes an anchor (places you can go to via link - often placed next to titles of paragraphs) on another page, so go to the page and see how you translated it in your language - then write it after the #.

Example:
[[Mann Co. Supply Crate/Active series#Rainy Day Cosmetic Case]] - takes you to the part of about the Rainy Day Cosmetic Case on the page [[Mann Co. Supply Crate/Active series]]

If you wanted to translate that link you'd do it like this:
[[Mann Co. Supply Crate/Active series/da#Regnfuld Dag-kosmetikkasse]]
So, language abbreviation BEFORE the # and a translation of the anchor AFTER the #.

Next there's the Disambiguation pages. You could say that they are the redirect pages for buzz words with more than one page associated with it - it generally looks like this:



As you can see, every link contains a little text describing what it is and all links are listed in an alphabetically order.

You add these kind of pages the same way as before (searching for a word that doesn't exist and make a page for it), but the format is a little bit different:


The main difference is the two template lines - remember to have 'em!

And when translating a disambiguation page you also need to keep in mind that the name of the page doesn't auto-translate so you need to add it yourself - this can be done by using the aforementioned {{DISPLAYTITLE:*Name of page}} template, but can also be done like this:



Lastly we got the Category pages. These are pretty simple to translate:


It is also one of the few places where you do not need to translate the name of the page.

To add a new category you need to search "Category:*name of your new category*" and add a new page (just like we did with redirects and disambiguation pages) and use the format you see in the picture above. Afterwards all the pages that contain that category will be listed as shown here:



That's it for special pages. See next part!
3. Editing (pt. 3) - Adding Pics/Vids
3.2.2 ADDING PICTURES
Pictures are an important part of any informational website (I mean just look at the amount of pictures I've used thus far just for explaining it) so of course it is important to know how to add pictures to the TF Wiki for personal and practical use.

(FYI: This will not be a guide on how to MAKE pictures for the wiki - ask some of our local picture makers (like Nikno, Wiki Pan and Mariomaster2008 to name a few) or read up on some guides on the wiki/elsewhere.)

Now, you found a picture/gif you want to add to your profile. The first thing you do is clicking on the Upload File tab on the sidebar or type "Special:Upload" into the search bar.

Once you are there you have all the information you need at the top, but here is how it is generally done (for user pictures/gifs):



Things like item pictures and painted cosmetic pictures generally have a logical structure for file names, but I won't go into detail about that here.

To show a picture on a page you used this structure:



You can do a lot else with a picture and I already showed you a page on which you can see most of the ways to format a picture - so go read that if you want to.

3.2.3 ADDING VIDEOS
Likewise, Videos are a huge part of the TF Wiki and constantly need to be updated with every weapon rebalance/addition. The most notable member of the video making side of the wiki is probably Karmacharger who has his well known youtube channel where he still makes weapon demonstrations.

If you want to make videos I advice you to go the Weapon Demonstration Project page and take a look - there's way too much to mention to add it all here. If you are still unsure you can ask on their talk page or get help from some of the other video makers.
3. Editing (pt. 4) - Updating
3.3 UPDATING
Due to the nature of a 10 year old game it is really rare for an article to remain the same way all the way through. New stuff is discovered and added and old stuff is changed or removed with every passing update. Therefore it is important to keep the pages up to date with the newest information. I will focus on the two main things that need to be updated with every passing update: Pages and templates - we'll start with pages:

3.3.1 UPDATING PAGES
This is how an initial page looks when a new item is added:


And without the pictures, too - pretty laconic, eh?

All the information available is all the information we can showcase in the beginning, and from there we just build on top of it. (This also the kind of page you should make if you want to make an initial page).

Some things to keep in mind when adding to a page:
  • It has to be written formally and informatively.
  • If you refer to something (like a hair style, character from another game, etc.) then remember to add a Wikipedia link.
  • If you want to link to something else on the TF Wiki then make sure the link hasn't been used already on the page nearby.
  • If you want to add Bugs/Trivia then read through their Style pages first (or just read the "in a nutshell" at the start of the Style pages).

Okay, let's say an item recieves a bug fix. In that case you have to do two things:

1. Add the bug fix/change to the Update History:


Just use the same formatting as seen above and you should be fine (just make sure to get the date right).

2. Remove the bug from the bug list


Not all items have bugs fortunately.

If an item receives a new style you also have two other things you need to do (you always gotta update the Update History so I won't count it):

1. Add a "style box" on the page



All the |style1/2/3/* - just needs to be called what the new style is called, simple as that.
As for the |image1/2/3/* - As you can see there is a logical way to file the names of the pictures "RED Batter's Helmet No Hat.png" so "*team color* (pretty sure we always use RED for Style pictures if that is the case - if it is a style that changes something paint related it is often replaced with 'painted') *name of the hat* *name of the style*.png" - so in a way you CAN predict what a picture will be called and add it before it is even ready. Just look at the name of some other Style pictures when in doubt - that's what I do.

2. Add the painted variants box for the style




In this case it is even easier - just use the format above and use the official name for the style.

If a cosmetic item goes all class then add the remaining class photos under gallery:


Also a simple format as you can see.

You are also free to add graphs or other fancy things to articles if you feel they're missing something or if you feel it would add to the page. To use an example: I added this to the Uber update page because I noticed it was missing and thought it would add a little to it:



Just remember to use the same style as the other stuff on the page (if it has any).

3.3.2 UPDATING TEMPLATES
This will be a little harder to describe as there are a million and two templates on the site, but the general rule of updating that I use is the following:

  • Look at how the others have been formatted and do the same.

If you do that you shouldn't be too lost.

Templates that often need an update/addition include:
  • The Navbar for things such as cosmetic items, tools/action items, updates, classes etc.
  • Every template relating to cosmetic items, pretty much.
  • This include "item styles", "list of items with Jiggle bones", "List of items with Self-illumination" and so on and so forth.
  • The list of tools
  • The list of taunts
  • The list of active/expired promotional items
  • Item quality lists (especially for Strange)
  • Reskin list

Just to name a few. You'll learn pretty quick when to update what and why. Of course you can also just add something because the template is either missing something or is incomplete - you do not have to wait for an update always.

I will only show how to add items to Hat Nav template (as that is the most common Template update stuff I can imagine). So let's say a new All-class item gets added called the "Cold Shoulder" and I want to update the Navbar for cosmetic items:

First I need to get to the Template edit page which can be found in one of two ways:

1. Clicking on the small "e" in the top left corner of the Navbar (most templates have this as a shortcut for "edit")



2. Writing "Template:Hat Nav" in the search bar

Once you are on the editing page for the Template search for the place it mentions "all class"



Then go down to the bottom (as items are ordered after class and release date):



And now you see the thing about following the structure of the Template because even if you have no idea what anything means you can still see a pattern and that should allow you to make the edit properly





There it is! Just without proper text since it isn't a real item and therefore not in the dictionary. It is the same for every item, it just needs to be filed differently for different classes.

Other Templates (especially those with lists) need a little more editing than this, but as I already showed you: Follow the patterns and everything will be fine.

And if you are really lost you can ask someone on the IRC Channel.

That was my small editing tutorial - I hope you learned something new. I am not quite done yet, though as there is still one more topic to discuss:

The Wiki Cap.

So read the next part if you are interested in some general information on how its distribution goes down.
4. The Wiki Cap
Welcome to the final part of the Tf2 wiki guide where I will talk about the infamous, sparkly and highly sought after Wiki Cap. To you who haven't heard of it before, it is basically a cosmetic item handed out to those who are regarded as valuable members of the tf2 wiki team. (It is also the only cosmetic item with the Community quality - as far as I know of).


My very own Wiki Cap

The process that determines who gets it is a sort of nomination based voting system:
You can nominate others you find qualified for the Wiki Cap and once they have been nominated the admins or mods have to agree to the nomination. If the nomination reaches 5 yes votes it will go through and the player will be awarded with the cap, if it reaches 5 no votes it will be declined for the time being. You can nominate the same person again and again, but it is better to wait a month or two before re-nominating someone.

You can read more about it here.

Now I have my own two cents I want to share

4.1 HOW NOT TO GET A WIKI CAP
It is no secret that a lot of people come to the wiki in order to get the Wiki Cap, but seeing as how the only guide thus far is about 4 years old, it might give a false sense of progression. So let me set some things straight.


Guess what month the Wiki Cap got released ;)

First of all: There is no set amount of edits required to get the Wiki Cap.

You can easily get hundreds of edits creating stuff like redirects and translating 8 year old patch notes, but we value what each edit has done instead of the amount. Don't forget that no matter if you translate a 200k byte page or change a single letter in sentence - both counts as one edit. So if you expect to get the Wiki Cap by casually translating small pages, making redirects and fixing small grammatical errors for 2 weeks then I am sorry to disappoint you.

Tl;dr - It is not about the amount of edits, but what the amount of edits represent/have been used for.

Second of all: Going for the Wiki Cap with no interest in the Wiki itself is hard.

You know that feeling of getting dragged along to do something you do not really want to do at all? Like playing sports when you'd rather just stay at home and study or game all day? Yeah, the wiki works in the same way. It takes HUGE dedication and a lot of time to really get going and if you are not up for the ride then I am afraid you need to be really stubborn or else you are gonna burn out in a matter of weeks at most. You are of course welcome to make an account and do some small changes you think are necessary and leave again - noone says you have to work towards a Wiki Cap (or anything for that matter), but if you are only there for the cap, then I wish you nothing but good luck getting that far.

Tl;dr - Working on the wiki for the Cap alone is tiredsome and will burn you out if you do not enjoy working the wiki in the first place.

Also: Do not feel entitled.

You may sit there and think you are qualified for the Cap, but until someone nominates you, it is all but in your head. You can improve your chances by being proactive in the community and joining in on some conversations (getting yourself known around these parts), but please refrain from going on long drawn out rants and get impatient for no reason - I can tell you right now: That won't improve your chances in the slightest.

Tl;dr - As it is stated on the nomination page: "The Wiki Cap is not a right. It is a privilege and reward for useful contributions."

Next: It takes time.

It takes a lot of time. To put it into perspective: I got my Wiki Cap in about 7-8 months and that is actually quite fast. If you expect to use less than half a year then you better have a lot of spare time or a lot of creative, innovative and crazy changes ready for the Wiki. Again: There are no time limit, no minimum/maximum edit count and no real "set-in-stone" way to get it, you just have to be a good asset to the team, and you can take all the breaks you want to - your edits do not go anywhere.

Lastly: Don't give up

Doing anything for the first time is hard. Life is a journey on which you do nothing, but learn how little you actually know. But even though you might feel disappointed or unknowledgeable you shouldn't throw a towel in the ring because someone gave you some constructive advice. If every goal you ever set in life got completed without trouble and without hardships, it would be meaningless; a goal is only a goal because we have to challenge ourselves and focus hard to reach it; what is quest without a journey? So - if you are interested in working with us then just remember: Everything will make sense eventually and you can't make an omelet without breaking a few eggs

So in conclusion, the way to NOT get a Wiki Cap is by being:
  • Impatient
  • Entitled
  • Taking quantity over quality
  • Too focused on the Cap itself (unless you have incredible amounts of dedication and "stubbornness")
  • Staying uninterested in the Wiki itself and the community within it
  • And last but not least: Giving up

4.2 THE WIKI CAP'S SYMBOL
Lastly I just want to acknowledge all the controversy surrounding the Wiki Cap and, by extension, the Wiki itself.

For the uninformed here is the short version:
Back in 2014 some users discovered and reported a devistating bug (a bug that could've ruined the economy of Tf2) that basically made it possible for Giftapults to be used as keys on Crates. In the good ol' days Valve gave out a free, untradable unusual hat of your choosing (before it got replaced by the Finder's Fee in 2015) and one of the players choose a Sunbeam Wiki Cap. That led to a debate between him and the tf2 wiki and long story short he ended up having to rechoose his chosen Unusal and he got a Burning Flames Max's Severed Head instead.

I wasn't around back then, but the incident seemed to have left a bad taste in everyone's mouth and to this day you can't mention the Wiki Cap on r/tf2 without someone bringing it up. I can see both sides of the argument, but I hope you can understand that the Wiki Cap means a lot to us. We give it out to people we want to represent our community, our strides and our work effort, and I guess it was too much to watch someone else get it, albeit different, just for what it symbolizes and means to US. You might not agree with the decision, and that's fine, but it is what it is.

Now what I can't understand is the rumors that the admins or mods are some kind of evil, patronising and stigmatizing group of individuals who do nothing but berate you - I can tell from my experience that it is a complete and utter lie. I have been with the wiki for some time now and I have never witnessed or been a victim of any sort of descrimination or unfair treatment - even when I was at my worst! I am almost certain that people whining about unfair treatment probably did something aggresive to deserve a harsher choice of words, or were so riled up that they took things harsher than they should. I still chat to a lot of the Wiki workers and I promise you nothing, but good friendships/relationships and karma if you decide to join us.
Epilogue
I hope you could use this guide for something; it surely took a lot of time to create. If anything I hope you just learned something new to traverse the wiki with or got a new insight into something you only ever saw through a peephole before.

Before I leave you all I just want to say two things:

1. If you ever need help with anything related to the wiki or have any more questions (that are not related to making photos or videos) you are free to befriend me on Steam and leave a question. I am sure a lot of other Wiki workers feel the same way. Never be afraid to ask!

2. Thanks for reading, and have a good day/night/afternoon/whatever!
< >
19 Comments
Grampa Swood Dec 24, 2018 @ 2:39pm 
:)
Faghetti | RSP  [author] Dec 24, 2018 @ 2:09pm 
:(
Grampa Swood Dec 24, 2018 @ 8:21am 
reported
Faghetti | RSP  [author] Dec 24, 2018 @ 6:04am 
Noob :^)
Grampa Swood Dec 23, 2018 @ 11:12am 
Instructions unclear, wiki cap in blender oh god ho fuck
Faghetti | RSP  [author] Aug 30, 2017 @ 3:18am 
Thanks, man :)
Anyar Aug 29, 2017 @ 11:27am 
Pretty darn good guide.
InsaneHype Jul 26, 2017 @ 11:05am 
This is a guide about a guide = guide-ception
Faghetti | RSP  [author] Jul 26, 2017 @ 8:58am 
Oh, thanks :D Glad you liked it!
✔AL-Friansyah Jul 26, 2017 @ 8:37am 
nice, because ur a good writer m8, i like ur guide :resmile: