Template:R with possibilities

When used inside the {{Redirect category shell}} template:

When used by itself:

• With possibilities: This is a redirect from a title that potentially could be expanded into a new page such as a new template. The topic described by this title may be more detailed than is currently provided on the target page or in a section of that page.
  • When the target page becomes too large, or for any reason a new page would be an improvement, this redirect may be replaced with an article, template or other project page that is carved out of the target page. See also {{R to section}} and use together with this rcat when appropriate.
  • If the topic of the redirect is not susceptible to expansion, then use other rcats such as {{R to section}} or {{R to list entry}} when appropriate.
  • Since a new page may be created, links to this redirect should not be replaced with a direct link to the target page. To make redirects to this page, use {{R avoided double redirect}}.
  • {{R printworthy}} should be used together with this template when applied to a redirect in mainspace.
  • When used on a template redirect, it will automatically populate Category:Template redirects with possibilities.

Template documentation follows
Note: the template above may sometimes be partially or fully invisible.
Visit "Template:R with possibilities/doc" to edit its documentation if it is available. (How does this work?)

Usage

Use this rcat template in any namespace.

• Use this redirect category (rcat) template for any redirect that, in your opinion, may stand alone as an article on a notable subject or a template. If you see a redirect with this template, and you are moved to write the article, then be BOLD!
  • For guidance on how to start a new page from a section, please see Wikipedia:Summary style. It is important that the topic is notable in accordance with the guideline, and that the article is structured in line with the manual of style; otherwise there is a possibility the article will be re-merged and turned back into a redirect.
• Apply this rcat to a redirect in the following manner:

#REDIRECT [[(target page name)]]

{{Rcat shell|
{{R with possibilities}}
{{R printworthy}}
}}

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:

#REDIRECT [[(target page name)]]

{{R with possibilities}}

This is in accord with the instructions found at Wikipedia:REDCAT.

• If a redirect in template namespace is tagged with this rcat, then Category:Template redirects with possibilities is populated.
• If a redirect is in categoryspace, then use {{R category with possibilities}} instead of this rcat.
• If a redirect is in any other namespace, then this rcat populates Category:Redirects with possibilities and,
• When a redirect is in the main-article namespace (mainspace), Category:Printworthy redirects is also populated by default. In 2003, efforts were begun to support the Wikimedia Foundation's goal of increasing access and availability of Wikipedia articles in printed versions. Mainspace redirects that may become articles someday are suitable for a printed version of this encyclopedia. In other words they are printworthy.

• Note: It is possible that a redirect from a misspelling may also be the correct spelling of a different subject with possibilities. An example is Jim BlytheJim Blyth. However, do not intentionally link to redirects from misspellings. Use a disambiguated title such as Jim Blythe (author), until the possibilities of an article about the author are actually realized. See {{R typo}} for more information.

Draft articles

When a draft exists in draftspace, this rcat will sense it and notify anyone who reads the redirect page with the following:

• This is a redirect from a title that is in draft namespace at Draft:(name of page), so please do not create an article from this redirect (unless moving a ready draft here). You are welcome to improve the draft article while it is being considered for inclusion in article namespace.

The following category will also be populated:

• Category:Redirects with draftspace articles

The text and category only appears if there is an actual aspiring article in draftspace. If the page in draftspace is only a redirect or has zero content, the message will not display.

Aliases

Please note that common misspellings can also be useful redirects.

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

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. See a monthly parameter usage report for Template:R with possibilities in articles based on its TemplateData.

TemplateData for R with possibilities

Places the redirect in [[Category:Redirects with possibilities]], indicates that the redirect could be turned into a full article. This template takes no parameters.

Template parameters[Edit template data]

Parameter		Description	Type	Status
No parameters specified

Links to redirects tagged with this template

If a page wikilinks to a redirect tagged with this template, do not replace it with a direct link to the target page, as a more specific article may be created on the (currently) redirecting page. However, redirects targeting a redirect with possibilities should be changed, as they violate the WP:2R policy, and should then be tagged as {{r avoided double redirect|<!-- name of r with possibilities -->}}.

User script for highlighting links to redirects with possibilities

To highlight links to redirects with possibilities with a red dashed border, first add this code to your common.js:

mw.hook( 'LinkClassifier' ).add( function ( linkClassifier ) {
    linkClassifier.cats['redirect-with-possibilities'] = [ 'Category:Redirects with possibilities' ].sort();
} );
mw.loader.load('/w/index.php?title=User:Anomie/linkclassifier.js&action=raw&ctype=text/javascript'); // Backlink: [[User:Anomie/linkclassifier]]

