Template:Non sequitur

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

Purpose

Use this template in the body of an article as a request for other editors to clarify text that is likely to be confusing to readers because it is a non sequitur, especially the introduction of a name, term, or other reference that was not previously mentioned, and the relevance of which is unclear. This most often happens when material is moved from its original context, in which it made sense, and pasted into an earlier section or into a different page. It also often happens when a source is quoted as mentioning someone by name, and this name is not linked or explained in the context of the Wikipedia article.

It also frequently happens when new editors used to an academic style use it in Wikipedia, e.g. writing "According to Johnson and Xiang...," without the article ever mentioning these people otherwise. It is not Wikipedia-normal to "namedrop" in mid-prose in this manner, even if it's a common form of attribution in journals in some fields. In this respect, encyclopedic writing is closer to news style than academic style: The reader needs to know why a particular person (or company, or whatever) is relevant before they'll understand why it's being mentioned; by contrast, academics in a field probably already know which other researchers are being referred to, and at least understand that the references to them are a short-hand form of citation to things given in detail in the footnotes. Most of our readers do not care about the footnotes, and Wikipedia content is often reused without them, so our article prose has to stand on its own. This template is not for material that is probably irrelevant (use {{relevance inline}}), but for material that probably is relevant, but the relevance of which is confused or confusing.

Usage

This is an inline template which should be placed immediately after the material in question, as with a footnote. For example:
      A reference to someone or something that needs explanation.{{non sequitur|date=October 2026}}
gives:
     A reference to someone or something that needs explanation.
The wikilink on "non sequitur" is set to Wikipedia:Please clarify.

Parameters

Abbreviated parameter sets:

{{non sequitur|date=October 2026 |reason= }}

{{non sequitur|date=October 2026 |reason= |text= }}

Full parameter set:

{{non sequitur|date=October 2026 |reason= |text= |pre-text= |post-text= |show= }}

Parameter descriptions:

|date=

This template allows 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. Alternatively, you may add the date automatically (without requiring bot intervention) by substituting the template. That is: {{subst:non sequitur}} is equivalent to {{non sequitur|date=October 2026}}. This technique also works if other parameters – |reason= |pre-text= |post-text= – are given.

|reason=

{{Clarify|reason=What the problem is}} (this is preferable to using a HTML <!-- comment --> after the tag, as it is tidier to keep all of the {{non sequitur}}-related code inside the template). If the explanation would be lengthy, use the article's talk page.

As well as being visible in the source code for editors' benefit, the reason parameter is, if provided, displayed when the mouse is hovered over the "non sequitur" link in the article. For technical reasons, this mouse-over feature does not work if the reason text contains double quotes. Use single quotes instead, or use the code " if it is essential to include a double quote.

|text= a.k.a. |1= or first, unnumbered parameter

The particular text needing clarification may be highlighted by wrapping this template around it:

• Text preceding the template, {{non sequitur|text=unclear namedropping,|date=October 2026}} text following the template.
  Text preceding the template, unclear namedropping, text following the template.

As with any template, if the material to be wrapped contains an equals character (=}, the parameter must be explicitly named or numbered.

|pre-text=

|post-text=

One can specify additional text to appear before and/or after the displayed "non sequitur" tag using the two parameters listed above:

• {{non-sequitur|pre-text=irrelevant}}
  will cause the words "irrelevant" to appear before "non sequitur" like this:
• {{non-sequitur|post-text=(complicated jargon)}}
  will cause "(complicated jargon)" to appear after "non sequitur" like this:.
• {{non-sequitur|post-text=(see [[Talk:Example#Unexplained namedropping|talk]])}}
  can be used to link to a discussion on the article's talk page; this example produces:

|show=

Change the displayed main wording of the template from non sequitur to something else, e.g. |show=who? (the template {{Who2}} is a shortcut wrapper for that particular case).

Style

When resolving this template, please note that the excessively news-style or "headline-ese" form of explaining a reference, as in "according to historian Jane Doe", is considered substandard by many readers and editors, especially non-North Americans. The more complete form, "according to the historian Jane Doe", is preferred and is acceptable in all dialects of English. Note also the difference between a clipped reference like "Said Oxford historian Doe, ..." versus the more informative and easier to parse version "According to the historian Jane Doe of Oxford University, ...". Shortening might be appropriate if Doe and Oxford have previously been mentioned in the article.

TemplateData

TemplateData documentation used by VisualEditor and other tools

See a monthly parameter usage report for Template:Non sequitur in articles based on its TemplateData.

TemplateData for Non sequitur

No description.

Template parameters[Edit template data]

Parameter		Description	Type	Status
reason	reason	A brief reason for the tag; do not include any double quotes.	String	optional
text	text	Text fragment containing concerns the tag is supposed to address. Auto value	String	optional
Month and year	date	The date the tag was added (this will be added automatically soon by a bot if not added manually). Example January 2019 Auto value {{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}	String	suggested
pre-text	pre-text	Any string to be added before the "Clarify" tag, such as "?"	String	optional
post-text	post-text	Any string to be added after the "Clarify" tag, such as "complicated jargon".	String	optional

Categorization

Adding this template to an article will automatically place the article into Category:Wikipedia articles needing clarification, or a dated subcategory thereof.

Redirects

• {{nonsequitur}}
• {{non-sequitur}}
• {{namedropping}}
• {{name dropping}}
• {{name-dropping}}

See also

Related inline templates {{Context inline}} {{Clarify}} {{Clarify span}} {{Ambiguous}} {{Definition}} {{Elucidate}} {{Vague}} {{Who2}}

Message-box templates {{Context}} {{Confusing}} {{Confusing section}}

Related pages Wikipedia:Citing sources Wikipedia:Explain jargon Wikipedia:Please clarify

Template:Non sequitur 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.