Template:Term/doc

The template is used in template-structured glossaries to create terms to be defined, that are properly structured, have semantic value, and can be linked to as if independent sections. It is a wrapper for , the description list term HTML element. The template has a mnemonic redirect at.

Basic usage:

Inline templates, reference citations, wikimarkup styles, etc., can be applied to the term in the second parameter (content or 2) as long as it remains without markup in the first parameter (term or 1. Technically, the explicit parameter names are optional if the term or content does not contain the "=" character, but as any editors can add material, including templates or URLs with this character in them,.
 * This will work:
 * This will fail:

More complex usage is typically:

or

or

{{#ifeq:{{BASEPAGENAME}}|Term|

Wiki-styling and linking the term

 * }}

If the second or content parameter is styled with wikimarkup, linked, or otherwise altered inside the template, the term must also be retained in unstyled form as the first or term parameter. Failing to do so will cause the template to malfunction, since it must have a "clean" term name to use as the  of the element, for linking purposes, among other reasons. The order intentionally mirrors that of wikilinking. Style cannot be applied around the template, either, as it is a container for content (the term), not content itself (and doing so will produce invalid markup that will have unpredictable results depending upon browser):
 * Correct:
 * Wrong:
 * Wrong:

For the same reasons that links to other pages are discouraged in headings, links are also discouraged in glossary terms:
 * Deprecated:
 * Preferred:, and use of in the  definition to link to the article esprit de corps.

Again, as with the first parameter (the term) itself, if the " " character (equals sign) is used in this second parameter, the syntax that the parameter be explicitly specified (and because many URLs, e.g. in reference citations, can contain this character, it is always safest to name the parameter):

numbered: "" or named: ""

The template can also be used in the content / 2 parameter, e.g. to provide the plural of the term (the most common usage), an alternative spelling, the old name of an entry that was linked to but has since changed, or a shortcut link anchor name:

""

As with styled terms, the second parameter must be used to provide the "bare" term. It is not necessary to add the term itself to the template when using. By contrast, when using semicolon-delimited terms in unstructured glossaries, the term does need to be added as an anchor explicitly if link anchorage is desired (which is almost always the case):

""|shortstops|short-stop|short stop|sslink}} }}

(Strictly speaking, this fact has nothing to do with this template, but may be of use to editors who are converting from one glossary style to the other.)

{{#ifeq:{{BASEPAGENAME}}|Term|

Multiple terms sharing a definition

 * }}

Two or more can be used for synonyms with a shared definition, though keep in mind that people looking for one and not finding it where they expect it to be alphabetized are liable to assume it is missing if you do not create a cross-reference entry. The parameter y is used on second and subsequent terms to visually group the terms close together so it is clear that they share a definition:

Example: { {term|1=asprin}} { {defn|1=A mild analgesic of the non-steroidal anti-inflammatory drug (NSAID) family...}} heroin: diacetylmorphine: diamorpine: { {defn|1=A synthetic narcotic drug of the opiate family...}} { {term|1=ranitidine}} { {defn|1=An antacid of the proton pump inhibitor family...}}

Result:

asprin: A mild analgesic of the non-steroidal anti-inflammatory drug (NSAID) family... heroin: diacetylmorphine: diamorpine: A synthetic narcotic drug of the opiate family... ranitidine: An antacide of the proton pump inhibitor family...

{{#ifeq:{{BASEPAGENAME}}|Term|

Languages

 * }}

To indicate the language of a non-English term, use the template and the ISO 639 language codes as documented at that template:

This shows no visual change for most languages:

esprit de corps:

For all non-English languages this provides many metadata features, but it is for those that do not use the Latin alphabet, so that the content displays properly in various browsers.

If it is useful to indicate the name of the language, there are individual templates for most languages, with names based on the ISO codes, and which automatically italicize the foreign content:

which renders as:

esprit de corps:


 * When two or more language variants of a term share the same definition&#58;:

One definition can actually have two or more terms above it as variations or alternatives with the same definition. The most common use case for this is presenting the term in two variants of English. Example: tyre: tyre: A resilient wheel covering usually made of vulcanized rubber. Result: tyre: tire: A resilient wheel covering usually made of vulcanized rubber.

The template has no lang parameter (and shouldn't – there are too many pitfalls).

{{#ifeq:{{BASEPAGENAME}}|Term|

Applying CSS styles to the term

 * }}

The style parameter will pass CSS styling on to the  element.

{{#ifeq:{{BASEPAGENAME}}|Term|

Examples

 * }}

This shows both a very simple and a rather complex instance:



applesnorkel: Definition of term 1.

arglefarst: Beginning of first definition of term 2

Conclusion of first definition of term 2. Second definition of term 2.

{{#ifeq:{{BASEPAGENAME}}|Term|

Images, hatnotes and other content

 * }}

Images, hatnotes and other "add-in" content intended to immediately follow the  They  be placed between the  and  or it will break the glossary markup. Images can, of course, be placed elsewhere within the, and bottom-notes like more can be placed at the ends of but s. 

colour ball: Set of Snookerballs.png

In snooker, any of the that are not. In blackball, a generic, collective term for the red and yellow of object balls.

{{#ifeq:{{BASEPAGENAME}}|Term|

Technical details

 * }}

What this template does on the technical level is wrap the term in the  HTML element to semantically mark the term as the on the page of the defined term, and puts this marked-up content inside a  description list (a.k.a. definition list, association list) term element, with CSS. That class isn't doing anything yet, but it could later, like the light font size increase.

{{#ifeq:{{BASEPAGENAME}}|Term| {{Gloss/doc}} {{Defn/doc}}