Then, in your common.css, add this code (or similar code if you'd prefer a different styling):

a.redirect-with-possibilities {border: 1.5px dashed #d33;padding: 3px;} /* Add red border around redirects with possibilities */

See also

• {{Disambiguation with potential}}
• {{R category with possibilities}}
• {{R from alternative name}}
• {{R to decade}}
• {{R from misspelling}}
• {{R to related topic}}
• {{R from subtopic}}
• {{R to subtopic}}
• Wikipedia:Your first article

• WikiProject Redirect/Style guide

Template:R with possibilities invokes Module:Navbox using Lua.

Usage

This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.

The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.

Syntax

{{navbox
|state      = uncollapsed, collapsed, plain, autocollapse (default)
|name       = mandatory - name of the template
|style      = optional - style for the whole table
|title      = mandatory - navbox header
|gtitleN    = optional - title of N-th group of items
|styleN     = optional - style for groupN; i.e. text-align
|groupN     = mandatory - list of groups of items
|fstyle     = optional - style for footer ; i.e. text-align
|footer     = optional - navbox footer
}}

• Groups: Currently there is no technical limit to the maximum number of groups.
  • Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
• Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
• Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
  • Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
• Line breaks: Line-breaks (<br />) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN.
• Bullets: Create unordered lists with lines beginning with *.
• Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! ({{!}}).

States

• Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
  • Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
• Uncollapsed: Forces the navbox to be displayed.
  • All of the navboxes in this documentation are in the uncollapsed state.
• Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
  • Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
• Plain: Removes the "show/hide" link.

Sub-groups

• For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
• To create sub-groups within {{navbox}}, certain parameters are to be included:
  • The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
  • The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.

{{navbox
|name    =
|title   =
|gtitle1 =
|group1  =
|gtitle2 =  
|gtype2  = Subgroup (mandatory)
|group2  = 
  {{navbox
  |subgroup = yes (mandatory)
  |gtitle1  = 
  |group1   =
  |gtitle2  = 
  |group2   = 
  }}
}}

Collapsible sub-groups

• For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
• To create collapsible sub-groups within {{navbox}}, these parameters need to be included:
  • The parent navbox is almost always uncollapsed (state=uncollapsed).
  • The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
  • The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
  • The nested collapsible navbox is forcefully collapsed (state=collapsed).

{{navbox
|state  = uncollapsed
|name   = 
|gtype1 = Subgroup
|group1 = 
  {{navbox
  |collapsible = yes
  |state   = collapsed
  |title   = 
  |gtitle1 = 
  |group1  = 
  |gtitle2 = 
  |group2  = 
  }}
}}

Use of images

• The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
• Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.

Link and file share the same name

{{plink|Item}}

File name differs from the link

{{plink|Item|File}}

Link and file share the same name, but different text is desired to display

{{plink|Item|alt=Text}}

File name differs from the link and different text is desired to display

{{plink|Item|File|alt=Text}}

Categorising

Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.

There are 2 methods of categorising pages with navboxes:

The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.

Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.

Examples

To see the following navboxes in action, see Template:Navbox.

Single line navbox with centered list

{{navbox
|name    = 
|title   = 
|style1  = text-align:center
|group1  =
}}

Navbox with standard footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|footer  = Centered footer
}}

Navbox with styled footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|fstyle  = text-align:right
|footer  = Right-aligned footer
}}

Multiple line navbox

{{navbox
|name    = 
|title   = 
|gtitle1 = Group title 1
|group1  = 
|gtitle2 = Group title 2
|group2  = 
|gtitle3 = Group title 3
|group3  = 
}}

Collapsed navbox

{{navbox
|state   = collapsed
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox with Tnavbar

{{navbox
|state   = plain
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox without Tnavbar

{{navbox
|state   = plain
|title   = 
|style1  = text-align:center
|group1  = 
}}

Complicated navbox

{{navbox
|state   = uncollapsed
|name    = 
|title   = 
|gtitle1 = Level 1 Title 1
|group1  = 
|gtitle2 = Level 1 Title 2
|group2  = 
|gtitle3 = Level 1 Title 3
|group3  = 
|gtitle4 = Level 1 Title 4
|group4  = 
|gtitle5 = Level 1 Title 5
|gtype5  = Subgroup
|group5  = 
  {{navbox
  |subgroup = Yes
  |gtitle1  = Level 2 Title 1
  |group1   =
  |gtitle2  = Level 2 Title 2
  |group2   =
  |gtitle3  = Level 2 Title 3
  |gtype3   = Subgroup
  |group3   = 
    {{navbox
    |subgroup = Yes
    |gtitle1  = Level 3 Title 1
    |group1   =
    |gtitle2  = Level 3 Title 2
    |group2   =
    }}
  |gtitle4  = Level 2 Title 4
  |group4   = 
  }}
|gtitle6 = Level 1 Title 6
|group6  = 
|gtitle7 = Level 1 Title 7
|group7  = 
|fstyle  = 
|footer  = 
}}

Preventing unwanted documentation

The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).

Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.