Call of Duty Esports Wiki:Tutorial/Writing Bios
The first part of a biography should be personal history. Generally include where the player is from, how they got into Call of Duty, and anything else relevant - for example, if they started college and then took time off to play professionally, or if they previously had a job, or if they moved, you would include facts like that.
Somewhere in the first sentence of the biography, you should include First Name "Alias" Last Name (if relevant, e.g. for Korean players, you would reverse given name and family name). After this first reference, if you use their name again instead of pronouns, it should be their last (family) name.
Call of Duty Career
Break the Call of Duty career into years based on the game that was played competitively at the time - Black Ops 1, Black Ops 2 , Black Ops 3, etc. Once the Call of Duty Career starts, refer to all players, including the one who the article is about, by their aliases. This switch is to reduce confusion.
Describe all roster swaps and role swaps. Also list major tournament results. Give context, but not too much -- for example, it might be worth mentioning in Karma's biography that compLexity Gaming won the Call of Duty Championship 2014 defeating Team EnVyUs 3-0, but it's not worth mentioning in detail that they went 3-0 in groups, defeating VexX Revenge, Team Orbit, and AllStars, then beating TCM Gaming 3-0 in the round 1, Xfinity 3-0 in round 2, FaZe Clan 3-1 in round 3, OpTic Gaming 3-2 in winners finals, and then finally Team EnVyUs 3-0 in the grand finals is too much. That much detail should be reserved for a team bio. However, if there was a major rivalry, it might be worth mentioning. For example in Clayster's biography, you might mention that his team beat NaDeSHoT's team 3-2.
If another major event occurred that impacted the player's career in any way, you would include that too. For example, the fact that ACHES was briefly banned from Season 3 of the MLG CoD League, or that he played with an injured hand at MLG Columbus Open 2014. It's not worth including as a major event that NaDeSHoT hosted an AMA, though the link to that AMA would be listed in the Interviews section.
Writing should be as encyclopedic as possible. Sentences should be to-the-point but still grammatically correct. Paragraphs should be between one and five sentences long; try to avoid paragraphs longer than five or six lines. If you have trouble writing in this style, do the best that you can. If English isn't your native language or you feel very uncomfortable writing biographies, contact us!
Add references where possible. The code for a reference is:
Put that at the end of the sentence that you are providing the reference for, and the wiki will automatically order your references and place them in the References section at the bottom of the page. If possible use a link to the site you're referencing with the page title. If the language isn't English, make note of that. For example:
<ref>][http://www.facebook.com/entus.progaming/photos/656254761139114 CJ Entus's Facebook Post (Korean/English)] ''facebook.com''</ref>
Here's the proper capitalization and phrasing for roles when written out:
|Clayster is an Anchor.|
|Octane is an AR slayer.|
|Scump is a SMG slayer.|
|MiRx is an Objective player.|
|Karma is an Support player.|
|Parasite is a Flex player.|
- A bulleted list of things that don't fit well into the biography.
- If possible, should be time-insensitive. Don't say "Favorite map is Freight," say "In 2014, favorite map was Freight."
- Each piece should end in a period.
- "Enjoys to anchoring" rather than "He enjoys to anchor."
- No required order, but try to order everything so that it makes sense.
Look at an example.
For all external content, if there's a large number (at least 10) pieces of content, it should be divided up into collapsible NavFrames, with one per year:
<div class="NavFrame collapsed" style="width:900px;max-width:100%"> <div class="NavHead" style="background-color:#EEE; border:1px solid #AAA">Click [show] on the right to view</div> <div class="NavContent" style="text-align:left"> [Content goes here] </div> </div>
We don't really have notability guidelines for articles / interviews / videos - feel free to link your own content! However, all content linked must be appropriate and relevant to the player. News articles do not belong in this section and should only be used as references. While we are okay with you linking your own content articles, do not replace an existing reference with a reference to your own site for any news posts (unless your site is without question a more accurate source - for example, it would be appropriate to replace a reddit speculation thread with screenshots of a player's stream with a link to an Dexerto article).
The NavFrames described above should be divided by year. So there'll be a level-3 2013 heading, then a navbox, then a level-3 2014 heading, then a navbox, etc.
Within each navbox (or outside of the navbox), content will be in a bulleted list.
- November 3rd - Title of Content - from esports.gamepedia
- December 10th - Title of Content - from esports.gamepedia
- Date - Link to content displayed as the Title - italicized from and then the link to the content creator's homepage displayed as their name
For Vlogs, it's just the player's vlog, so you wouldn't list a content creator. Same for blog posts. (Vlog = video log = video content, Blog = weblog = written content)
Please do include the date of the videos' creation here, even though a lot of our highlight videos don't. Try not to spam too many links here, but it's fine to put popular highlight videos in this section.
Only non-time-sensitive links should go here (e.g. a link to a player's LoL eSports bio) Interviews, Articles, Vlogs, etc should not go here! Those are the most relevant at the point of creation; this is for links that are always equally relevant. News items should be used as references in the biography above.
(Obviously in 5 years the link may not be relevant. But the idea is to link more long-term things here.)
Automatically created with form and filled out when you use references above.