Template:Requested move/doc

__EXPECTED_UNCONNECTED_PAGE__

"Template:Move" and "Template:Move-multi" redirect here. For the template for moving discussions, see Template:Moved discussion to. For details on the corresponding procedure, see § Multiple related move requests.

"Template:Rename" redirects here; not to be confused with Template:Renamed.

Template:Requested move, with the assistance of RMCD bot, populates Wikipedia:Requested moves/Current discussions and Category:Requested moves.

This template is substituted for input validation and archiving reasons (so a permanent record of the proposed page name can be placed on the talk page).

Edits to this template, and Module:Requested move, which it invokes, can adversely affect RMCD bot. Please check edits with the bot operator before implementation.

Usage

Specified new name

Use this template to tag articles with a controversial or potentially controversial move request. For uncontroversial/technical requests, use {{subst:RMassist}}.

This template should be substituted into the talk page of the article to be moved. It is not placed in the article itself.

Please note that unlike {{Article for deletion}}, the discussion for a page move must take place on the talk page, not on Wikipedia:Requested moves.

Add this template at the bottom of the talk page of the page that you want to be moved. It should be formatted like this:

{{subst:Requested move |NewName |reason=Why ...}}

Where:

• NewName = your proposed new name for the page, i.e., the name which the page should be renamed or moved to
• Why ... = your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate
  • Please do not include templates that expand to tables, such as nav templates or {{Not a ballot}}, and also avoid collapse templates such as {{collapse}} and {{hidden}}. Templates like {{Not a ballot}} can go in the line above the requested move banner.
  • If such extra information is required in the nomination, please post it afterwards as a comment.

This will create a template (see Template:Requested move/dated) in a new section on the talk page, and links to the old page and new page. For example:

{{subst:Requested move |Template:Move |reason="Move" was the original name of this template, and we should revert to that.}}

will create:

Requested move 31 October 2026

Template:Requested move → Template:Move – "Move" was the original name of this template, and we should revert to that. Username (talk) 18:24, 31 October 2026 (UTC)

User:RMCD bot will copy the move information to WP:RM, usually within 20 minutes.

Unspecified new name

If you're unsure about what the best new name is, use a question mark for the new name.

{{subst:Requested move |? |reason=The name should be either "move" or "rename", let's discuss which is better.}}

creates:

Requested move 31 October 2026

Template:Requested move → ? – The name should be either "move" or "rename", let's discuss which is better. Username (talk) 18:24, 31 October 2026 (UTC)

Custom heading

You may also ask the template to override the default heading by supplying a value to the |heading= parameter (|header= will also work).

{{subst:Requested move |Template:Rename |reason=Rename is a more intuitive term. |heading=Rename this?}}

creates:

Rename this?

Template:Requested move → Template:Rename – Rename is a more intuitive term. Username (talk) 18:24, 31 October 2026 (UTC)

Shared talk pages

If the talk page is a redirect, you may start the discussion on the target's talk page.

In the following example, the talk page of the page to be moved, WT:WikiProject Articles for creation/Resources, redirects to its parent talk page, WT:WikiProject Articles for creation. The below code would be placed on the latter to centralize discussion:

{{subst:requested move |reason=(the reason for the page move goes here). |current1=Wikipedia:WikiProject Articles for creation/Resources |new1=Wikipedia:WikiProject Articles for creation/Reviewing and templates}}

Instead of the |1= unnamed parameter, the |current1= and |new1= parameters are used. The method is similar to the one under #Multiple related move requests. This creates:

Requested move 31 October 2026

• Wikipedia:WikiProject Articles for creation/Resources → Wikipedia:WikiProject Articles for creation/Reviewing and templates

– (the reason for the page move goes here). Username (talk) 18:24, 31 October 2026 (UTC)

Multiple related move requests

Related moves should be combined into a single request. This is particularly applicable when changing a primary topic, which generally requires moving at least a disambiguation page and another related page. Additional proposed moves should be formatted like this:

{{subst:Requested move
|NewName |reason=Why ...
|current2=Current title of page 2
|new2=New title for page 2
|current3=Current title of page 3
|new3=New title for page 3
...
|currentN = Current title of page N
|newN = New title for page N
}}

Where:

• NewName = your proposed new name for page 1, i.e., the page whose talk page is being used for the discussion
• N = the number of pages which are proposed for moves

Occasionally the discussions for significant multi-move requests may be hosted on WikiProject talk pages or other pages in Project namespace. For multi-move discussions hosted on a page which is not itself proposed to be moved, specify |current1=Current title of page 1 for the first page to move.

Adding survey and discussion subsections

Use the code |talk=yes to append the subsections in {{Requested move/talk}}.

Suppressing the signature or the section heading

This template automatically adds a signature to the requested move reason unless it appears to be already signed. To suppress the signature, you can use the code |sign=no. To suppress the section heading, |heading=no (|header=no will also work).
Requested moves are required to have a section heading and signature, so these parameters should rarely be used, generally only by experienced editors repairing malformed requests.

Default behavior

• If neither parameter |1= nor |new1= are specified, then ? – an unspecified destination to be decided on the talk page – is assumed
• If neither parameter |2= nor |reason= are specified, the default text is "Please place your rationale for the proposed move here." This text should be edited to replace it with an actual rationale for the requested move, or the request will be rejected.

Deprecated parameter

• Use of unnamed parameter |2= is not encouraged, because an unnamed parameter doesn't support a rationale containing an equals sign (often in web links, custom signatures, etc.), due to MediaWiki bug T16235.

Error messages

This template validates editor input, and may write one of the following messages if it's not used as intended. These errors are not reported at WP:RM. If you need help using this template, review the instructions given at requesting controversial and potentially controversial moves. If you still need help, post a question at Wikipedia talk:Requested moves.

• – A pagename cannot contain any of the following characters: # < > [ ] { }
• – There are other invalid characters and character sequences, e.g. [[./]]
• (e.g. wikt:)
• (applicable to multiple related move requests)
• (applicable to multiple related move requests)

TemplateData

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

TemplateData for Requested move

The templates should always be substituted! This template begins a discussion about a controversial or a potentially controversial move. It must be used on the talk page.

Template parameters

This template prefers inline formatting of parameters.

Parameter		Description	Type	Status
New name	1	The proposed title for the page	Page name	suggested
Reason	reason	The reason for the proposed page title	String	required
Custom heading	heading	Suppresses the default heading and adds a custom section title	String	optional
Signature	sign	Suppresses the signature if set to no	Boolean	optional

See also

• {{Rename media}}
• Wikipedia:Template messages/Moving
• Wikipedia:Requested moves
• Wikipedia:Categories for discussion

Template:Requested move 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.