Template:Hatnote templates documentation

Wikipedia se

Hatnote templates[source ke badlo]

For a summary page on how to use these templates, see the example page here. For the full editing guideline on hatnotes, see Wikipedia:Hatnote.

Generic[source ke badlo]

  • {{Hatnote|CUSTOM TEXT}}
{{Hatnote|For other senses of this term, see [[etc…]]}}

More pages on the same topic ("Further information ...")[source ke badlo]

"Main article: …"[source ke badlo]

{{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:

  • {{Main|Main Article}}
Khaas article: Main Article
  • {{Main|Main Article|Article2}}
Khaas articles: Main Article and Article2

"For more details on …, see …"[source ke badlo]

{{Details}} can supplement {{Main}} in summary sections, or can indicate more details in nonsummary sections:

  • {{Details|PAGE1}}Lua error in Module:Details at line 30: attempt to call field '_formatLink' (a nil value).
  • {{Details|PAGE1|TOPIC}}Lua error in Module:Details at line 30: attempt to call field '_formatLink' (a nil value).

{{Details3}} allows any text to links:

"See also …"[source ke badlo]

  • {{See also|TOPIC PAGE|OTHER TOPIC PAGE}}Lua error in Module:See_also at line 43: attempt to call field 'formatPageTables' (a nil value).
Note: use only when OTHER TOPIC PAGE is related to current article and contains a self-explanatory parenthetical.

"Further information: …"[source ke badlo]

Other uses of the same title[source ke badlo]

"This page is about … For other uses …"[source ke badlo]

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

Note. When used in main namespace, the word "page" in the following hatnotes is replaced by "article".

  • {{About|USE1}}Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1||PAGE2}} (When the disambiguation page has a different name – Note the empty second parameter) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2}} (When there is only one other use) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2|and|PAGE3}} (Two pages for USE2) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2#SUBSECTION{{!}}PAGE2TITLE}} (Using the {{!}} template to give the link a different title) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2|USE3|PAGE3|USE4|PAGE4|USE5|PAGE5}} (When there are up to four other uses – You should generally create a disambiguation page at this point) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2|USE3|PAGE3|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) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2|USE3|PAGE3|other uses|PAGE4}} (When there are several standard other uses and also a disambiguation page with non-default name) →Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|USE1|USE2|PAGE2|USE3|PAGE3|other uses|PAGE4|and}}Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{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) → Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
  • {{About|||PAGE1|and|PAGE2}}Lua error in Module:Pagetype at line 175: attempt to call upvalue 'getPageObject' (a nil value).
Note: {{for||PAGE1|PAGE2}} produces the same result.
Note: this hatnote says "section", instead of "article" or "page".

"For …, see …"[source ke badlo]

{{For}} can be used instead of {{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 {{About}} as in:

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

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

Variations

As with {{Other uses}}, there is a whole family of "for" templates.[clarification needed]

  • {{For2|OTHER TOPIC|CUSTOM TEXT}}

"For other uses, see …"[source ke badlo]

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

Variations

There are, historically, a whole family of "other uses" templates for specific cases. {{About}} is the standard hatnote for "other uses" and many of them can be specified using the {{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 {{About}}, {{Other uses}} or {{For}} templates.

Note: adds "(disambiguation)" to whatever is input as the PAGE1.
Note: {{Other uses|PAGE1 (disambiguation)}} produces the same result.
Note: same as {{about}}, except it forces a second use to be noted if unspecified by parameters.

"For other uses of …, see …"[source ke badlo]

"… redirects here. For other uses, see …"[source ke badlo]

  • {{Redirect|REDIRECT}} (disambiguous) → Script error: No such module "redirect hatnote".
  • {{Redirect|REDIRECT||PAGE1}}Script error: No such module "redirect hatnote".
  • {{Redirect|REDIRECT|USE1|PAGE1}}Script error: No such module "redirect hatnote".
  • {{Redirect|REDIRECT|USE1|PAGE1|USE2|PAGE2}}Script error: No such module "redirect hatnote".
  • {{Redirect|REDIRECT|USE1|PAGE1|USE2|PAGE2|USE3|PAGE3}}Script error: No such module "redirect hatnote".
  • {{Redirect|REDIRECT|USE1|PAGE1|and|PAGE2}}Script error: No such module "redirect hatnote".
  • {{Redirect|REDIRECT|USE1|PAGE1|USE2|PAGE2|and|PAGE3}}Script error: No such module "redirect hatnote".
  • {{Redirect6|REDIRECT|USE1|PAGE1}} (disambiguous) → Template:Redirect6
  • {{Redirect6|REDIRECT|USE1|PAGE1||PAGE2}}Template:Redirect6
Variations
... Not to be confused with ...

Similar proper names ("For other people named ...")[source ke badlo]

Other people[source ke badlo]

Note: same as {{About}} except uses "other people" instead of "other uses" if only 1 parameter is used
Note: defaults to "named" as in {{Other people}}, exists for options like "nicknamed", "known as", etc.

Other places[source ke badlo]

Other hurricanes[source ke badlo]

Other ships[source ke badlo]

For articles on ships:

Other popes named Stephen[source ke badlo]

Distinguish[source ke badlo]

"Not to be confused with …"[source ke badlo]

"… redirects here. It is not to be confused with …"[source ke badlo]

"For technical reasons, … redirects here. For … , see … ."[source ke badlo]

Wikipedia self-reference[source ke badlo]

Categories[source ke badlo]

Category-specific templates:

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 both categories to create reciprocal linkage between the two categories.

Family names[source ke badlo]

Lists[source ke badlo]

User pages[source ke badlo]

Template:This user talk

Notes[source ke badlo]

Do not use subst: with these templates, as that will prevent:

  1. propagating changes as the template is modified; and the
  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:Disambiguation and redirection 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 {{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 Template sandbox and test cases.

See also[source ke badlo]
https://hif.wikipedia.org/wiki/Template:Hatnote_templates_documentation
hif.wikipedia.org
CC-MAIN-2023-40
165088
application/http; msgtype=response
sha1:QAVAQZPKU2DZIW3Y4GGAX5V3NUVF6RME
<urn:uuid:0cc6509c-31d6-4a6d-baef-bcfb9b0b39ac>
2023-10-03T21:46:58Z
208.80.154.224
text/html
sha1:HMSY45MEUJPXQPMEMQKSM6N26376GLAJ
<urn:uuid:8546edb3-0295-4eb0-9ecb-6f792eb9f1d8>
https://hif.wikipedia.org/wiki/Template:Hatnote_templates_documentation
response
<urn:uuid:38ca46fd-f2a2-4bb2-893b-c4803305bced>
isPartOf: CC-MAIN-2023-40
publisher: Common Crawl
description: Wide crawl of the web for September/October 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-154
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/