Template:Em

{{{1}}}

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

This template is used in MediaWiki:Newpages-summary, and on approximately 1,560,000 pages, or roughly 1764% of all pages.
Changes to it can cause immediate changes to the Elite Dangerous Wiki user interface.
To avoid major disruption and server load, any changes should be tested in the template's /sandbox or /testcases subpages, or in your own user subpage. The tested changes can be added to this page in a single edit. Please discuss changes on the talk page before implementing them.

For the em dash template, see Template:Em dash.

Purpose

The Em template makes it faster and easier to apply the ... emphasis HTML element to text, and more importantly to indicate to human editors and Wikipedia bots they should not use ''...'' or ... typographic italicization to replace the intentional and semantically meaningful . Emphasis (...) is usually rendered visually in an italic (or oblique, a.k.a. slanted) typeface by default on graphical browsers, but can be parsed and acted upon in customizable ways with style sheets, apps, and text-to-speech screen readers. It is semantic markup, i.e. markup that conveys meaning or context, not just visual appearance.

Simple italicizing (''...'' or ...) is purely typographic and is semantically meaningless; however, there are some occasions when simple italics are preferable to the emphasis template, most often for titles of publications (books, films, albums, etc.), foreign words and phrases, words as words (when quotation marks are not used for that purpose), names of ships, scientific names of genera and below and other cases where stylistic conventions demand italics, but they convey no sense of emphasis.

The average reader, and average editor, do not and need not care about this distinction most of the time, but it can be important and editors who understand it can use this template as a baseline insurance against accidental or uninformed replacement by bots and human editors, as well as to add web accessibility.

Usage

{{em|text to be emphasized}}

or, if the text to be emphasized contains an equals sign:

{{em|1=text to be emphasized}}

These both render as:

text to be emphasized

This template puts intentional and explicit ... (emphasis) [X]HTML markup around the text provided as the first parameter. It is safest to always use the |1=.

Optional parameters

Advanced HTML values can be passed through the template to the HTML code:

|role= takes a WAI-ARIA role; adds role="rolename" to the HTML code
|class= takes a class name (or multiple class names, separated by spaces); adds class="classname[s]" to the HTML code
|style= takes inline CSS input; adds style="CSS directive[s]" to the HTML code
|id= takes a valid, unique HTML id (must begin with an alphabetic letter); adds id="name" to the HTML code
|title= takes text, which cannot be marked up in any way, and displays it as a pop-up "tooltip" (in most browsers) when the cursor hovers over the span

Use cases

This template is made to mildly emphasize an important word or phrase in a passage, in a way that is (unlike simply italicizing it) semantically meaningful markup. With this technique, the emphasized text stands out from the rest of the nearby text in most visual browsers and some text-to-speech screen readers (which usually ignore purely typographic italicization), without strongly affecting scannability. It can also be parsed by user agents and other software as definitively indicating emphasis, rather than text italicized for appearance or other purposes. Therefore, it should only be used sparingly in articles to highlight something being stressed (e.g., to represent mild vocal emphasis). Example:

"Contrary to reports, she was {{em|not}} dead after all."
"Contrary to reports, she was not dead after all."

It is also occasionally used for disambiguation, e.g. between two adjacent but different uses of the same word or homonym ("What it is is a kind of custard."), but this usage is not often encyclopedic and can usually be rewritten to avoid the awkward construction, unless part of a direct quotation.

When this template should not be used

Because {{em}} is strictly for semantic (meaningful) emphasis, it should not be used for layout, typography conventions (titles, foreign words, scientific names of genera and species, etc.), and other cases that are not true emphasis. In these different cases, italics Wikicode ''...'', which is rendered as ... for the browser or other user agent, should be used instead, or special markup for a particular case, such as {{var|...}} or <var>...</var> for variables in computer science and mathematics.

{{Em}} should also not be used when the text to which it is applied is italicized for some other reason (e.g., it is part of a book title); in such cases use {{Strong}} instead. Usually avoid using {{em}} in non-quoted sentences that end in an exclamation point. It is usually excessive to use {{em}} on terms that are Wikilinked, since the link markup acts as a form of emphasis itself.

"The New York Times is an American daily newspaper." This example should use ''The New York Times''.

If {{em}} is used in the lead or introduction of an article, popups previews will omit the template content when a link to it is hovered over, which may cause confusion; in these cases it may be preferable to use ''...'' markup instead.

TemplateData

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

TemplateData for Em

Formats text with the HTML emphasis () element. Do not use for layout, typography conventions (titles, foreign words, scientific names of genera and species, etc.), and other cases that are not true semantic (meaningful) emphasis; use normal ''italics'' formatting instead.

Template parameters[Edit template data]
This template prefers inline formatting of parameters.
Parameter		Description	Type	Status
Text	`1`	The text to format.	Content	required
WAI-ARIA role	`role`	The WAI-ARIA (Accessible Rich Internet Applications) role that the text plays. Adds the "role" attribute with the provided value to the HTML code. Suggested values `math` `presentation` `none` `note`	String	optional
HTML class(es)	`class`	Name(s) of the class(es), separated by spaces, to be added to the HTML "class" attribute.	String	optional
CSS formatting markup	`style`	CSS directives for formatting the text. Added to the HTML "style" attribute.	String	optional
HTML unique identifier	`id`	A unique HTML identifier, which must start with an alphabetic letter. Added to the "id" attribute.	String	optional
Tooltip text	`title`	Explanatory text of the pop-up tooltip to be displayed on hover. Added to the HTML "title" attribute.	String	optional

Template:Em 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 ( ) 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.