Mkwtas wiki:Article guidelines

The following are guidelines for various aspects of writing article content on this wiki. These should always be followed when creating or editing a page.

General style

It is important that there is a consistent level of quality and formality on the wiki. Without such consistency, this wiki cannot become the resource we hope for it to be.

• Do not include false information! Always confirm with other users that everything in your article is correct.
• Use proper grammar, spelling, and English writing conventions. If you are unfamiliar with proper grammar, you should either learn it or put suggestions for articles in Discord.
• Use conventional Wiki/Wikipedia style conventions. Please read the Wikipedia Manual of Style.

Wikipedia conventions

• Make the title of the article, the title of the current subsection, and any synonyms bold the first time they are mentioned only. This should only be in the opening paragraph.
• Only link to other articles once. If the subject is mentioned again, don't link it unless the article you're writing is very long and it has been a while since the last link.
• Be as concise as possible! However, don't sacrifice information for concision.

Other notes

• Use proper capitalization in title names. Follow the Wikipedia guidelines on titles. Note that article titles, as well as section headers, should be in sentence case.
• Know when to use an en-dash "–" or em-dash "—" in place of a hyphen "-". These can be found in all parts of an article, so is important to be able to differentiate.
• It is not necessary to specify that something is a part of Mario Kart Wii since everything on this wiki is centered around Mario Kart Wii.

Layout

Some common types of articles have their own standard layouts, which should be followed when creating or editing an article of such a type. As the wiki expands, new information may be deemed useful to add, so what is listed below is not exclusive.

For tracks

• Lead section: The name of the track in bold and its location in the cup selection go first. Then, if it is a retro course, its original appearance. If it is a custom track, its author(s) and creation date. Lastly, if it has any, a fact about the track's significance.
• Infobox: TBD
• Overview: A summary table of the current TAS BKTs, followed by the general features of the track's categories - types of glitches, 3lap/flap viability, existence of runs). Each category with a TAS should get its own subsection, starting with an overview of the route, and then a step-by-step breakdown of the TAS itself. The encode of the TAS should also be linked.
• History: Discuss the history of all strat developments. For tracks with more progression, break into subsections. Devote subsections to specific eras or breakthroughs. Leave one subsection for features of the track in events such as TAS competitions.
• Future: One subsection each for known and potential timesaves, broken down further by each category. Unpublished or WIP runs are mentioned here.
• References: Cite sources! If you are unsure what to include as references, videos from YouTube are the best candidates. When linking to Discord, use a message link, and include the server invite where possible. Avoid expiring links, such as Streamable.
• Navbox: Use Template:Courses

For tech

• Lead section: The name of the tech in bold, and a more general description of the type of tech, its purpose, and how it is performed. If necessary, break into multiple sentences. Then, any other general information worth noting about the tech.
• Infobox: Use Template:Infobox strat
• History: Discuss the history of the tech's utilisation in TASes. For tech with more progression, break into subsections. Devote subsections to specific eras or breakthroughs. For basic game mechanics, this section may be omitted.
• Technical description: Discuss how the tech works in more precise detail. If necessary explain or link to relevant related concepts that are important to understand the tech. For more complex tech, break into subsections.
• Relevant code: Include small extracts from Kinoko or another decompilation source as appendices to the previous section.
• Variations: Discuss any variations to the tech here. Only include variations if they are widely considered a subset or separate tech.
• Optimizations: Discuss any optimizations or major breakthroughs made in the tech here. Try to avoid overlap with the History section. This section should contain more technical descriptions, with the History section focused on the progression from one breakthrough to another.
• Applications: A summary table of all applicable categories for the tech, followed by a list of notable strats the tech is used in, and a list of custom tracks the tech is used in TASes on. For basic game mechanics, this section may be omitted.
• References: Cite sources! If you are unsure what to include as references, videos from YouTube are the best candidates. When linking to Discord, use a message link, and include the server invite where possible. Avoid expiring links, such as Streamable.

For people

As not many articles concerning people have been written, this type of page is yet to be standardised. Please discuss in the Discord if you have any ideas or questions about creating or editing this type of article. If in doubt, follow the Wikipedia guidelines on biographies.

• Lead section: TBD
• Infobox: Use Template:Infobox taser or Template:Infobox user

For lists

As not many list articles have been written, this type of page is yet to be standardised. Please discuss in the Discord if you have any ideas or questions about creating or editing this type of article. If in doubt, follow the Wikipedia guidelines on stand-alone lists.

• Lead section: TBD
• Infobox: List articles should not need infoboxes.

For tasks

• Lead section: The name of the task in bold and its location within a year of TAS Comp and overall go first. Then, its running time and, if applicable, the date of the results stream. Then, list the credits for task creation and hosting details. Lastly, if applicable, state any details about collaboration with CT Jams or MGTC. In a separate paragraph, list the three medallists, and the number of submissions.
• Infobox: TBD
• Task: A direct quote of the task message goes first. Then, a section devoted to the creation of the task, followed by a section devoted to its release and initial reception.
• Results: A table listing the results of the task goes first. Then, if applicable, a section devoted to the results stream, followed by a section devoted to the results video. Links should be provided for both.
• Legacy: If the task holds any significance to the competition as a whole, describe its legacy here. Examples include; a turning point for activity, a debut task concept, a prime group of competitors, or the catalyst of a change in policy.
• References: Cite sources! If you are unsure what to include as references, videos from YouTube are the best candidates. When linking to Discord, use a message link, and include the server invite where possible. Avoid expiring links, such as Streamable.
• Navbox: Use Template:Navbox MKWii TAS Competition