WP:Hatnote#Hatnote templates

{{short description|Short navigational notes in Wikipedia articles}}

{{Redirect2|WP:HN|Hatnote|text= It should not be confused with Wikipedia:Help namespace, Headnote, or Hat notation}}

{{redirect|WP:HAT|other uses|WP:HAT (disambiguation)|and|WP:Hatnote (disambiguation)}}

{{subcat guideline|editing guideline|Hatnote|WP:HN|WP:HAT}}

{{nutshell|Hatnotes provide links at the top of an article or a section to help readers locate a different article if the one they are viewing is not the one they're looking for.}}

{{Linking and page manipulation|linking and diffs}}

Hatnotes are short notes placed at the top of a page or a section, in the way that a hat is placed on top of one's head. For an example, see the notes in italics immediately preceding the boxes above. The purpose of a hatnote is to help readers locate a different article if the one they are at is not the one they're looking for. Readers may have arrived at the article containing the hatnote because:

  • They were redirected.
  • They may be seeking an article that uses a more specific, disambiguated title.
  • They may be seeking an article with a similar name to, or that otherwise might be confused with, the article with the hatnote.

Hatnotes provide links to the possibly sought article or to a disambiguation page.

Rules

{{Shortcut|WP:HATNOTERULES|WP:HRULES|WP:HNR}}

The six basic rules of hatnotes are:

  1. Link directly to other articles; do not pipe non-disambiguation links. With regard to linking to redirects, follow any applicable rules in the disambiguation guideline. For example, links to disambiguation pages should always end in "(disambiguation)".
  2. Keep explanations to a minimum; explain vital information only, letting the lead section and body of the article clarify things for the reader.
  3. Mention other topics and articles only if there is a reasonable possibility of a reader arriving at the article either by mistake or with another topic in mind.
  4. However, if a notable topic X is commonly referred to as "Foo", but the article "Foo" is not about X, there {{em|must}} be a hatnote linking to the article on X or linking to a disambiguation page that contains a link to the article on X.
  5. Ideally, limit hatnotes to just one at the top of the page or section. Multiple hatnotes may be appropriate when they serve different purposes, such as disambiguating topics with similar names and explaining redirects. (In such cases, consider using {{tlx|hatnote group}}.)
  6. Refrain from having redlinks in your hatnotes. As opposed to having redlinks in the writing of the article, redlinks in hatnotes do not help and add to a large backlog.

For more information about methods of disambiguating articles, see Wikipedia:Disambiguation.

Placement

{{See also|Wikipedia:Manual of Style/Lead section#Elements}}

{{shortcut|WP:HATNOTEPLACE|WP:HNP}}

Hatnotes are placed at the top of an article or section. When used at the top of an article, hatnotes are placed immediately following a short description template but strictly before any other content including protection icons or maintenance tags. For the specific order of placing hatnotes with respect to other article elements, see MOS:SECTIONORDER. Text-based web browsers and screen readers present the page sequentially. Placing hatnotes immediately after the title ensures that readers are promptly directed to related or alternative articles if they have arrived at the page unintentionally. This placement enhances navigation and improves the overall user experience.

Format

In most cases, hatnotes should be created using a standard hatnote template, as illustrated in {{section link|#Hatnote templates}} below. This permits the form and structure of hatnotes to be changed uniformly across the encyclopedia as needed, and the templates to be excluded in print.

Current style on the English Wikipedia is to italicize and to indent each note, without a bullet before the item. A horizontal dividing line should not be placed either under a note or after the final item in a list. Links to articles should follow the naming conventions for capitalization – typically sentence case, not all lower case.

When determining the content of the hatnote, keep in mind that it forms part of the user interface rather than the article content. Two applicable user interface design principles are clarity and conciseness. The hatnote should not overload the user with extraneous information, and the content should be imparted quickly and accurately. These design goals are conveyed succinctly in the principle less is more.

= Length and number =

{{shortcut|WP:1HAT|WP:ONESHORTHAT|WP:HATLENGTH}}

{{see|WP:SUMMARYHATNOTE}}

As hatnotes separate the reader from the content they are looking for, hatnotes should generally be as concise as possible. Long explanations are generally discouraged; the article's lead text, not the hatnote, should explain what the article is about. In almost all cases, the hatnote is intended only to direct readers to other articles in case they were actually looking for something they will not find in the article containing the hatnote.

If a disambiguation page exists for a given term, then linking to it should be enough. For example, if the article is X then its hatnote will link to X (disambiguation); it should not have entries for other topics known as X, like X (Grafton novel) or X (charge), because they are already listed in the disambiguation page. However, such an article may be linked if it could be expected by a significant number of readers to be at the title in question: for instance, Turkey is about the country, but many readers expect to find the article about the bird at that title; therefore, the hatnote there correctly reads

:{{xt|{{about|the country|the bird|Turkey (bird)|other uses}}}}

which renders

{{about|the country|the bird|Turkey (bird)|other uses|Turkey (disambiguation)}}

There should be as few hatnotes as possible. One single hatnote, which can accommodate several links, is greatly preferable to two or more. Multiple hatnotes may however be appropriate when each serves a different purpose, such as disambiguating the title or distinguishing similar terms.The acceptability of multiple hatnotes was clarified in a 2016 discussion.

Summarize or not?

{{shortcut|WP:HNS}}

Some hatnote disambiguation templates include a brief summary of the present article's topic; others do not have a summary. For instance, in the article Honey, one might use the template {{tlx|about|the insect-produced fluid}} to produce:

{{about|the insect-produced fluid|other uses|Honey (disambiguation)}}

Alternatively, one might use {{tlx|other uses}} to produce:

{{other uses|Honey (disambiguation)}}

Either of these two styles is acceptable. The choice of style in a given article is based on editors' preferences and on what is likely to be clearer and easier for the reader. (In this particular instance, most English speakers will know what honey is, and the second, more concise hatnote is preferable.) Where an article already has a hatnote in one of these styles, editors should not change it to the other style without good reason.

Examples of proper use

= Two articles with similar titles =

{{shortcut|WP:SIMILAR}}

{{See also|WP:PRIMARYTOPIC|WP:TWODABS}}

{{about|the village in England|H. P. Lovecraft's fictional town|Dunwich (Lovecraft)}}

Dunwich ({{IPAc-en|ˈ|d|ʌ|n|ɪ|tʃ}}) is a town in the county of Suffolk in England, the remnant of what was once a prosperous seaport and centre of the wool trade during the early middle ages, with a natural harbour formed by the mouths of the River Blyth. ...

When two articles share the same title, except that one title is disambiguated and the other is not, and it is not appropriate to change the undisambiguated article's title {{crossref|pw=y|(see {{section link|WP:Disambiguation#Primary topic}})}}, the undisambiguated article should include a hatnote with a link to the other article. It is not necessary to create a separate disambiguation page. The {{tlx|about}} template may be used for this. In this case, the parameterization was {{tlx|about|the village in England|H. P. Lovecraft's fictional town|Dunwich (Lovecraft)}}.

=Terms that can cause confusion with another topic=

{{shortcut|WP:HATCONFUSE|WP:HATMISSPELL}}

{{distinguish|Pearl}}

Perl is a family of high-level, general-purpose, interpreted, dynamic programming languages. ...

{{tlx|Distinguish}} or a related template can be used when there can be confusion with a similar term. They are typically used when readers have misspelled their desired title, and the error would be apparent by simply displaying the alternative term without further explanation. These hatnotes should only be used when the ambiguity exists for a significant portion of the readership.

However, they are not suitable when the difference is not readily apparent without additional details. In those cases, use {{tlx|about}}, {{tlx|for}} or {{tlx|other uses}} instead, as the differences in the suggested article are explained upfront without requiring the reader to click through and differentiate the terms on their own.

= Linking to a disambiguation page =

{{shortcut|WP:HATDAB}}

{{other uses|Monolith (disambiguation)}}

A monolith is a monument or natural feature, such as a mountain, consisting of a single massive stone or rock. Erosion usually exposes these formations. ...

When a term has a primary meaning and two or more additional meanings, the hatnote on the primary topic page should link to a disambiguation page. {{tlx|other uses}} may be used for this.

In many cases, the hatnote also includes a brief description of the subject of the present article, for readers' convenience:

{{about|the maze-like labyrinth from Greek mythology|other uses|Labyrinth (disambiguation)}}

In Greek mythology, the Labyrinth was an elaborate maze-like structure constructed for King Minos of Crete and designed by the legendary artificer Daedalus to hold the Minotaur. ...

The template {{tlx|about}} may be used for this. In this case the parameterization was {{tlx|about|the mazelike labyrinth from Greek mythology}}.

= Ambiguous term that redirects to an unambiguously named article =

{{shortcut|WP:AMBIGTERM|WP:HATREDIR}}

{{tlx|redirect}}, or a related template, can be used when an ambiguous title is redirected to an unambiguous title or a primary topic article:

Johann Sebastian Bach

----


(Redirected from {{querylink|Bach|qs=title=Bach&redirect=no}})

{{redirect|Bach}}

Johann Sebastian Bach ({{OldStyleDate|31 March|1685|21 March}}{{spaced ndash}}28 July 1750) was a German composer and musician of the late Baroque period. He is known for his orchestral music such as the ...

= Hatnotes above maintenance tags=

{{Further information|Wikipedia:Manual of Style/Layout#Order of article elements}}

Always place a hatnote above maintenance tags, but below short description templates. See above for specific details regarding the placement of hatnotes.

{{For|the 2014 film adaptation|The Giver (film){{!}}The Giver (film)}}

{{ambox

| name = Refimprove

| type = content

| class = ambox-Refimprove

| image = File:Question book-new.svg

| issue = This article needs additional citations for verification.

| fix = Please help [{{fullurl:{{FULLPAGENAME}}|action=edit}} improve this article] by adding citations to reliable sources. Unsourced material may be challenged and removed.

| date = October 2014

}}

The Giver is a 1993 American young-adult dystopian novel by Lois Lowry. It is set in a society which at first appears as utopian, but is later revealed to be a dystopian one as the story progresses. The novel follows a boy named Jonas. ...

Examples of improper use

{{Shortcut|WP:NOTHATNOTE|WP:NOTAHAT|WP:HATNOT}}

Below are some examples of improper usages of hatnotes.

{{Clear}}

=Trivial information, dictionary definitions, and slang=

{{Shortcut|WP:TRHAT}}

When notes feature a trivial detail or use of a term, or links to overly specific and tendentious material, they are unwarranted.

A previous version of the article Investment showed:

{{Hatnote|During a siege, to invest a town or fortress means to surround it with a contravallation and a circumvallation.}}

Investment is a term with several closely related meanings in finance and economics. It refers to the accumulation of some kind of asset in hopes of getting a future return from it. ...

In this case, there is no direct disambiguation, and the note listed is bound to be uninteresting to most readers. The proper disambiguation simply links to a separate Invest (disambiguation) page.

=Legitimate information about the topic=

{{Shortcut|WP:LEGITHAT}}

A previous version of the Aisha article showed:

{{Hatnote|Ayesha is sometimes used as a woman's name. Once popular only among Muslims, it was briefly popular among English-speakers after it appeared in the book She by Rider Haggard.}}

Aisha or Ayesha (Arabic {{lang|ar|عائشه}} {{lang|ar-Latn|`ā'isha}} = 'she who lives') was a wife of the Islamic prophet Muhammad. ...

This is an improper use of disambiguating hatnotes. Instead, the information belongs in the body of the article, or in the article about the book, or in a separate article about names, or all three places. Hatnotes are meant to reduce confusion and direct readers to another article they might have been looking for, not for information about the subject of the article itself.

=Disambiguating article names that are not ambiguous<span class="anchor" id="NAMB"></span>=

{{Shortcut|WP:NAMB|WP:NOTAMB|WP:NOHAT|WP:NOHATNOTE|WP:NOTAMBIGUOUS}}

It is usually preferable not to have a hatnote when the name of the article is not ambiguous.

Water (wuxing)

----

{{Other uses|Water (disambiguation)}}

In Chinese philosophy, water ({{zh|c=水|p=shuǐ}}), is the low point of matter. It is considered matter's dying or hiding stage. ...

Here, the hatnote can be removed. A reader who is following links within Wikipedia is unlikely to end up at Water (wuxing) if they were looking for other meanings of water, since water does not redirect there.

A hatnote may still be appropriate when even a more specific name is still ambiguous. For example, Tree (set theory) might still be confused with Tree (descriptive set theory).

The presence or absence of hatnotes in articles with disambiguated titles has been a contentious issue. There are cases where some editors strongly believe that such hatnotes should be included, such as the various articles about treaties called Treaty of Paris.

A hatnote {{Strong|may be appropriate}} in an unambiguously named article {{Strong|when an ambiguous term redirects to it}}, as explained in {{Section link|#Ambiguous term that redirects to an unambiguously named article}} above.

= Non-existent articles =

{{Shortcut|WP:NOARTICLE|WP:REDHAT}}

{{For|the guideline on when to create standalone articles versus sections|WP:NOPAGE}}

Hatnotes should not contain red links (links to non-existent articles), since hatnotes are intended to help users navigate to another article they may have intended to find.

<span class="anchor" id="Templates"></span>Hatnote templates

=Generic hatnote=

{{tlx|Hatnote}} allows general text to be shown in hatnote format. It is appropriate when none of the other specific templates listed below includes the combination of parameters needed, or to combine several of them in a single hatnote.

  • {{tlx|Hatnote|CUSTOM TEXT}} → {{Hatnote|CUSTOM TEXT}}
  • {{tlx|Hatnote|For other senses of this term, see etc...}} → {{Hatnote|For other senses of this term, see etc...}}
  • {{tlx|Self reference}} (a generic template for self-references to Wikipedia material)

=Other uses of the same title ("''For ..., see ...''")=

Per Wikipedia:Hatnote#Disambiguating article names that are not ambiguous, it is usually preferable {{em|not}} to have a hatnote when the name of the article is not ambiguous.

=="''This article is about ... For other uses, see...''"==

{{tlx|About}} is the main template for noting other uses.

{{em|Note: When used in main namespace (a.k.a. mainspace), the word "page" in the following hatnotes is replaced by "article".}}

  • {{tlx|About|TOPIC}} → {{About|TOPIC}}
  • {{tlx|About|USE1||PAGE2}} (When the disambiguation page has a different name – Note the empty second parameter) → {{About|USE1||PAGE2}}
  • {{tlx|About|USE1|USE2|PAGE2}} (When there is only one other use) → {{About|USE1|USE2|PAGE2}}
  • {{tlx|About|USE1|USE2|PAGE2|and|PAGE3}} (Two pages for USE2) → {{About|USE1|USE2|PAGE2|and|PAGE3}}
  • {{tlx|About|USE1|USE2|PAGE2#SUBSECTION{{tlf|!}}PAGE2TITLE}} (Using the {{tlx|!}} magic word to give the link a different title) → {{About|USE1|USE2|PAGE2#SUBSECTION{{!}}PAGE2TITLE}}
  • {{tlx|About|USE1|USE2|PAGE2|other uses}} (When there are several standard other uses and also a disambiguation page with default name – Note that the last page name is not specified) → {{About|USE1|USE2|PAGE2|other uses}}
  • {{tlx|About|USE1|USE2|PAGE2|other uses|PAGE3}} (When there are several standard other uses and also a disambiguation page with non-default name) →{{About|USE1|USE2|PAGE2|other uses|PAGE3}}
  • {{tlx|About||USE2|PAGE2|USE3|PAGE3|other uses}} (When you don't need to state the focus of this article/page – Note the empty first parameter) → {{About||USE2|PAGE2|USE3|PAGE3|other uses}}
  • {{tlx|About|||PAGE1|and|PAGE2}} → {{About|||PAGE1|and|PAGE2|_nocat=1}}
  • Note: {{tlx|for||PAGE1|PAGE2}} produces the same result.
  • {{tlx|About|TOPIC|section=yes}} → {{About|TOPIC|section=yes}}
  • Note: this hatnote says "section", instead of "article" or "page".
  • {{tlx|About|USE1|text{{=}}TEXT}} → {{About|USE1|text = TEXT}}

=="''This page is about ... It is not to be confused with ...''"==

{{tlx|About-distinguish}} is a template for noting other uses when there could be confusion with another topic.

  • {{tlx|About-distinguish|USE1|PAGE1}} → {{About-distinguish|USE1|PAGE1}}
  • {{tlx|About-distinguish-text|USE1|TEXT}} → {{About-distinguish-text|USE1|TEXT}}

=="''For ..., see ...''"==

{{tlx|For}} can be used instead of {{tlx|About}} so as not to display: This page is about USE1. but still specify a specific other use. This effect can also be achieved by using an empty first parameter in {{tlx|About}} as in:

For example: {{tlx|For|OTHER TOPIC|PAGE1}} is the same as {{tlx|About||OTHER TOPIC|PAGE1}} (note the empty first parameter).

However, it is somewhat clearer when using the {{tlx|For}} template, since the word "about" does not appear in the statement.

  • {{tlx|For|OTHER TOPIC}} → {{For|OTHER TOPIC}}
  • {{tlx|For|OTHER TOPIC|PAGE1}} → {{For|OTHER TOPIC|PAGE1}}
  • {{tlx|For|OTHER TOPIC|PAGE1|PAGE2}} → {{For|OTHER TOPIC|PAGE1|PAGE2}}
  • {{tlx|For|OTHER TOPIC|PAGE1|PAGE2|PAGE3}} → {{For|OTHER TOPIC|PAGE1|PAGE2|PAGE3}}

;Variations

:As with {{tlx|Other uses}}, there is a whole family of "for" templates. {{tlx|For-text}} allows custom text, such as quotation marks or a link from part of the "CUSTOM TEXT", but does not supply automatic wikilinking

:* {{tlx|For-text|OTHER TOPIC|CUSTOM TEXT}} → {{for-text|OTHER TOPIC|CUSTOM TEXT}} (note how CUSTOM TEXT isn't bluelinked)

:It also supports up to three topics:

:* {{tlx|For-text|OTHER TOPIC|CUSTOM TEXT|OTHER TOPIC 2|CUSTOM TEXT 2}} → {{for-text|OTHER TOPIC|CUSTOM TEXT|OTHER TOPIC 2|CUSTOM TEXT 2}}

:* {{tlx|For-text|OTHER TOPIC|CUSTOM TEXT|OTHER TOPIC 2|CUSTOM TEXT 2|OTHER TOPIC 3|CUSTOM TEXT 3}} → {{for-text|OTHER TOPIC|CUSTOM TEXT|OTHER TOPIC 2|CUSTOM TEXT 2|OTHER TOPIC 3|CUSTOM TEXT 3}}

=="''For other uses, see ...''"==

When such a wordy hatnote as {{tlx|About}} is not needed, {{tlx|Other uses}} is often useful.

  • {{tlx|Other uses}} → {{Other uses|Hatnote (disambiguation)}}
  • {{tlx|Other uses|PAGE1}} → {{Other uses|PAGE1}}
  • {{tlx|Other uses|PAGE1|PAGE2}} → {{Other uses|PAGE1|PAGE2}}

;Variations

:There are, historically, a whole family of "other uses" templates for specific cases. {{tlx|About}} is the standard hatnote for "other uses" and many of them can be specified using the {{tlx|About}} template. However, the individual templates may be easier to use in certain contexts.

:Here are the variations and (when appropriate) the equivalents using the {{tlx|About}}, {{tlx|Other uses}} or {{tlx|For}} templates.

;"For other uses of ..., see ..."

:* {{tlx|Other uses of|TOPIC}} → {{Other uses of|TOPIC|Topic (disambiguation){{!}}TOPIC (disambiguation)}}

:* {{tlx|Other uses of|TOPIC|PAGE1}} → {{Other uses of|TOPIC|PAGE1}}

=Redirect=

=="''... redirects here. For other uses, see ...''"==

  • {{tlx|Redirect|REDIRECT1}} → {{Redirect|REDIRECT1}}
  • {{tlx|Redirect|REDIRECT1||PAGE1}} → {{Redirect|REDIRECT1||PAGE1}}
  • {{tlx|Redirect|REDIRECT1|USE1|PAGE1}} → {{Redirect|REDIRECT1|USE1|PAGE1}}
  • {{tlx|Redirect|REDIRECT1|USE1|PAGE1|USE2|PAGE2}} → {{Redirect|REDIRECT1|USE1|PAGE1|USE2|PAGE2}}
  • {{tlx|Redirect|REDIRECT1|USE1|PAGE1|and|PAGE2}} → {{Redirect|REDIRECT1|USE1|PAGE1|and|PAGE2}}

;Variations:

  • For two sources:
  • {{tlx|Redirect2|REDIRECT1|REDIRECT2}} → {{Redirect2|REDIRECT1|REDIRECT2}}
  • {{tlx|Redirect2|REDIRECT1|REDIRECT2|USE}} → {{Redirect2|REDIRECT1|REDIRECT2|USE}}
  • {{tlx|Redirect2|REDIRECT1|REDIRECT2||PAGE1}} → {{Redirect2|REDIRECT1|REDIRECT2||PAGE1}}
  • {{tlx|Redirect2|REDIRECT1|REDIRECT2|USE|PAGE1}} → {{Redirect2|REDIRECT1|REDIRECT2|USE|PAGE1}}
  • {{tlx|Redirect2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2}} → {{Redirect2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2}}
  • For three or more sources:
  • {{tlx|Redirect-multi|2|REDIRECT1|REDIRECT2}} → {{Redirect-multi|2|REDIRECT1|REDIRECT2}}
  • {{tlx|Redirect-multi|3|REDIRECT1|REDIRECT2|REDIRECT3}} → {{Redirect-multi|3|REDIRECT1|REDIRECT2|REDIRECT3}}
  • {{tlx|Redirect-multi|2|REDIRECT1|REDIRECT2|USE|PAGE}} → {{Redirect-multi|2|REDIRECT1|REDIRECT2|USE|PAGE}}
  • {{tlx|Redirect-multi|2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2|and|PAGE3}} → {{Redirect-multi|2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2|and|PAGE3}}
  • {{tlx|Redirect-several|REDIRECT1|REDIRECT2|REDIRECT3}} → {{Redirect-several|REDIRECT1|REDIRECT2|REDIRECT3}}
  • To specify the text following "redirects here.":
  • {{tlx|Redirect|REDIRECT|text{{=}}TEXT}}→ {{Redirect|REDIRECT|text = TEXT}}
  • {{tlx|Redirect-synonym|TERM|OTHER TOPIC}} → {{Redirect-synonym|TERM|OTHER TOPIC}}

=="''For technical reasons, ... redirects here. ... ''==

  • {{tlx|Technical reasons|REDIRECT}} → {{Technical reasons|REDIRECT}}
  • {{tlx|Technical reasons|REDIRECT|PAGE}} → {{Technical reasons|REDIRECT|PAGE}}
  • {{tlx|Technical reasons|REDIRECT|DESCRIPTION|PAGE}} → {{Technical reasons|REDIRECT|DESCRIPTION|PAGE}}
  • {{tlx|Technical reasons|REDIRECT|DESCRIPTION1|PAGE1|DESCRIPTION2|PAGE2}} → {{Technical reasons|REDIRECT|DESCRIPTION1|PAGE1|DESCRIPTION2|PAGE2}}

==''... redirects here. Not to be confused with ...''==

  • {{tlx|Redirect-distinguish|REDIRECT|PAGE1}} → {{Redirect-distinguish|REDIRECT|PAGE1}}
  • {{tlx|Redirect-distinguish|REDIRECT|PAGE1|PAGE2|PAGE3}} → {{Redirect-distinguish|REDIRECT|PAGE1|PAGE2|PAGE3}}
  • {{tlx|Redirect-distinguish2|REDIRECT|TEXT}} → {{Redirect-distinguish2|REDIRECT|TEXT}}

=Similar proper names ("''For other people named ...''")=

==Other people==

  • {{tlx|Other people}} → {{Other people}}
  • {{tlx|Other people|NAME}} → {{Other people|NAME}}
  • {{tlx|Other people|NAME|PAGE}} → {{Other people|NAME|PAGE}}
  • {{tlx|Other people||PAGE}} → {{Other people||PAGE}}
  • {{tlx|Other people|NAME|PAGE|named{{=}}titled}} → {{Other people|NAME|PAGE|named=titled}}
  • {{tlx|About other people|PERSON1}} → {{About other people|PERSON1}}
  • {{tlx|About other people|PERSON1|NAME}} → {{About other people|PERSON1|NAME}}
  • {{tlx|About other people|PERSON1|NAME|named{{=}}titled}} → {{About other people|PERSON1|NAME|named=titled}}
  • {{tlx|About other people|PERSON1|NAME|PAGE}} → {{About other people|PERSON1|NAME|PAGE}}
  • {{tlx|About other people|PERSON1||PAGE}} → {{About other people|PERSON1||PAGE}}
  • {{tlx|About other people|PERSON1||PAGE1|PAGE2|PAGE3}} → {{About other people|PERSON1||PAGE1|PAGE2|PAGE3}}
  • {{tlx|Similar names|NAME1|NAME2|NAME3|NAME4}} → {{Similar names|NAME1|NAME2|NAME3|NAME4}}
  • :Note: defaults to "named" as in {{tlx|Other people}}, exists for options like "nicknamed", "known as", etc.

==Other places/ships/hurricanes==

  • {{tlx|Other places}}, analogous to {{tlx|Other uses}} → {{Other places|Hatnote (disambiguation)}}
  • {{tlx|Other places|PAGE}}, analogous to {{tlx|Other uses}} → {{Other places|PAGE}}
  • {{tlx|Other ships|SHIP1}} → {{Other ships|SHIP1}}
  • {{tlx|Other hurricanes|HURR}} → {{Other hurricanes|HURR}}

=Distinguish=

=="''Not to be confused with ...''"==

  • {{tlx|Distinguish|PAGE1}} → {{Distinguish|PAGE1}}
  • {{tlx|Distinguish|PAGE1|PAGE2|PAGE3|PAGE4}} → {{Distinguish|PAGE1|PAGE2|PAGE3|PAGE4}}
  • {{tlx|Distinguish|text {{=}} TEXT}} → {{Distinguish|text = TEXT}}
  • {{tlx|Distinguish|text {{=}} TEXT1 [[PAGE1]] TEXT2}} → {{Distinguish|text = TEXT1 PAGE1 TEXT2}}

=="''... redirects here. It is not to be confused with ...''"==

  • {{tlx|Redirect-distinguish|REDIRECT|PAGE1}} → {{Redirect-distinguish|REDIRECT|PAGE1}}
  • {{tlx|Redirect-distinguish|REDIRECT|PAGE1|PAGE2|PAGE3|PAGE4}} → {{Redirect-distinguish|REDIRECT|PAGE1|PAGE2|PAGE3|PAGE4}}
  • {{tlx|Redirect-distinguish-text|REDIRECT|TEXT}} → {{Redirect-distinguish2|REDIRECT|TEXT}}

=Family names=

{{shortcut|WP:HATPAT|WP:HATFAM}}

{{further|:Category:Hatnote templates for names}}

Family names can also be clarified using inline footnotes via {{tlx|Family name footnote}}.

=For use in sections=

{{See|WP:SUMMARYHATNOTE}}

=="''Main article: ...''"==

{{tlx|Main}} is used to make summary style explicit, when used in a summary section for which there is also a separate article on the subject:

  • {{tlx|Main|Main Article}} → {{Main|Main Article}}
  • {{tlx|Main|Main Article|Article2}} → {{Main|Main Article|Article2}}
  • {{tlx|Main list|Article1}} → {{Main list|Article1}}
  • {{tlx|Main category|Category name}} → {{Main category|Category name}}

=="''Further information: ...''"==

{{tlx|Further}} can supplement {{tlx|Main}} in summary sections, or can indicate more details in nonsummary sections:

  • {{tlx|Further|PAGE}} → {{Further|PAGE}}
  • {{tlx|Further|PAGE1|PAGE2|PAGE3}} → {{Further|PAGE1|PAGE2|PAGE3}}
  • {{tlx|Further|topic{{=}}TOPIC|PAGE1|PAGE2|PAGE3}} → {{Further|topic=TOPIC|PAGE1|PAGE2|PAGE3}}
  • {{tlx|Further2|PAGE1, PAGE2, and other text}} → {{Further2|PAGE1, PAGE2, and other text}}
  • {{tlx|Further ill}} may be used to link to articles containing further information on a topic, where English Wikipedia does not yet have an article, but another language Wikipedia does.

=="''See also ...''"==

{{tlx|See also}} can be used at the head of a section.

  • {{tlx|See also|TOPIC PAGE|OTHER TOPIC PAGE}} → {{See also|TOPIC PAGE|OTHER TOPIC PAGE}}

:Note: use {{em|only}} when OTHER TOPIC PAGE is {{em|related}} to current article and contains a self-explanatory parenthetical.

==Article or section transclusions==

  • {{tlx|Transcluding article|PAGE1|PAGE2|PAGE3...}} (used when transcluding 1 or more entire articles into a target article) → {{Transcluding article|PAGE1|PAGE2|...}}
  • {{Tlx|Transcluded section|PAGE}} (used when selectively transcluding a section from one article into a section of the target article) → {{Transcluded section|PAGE}}
  • {{Tlx|Transcluded section|PAGE|part{{=}}yes}} (used when selectively transcluding a section into part of a section on the target page) → {{Transcluded section|PAGE|part=yes}}

=<span id="Categories">For category pages</span>=

{{Category see also|Hatnote templates for category pages}}

Category-specific templates:

  • {{tlx|Category see also|THIS|THAT|THE OTHER}} → {{Category see also|THIS|THAT|THE OTHER}}

This is a template for linking categories horizontally. Horizontal linkage is often the right solution when vertical linkage (i.e., as sub-category and parent category) is not appropriate.

In most cases, this template should be used on {{em|both}} categories to create reciprocal linkage between the two categories.

  • {{tlx|Cat main|MAIN ARTICLE}} → {{Cat main|MAIN ARTICLE}}
  • {{tlx|Category explanation|colourless green ideas}} → {{Category explanation|colourless green ideas}}
  • {{tlx|Category pair|TOPIC1|TOPIC2}} → {{Category pair|TOPIC1|TOPIC2}}
  • {{tlx|Preceding category|OTHER TOPIC}} → {{Preceding category|OTHER TOPIC}}
  • {{tlx|Succeeding category|OTHER TOPIC}} → {{Succeeding category|OTHER TOPIC}}
  • {{tlx|Contrast|OTHERCAT1|OTHERCAT2}} → {{Contrast|OTHERCAT1|OTHERCAT2}}
  • {{tlx|Contrast|OTHERCAT1|OTHERCAT2|plural{{=}}yes}} → {{Contrast|OTHERCAT1|OTHERCAT2|plural=yes}}

=Correct titles=

"The correct title of this article is ... The substitution or omission of the (or, without a reason: "It appears incorrectly here") ... is due to technical restrictions."

{{main|Template:Correct title}}

=Lists=

{{further|:Category:Hatnote templates for lists}}

What to do before editing or creating a template<span class="anchor" id="Notes"></span>

{{strong|Do not use subst: with these templates}}, as that will prevent:

  1. Propagating changes as the template is modified
  2. What links here (WLH) listing.

These templates are used in thousands of articles; therefore, changing the syntax could break thousands of articles. If you wish to create or edit a disambiguation or redirection template, first ask yourself the following questions:

  1. Is there already a template that will do this job? Since many disambiguation and redirection templates have already been created, first check: :Category:Hatnote templates.
  2. Do I really need a new template for this? Will it likely be used on any other articles or should I just use {{tlx|Hatnote}} instead? Before creating a new template, see the template namespace guideline.
  3. If I change the parameters around on an existing template, do I know what the result will be? Will it break existing uses of the template, and if so, can I fix all of the errors?

Before making any changes, see Wikipedia:Template sandbox and test cases.

See also

References

{{Reflist}}

{{Hatnote templates|state=collapsed}}

{{Wikipedia templates}}

{{Wikipedia policies and guidelines}}

Category:Wikipedia disambiguation

Category:Wikipedia Manual of Style (related guidelines)