SmashWiki:Redirects: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
(→‎Bad redirects: ick. Did I even proof read this? (sadly yes, also thanks for pointing out the capitalism thing. I don't really want to pay for this policy.))
Line 14: Line 14:


==Bad redirects==
==Bad redirects==
*'''Misspelling and capitalization redirects''': Redirects are not to be used to idiot-proof this wiki. Additionally, capitalization redirects are pointless because any SmashWiki search will automatically fix any capitalization mistake made, if a match is found.
Redirects should not be used...
*'''When the article's subject's name has an obscure or previously unknown alternate term''': If you don't think too many people know the article's subject by a certain name, that probably means that you shouldn't create a redirect from that title.
*'''for misspelling and capitalization redirects''': Redirects are not to be used to idiot-proof this wiki. Additionally, capitalization redirects are pointless because any SmashWiki search will automatically fix any capitalization mistake made, if a match is found.
*'''When the article already has many similar redirects''': The goal is not to over-saturate articles with pointless redirects that no one will use. Creating different "versions" of redirects to the same article is generally not helpful.  
*'''when the article's subject's name has an obscure or previously unknown alternate term''': If you don't think too many people know the article's subject by a certain name, that probably means that you shouldn't create a redirect from that title.
*'''When the redirecting title could apply to more than one article''': In this case, a disambiguation article is the way to go, where all articles that the subject could be referencing art listed out and linked to.  
*'''when the article already has many similar redirects''': The goal is not to over-saturate articles with pointless redirects that no one will use. Creating different "versions" of redirects to the same article is generally not helpful.  
*'''Images, templates, and talk pages''': These should generally not have redirects made to them, although there are a slew of exceptions.
*'''when the redirecting title could apply to more than one article''': In this case, a disambiguation article is the way to go, where all articles that the subject could be referencing art listed out and linked to.  
*'''Redirects to other redirects''': Called a double redirect, usually this is a mistake or a result of moving an article. It can be rectified, usually, by simply redirecting the offending redirect to the target article.
*'''on images, templates, and talk pages''': These should generally not have redirects made to them, although there are a slew of exceptions.
*'''on other redirects''': Called a double redirect, usually this is a mistake or a result of moving an article. It can be rectified, usually, by simply redirecting the offending redirect to the target article.

Revision as of 22:12, April 20, 2017

Template:Proposed policy

Proposed.png
This page is a draft.
Feel free to contribute to this page as you would a mainspace page.

Redirects are pages that automatically transfer users to their targets. To create a redirect, one need only use the following code: #REDIRECT [[<target article>]]. They can be accessed and used either by using the search bar or by links.

Redirects need to be used constructively and not haphazardly, nor unnecessarily.

Good redirects

Redirects should be used...

  • When the article's subject is also known by other names (officially or otherwise): The most obvious one, when something is known by more than one name, the most common name should house the content, and the other name(s) should redirect to that article. While alternative (yet official) names should always get a redirect, unofficial names should get a redirect only if they are well known enough (This, however, does not extent to unofficial move names).
  • When the article's subject's Japanese name differs from its English one.
  • When the article's subject's internal name (if applicable) is known: If a character, stage, move, item, technique, etc is known by its internal name (via debug menu or data mining) that name should be redirected to the subject.
  • When the article's subject's name has a popular shortening, abbreviation, or acronym: Good examples: SSB, PM, DI, KB, ICs, DK; Bad examples: RttF (Race to the Finish), TS (Title Screen), SIC (Squirtle Ivysaur Charizard).
  • When the article's subject has a section that may be searched for or linked to: In this case, use the following code: #REDIRECT [[<target article>#<section>]]. The redirects title should usually be the same as the section's title.

Bad redirects

Redirects should not be used...

  • for misspelling and capitalization redirects: Redirects are not to be used to idiot-proof this wiki. Additionally, capitalization redirects are pointless because any SmashWiki search will automatically fix any capitalization mistake made, if a match is found.
  • when the article's subject's name has an obscure or previously unknown alternate term: If you don't think too many people know the article's subject by a certain name, that probably means that you shouldn't create a redirect from that title.
  • when the article already has many similar redirects: The goal is not to over-saturate articles with pointless redirects that no one will use. Creating different "versions" of redirects to the same article is generally not helpful.
  • when the redirecting title could apply to more than one article: In this case, a disambiguation article is the way to go, where all articles that the subject could be referencing art listed out and linked to.
  • on images, templates, and talk pages: These should generally not have redirects made to them, although there are a slew of exceptions.
  • on other redirects: Called a double redirect, usually this is a mistake or a result of moving an article. It can be rectified, usually, by simply redirecting the offending redirect to the target article.