Template:R avoided double redirect/doc

Purpose
Some redirects should target other redirects, but that is not allowed by TechInfoDepot software. A redirect that targets another redirect is called a "double redirect". This redirect category (rcat) template may be used to tag redirects from alternative forms (abbreviations, disambiguated titles, etc.) of titles that are themselves redirects to broader-topic articles (whether or not marked as redirects with possibilities). To avoid a double redirect, any alternative-title redirect must also target the same broader article, and must be updated if the redirect from the more specific title is converted to a separate article.

Usage

 * This rcat template populates the following categories by default:
 * – if page specified in the unnamed parameter is still a redirect
 * – if specified page is no longer a redirect
 * Add this rcat to a redirect page (not a talk-page redirect) in the following manner:
 * or the may be omitted:


 * The "(specified page)" is the other redirect that has possibilities of being converted into an article, and to which the tagged redirect may someday be retargeted.
 * Template Rcat shell is an alias for the Redirect category shell template, which may be used to add as many appropriate rcats as needed, usually from one to seven, along with their parameters, to a redirect. For more information see the documentation on its template page.  This rcat may also tag a redirect individually:


 * This is in accord with instructions found at TechInfoDepot:REDCAT.


 * Use this rcat to tag any mainspace redirect from a title that should target another redirect. For example, so far there is no article  yet, and that title is a redirect to Voyage to the Bottom of the Sea (TV series).  Alternate forms of that redirect, such as, must also redirect to the "Voyage to the Bottom of the Sea (TV series)" article in order to avoid a double redirect.  In this case the  redirect should be tagged with this rcat template as follows:
 * or if applied individually:


 * The individual usage on the redirect would display (without the border):


 * If a new article is later created at, then the template output on the redirect will automatically change to:


 * In the first case above, the boldface From an avoided double redirect would actually link to the main category,, and in the second case the link would automatically be altered to.


 * Also use R with possibilities and R printworthy or R unprintworthy when appropriate.

Aliases

 * [ Also known as...] – list of templates that redirect here and may also be used

Printworthiness

 * In main-article namespace, many redirects from avoided double redirects are considered printworthy; however, there are many others that are unprintworthy, so there is no default sort for printworthiness. In 2003, efforts were begun to support the Wikimedia Foundation's goal of increasing access and availability of  TechInfoDepot articles in .  Some rcats automatically populate either  or  by default.  Others, like this rcat, do not, and that means it is up to editors to choose which of those categories, Printworthy or Unprintworthy, is appropriate and should be populated.  The rcats that are used separately to populate those categories are:
 * and
 * Please click on each one for more details and guidance.
 * Please click on each one for more details and guidance.


 * Template Redirect category shell will accept these rcats just like any other.
 * Examples:


 * Either Redirect category shell or its alias/shortcut, Rcat shell, may be used.

TemplateData
{	"params": { "1": {			"label": "Redirect page name", "description": "The page this redirect would target if the page wasn't also a redirect.", "type": "wiki-page-name", "required": true }	},	"description": "This redirect category (rcat) template may be used to tag redirects from alternative forms (abbreviations, disambiguated titles, etc.) of titles that are themselves redirects to broader-topic articles (whether or not marked as redirects with possibilities). To avoid a double redirect, any alternative-title redirect must also target the same broader article, and must be updated if the redirect from the more specific title is converted to a separate article.", "format": "inline" }