Mkwtas wiki:Article guidelines: Difference between revisions

Line 32:

* '''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]].

* '''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.

Line 58:

Line 59:

* '''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]]

@@ Line 32: / Line 32: @@
 * '''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]].
+* '''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.
@@ Line 58: / Line 59: @@
 * '''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]]