Template:Specify

^[specify]

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

This template may be used to tag statements that seem to be sourced but lack sufficient specificity as to what exactly is being drawn from the source. This situation most often arises when sources are over-summarized to an excessive level, without sufficient care for whether the result has a clear enough meaning to be properly verifiable.

Usage

Typical:

A questionably verifiable statement here.{{Specify |reason=One-line description of the problem. |date=October 2026}}

Examples

The Speaker of the House proposed extending the sunset clause in section 24 by another two years, while a similar amendment was proposed in the Senate.^[specify]^[1]
"Similar" has no clear meaning here, and could refer to something similarly phrased but radically different in scope, or instead, to an effectually identical provision worded very differently, so it is too unclear to count as being properly sourced without more specificity.
The paper's conclusions were questioned in some follow-up studies, but confirmed by others.^[2]^[3]^[4]^[5]^[specify]
It should not be left to the reader to play a guessing-game with regard to which studies did and did not confirm the conclusions, especially since the citation data may already provide a lot of contextual cues about the reputability of the two sets of conflicting results without having to pore over the studies' texts.
Latin American liberation theology met opposition from power in the US.^[specify]^[6]
Clearly needs further specification as to who opposed it, how, and when, or the claim is too vague to really be verifiable, and seems like a conspiracy theory in Wikipedia's voice.

When to use and not to use this template

Do not use this tag to label text which appears doubtful or false. In the case of biographies of living people, simply remove any alleged but unsourced information. Otherwise, please use another more appropriate tag for doubtful claims, as described below. For passages that are confusing, unclear, ambiguous, or missing a clarifier of some kind (i.e. the problem is with the wording, not the sourcing), use {{Clarify}}.

Regarding unsourced or poorly sourced information:

if it is likely true, but needs specificity, you may use {{Specify}}
if it is not doubtful, you may use {{Citation needed}} or {{Cite quote}} tag to ask for better citation in order to make the article complete.
if it is doubtful but not harmful to the whole article, you may use {{Verify source}} tag to ask for source verification.
If it is doubtful and harmful, you may move it to the talk page and ask for a source.
If it is very doubtful and very harmful, you may remove it directly without the need of moving it to the talk page first.

Technical

This template takes a |reason= parameter. Because it may not be immediately apparent to other editors what precisely needs to be specified, it may be helpful to add a brief reason for the tag like this:
{{Specify|reason=What the problem is.}}
As well as being visible in the source code for editors' benefit, the reason parameter is, if provided, displayed in the tooltip text when the mouse is hovered over the "specify" link in the article.

The template links to Wikipedia:Citing sources.

This template adds tagged articles to Category:Articles needing more detailed references.

This template is a self-reference and so is part of the Wikipedia project rather than the encyclopedic content.

TemplateData

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

TemplateData for Specify

This template may be used to tag statements that seem to be sourced but lack sufficient specificity as to what exactly is being drawn from the source. This situation most often arises when sources are over-summarized to an excessive level, without sufficient care for whether the result has a clear enough meaning to be properly verifiable.

Parameter		Description	Type	Status
reason	`reason`	A brief reason for the tag; do not include any double quotes.	String	optional
Date	`date`	An optional date parameter that records when the tag was added. If this template is added without the date parameter, the date parameter will be added soon after by a bot. Example January 2013 Auto value {{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}	String	suggested

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.

v • d • e Inline cleanup tags
Attribution
Clarity
Miscellaneous
Neutrality
Precision
Time-sensitivity
Verifiability
Wording
General advice

Template:Specify

Contents

Usage

Examples

When to use and not to use this template

Technical

TemplateData

See also

Usage

Syntax

States

Sub-groups

Collapsible sub-groups

Use of images

Categorising

Examples

Single line navbox with centered list

Navbox with standard footer

Navbox with styled footer

Multiple line navbox

Collapsed navbox

Plain navbox with Tnavbar

Plain navbox without Tnavbar

Complicated navbox

Preventing unwanted documentation