This is a documentation subpage for

Template documentation

Template sandbox and testcases for TEMPLATE_NAME

Overview

This page provides a clean workflow to safely edit and validate TEMPLATE_NAME:

Sandbox: Template:TEMPLATE_NAME/sandbox — a working copy where you make changes.
Testcases: Template:TEMPLATE_NAME/testcases — inputs that exercise typical and edge cases.
Live: Template:TEMPLATE_NAME — the production version. Do not edit directly without review.

Use this page to:

Preview sandbox output against fixed testcases without touching the live template.
Compare actual vs expected output for each testcase.
Track recent changes and invite reviewers.

Quick links

Live template: Template:TEMPLATE_NAME
Sandbox: Template:TEMPLATE_NAME/sandbox
Testcases: Template:TEMPLATE_NAME/testcases
Documentation: Template:TEMPLATE_NAME/doc (optional)
Talk page: Template talk:TEMPLATE_NAME

How to test

1. Edit the sandbox at Template:TEMPLATE_NAME/sandbox. 2. Open this test page and click “Show preview” to render the sandbox with inputs below. 3. Verify each testcase: Does the “Actual output” match the “Expected output”? 4. If all pass, consider copying sandbox to live using an edit summary like:

  “Sync from /sandbox: passes all /testcases as of YYYY-MM-DD.”

Previewing tips

Use “Preview page with this template” gadget or the built-in preview.
Check parser output in different skins and mobile view.
Validate accessibility: headings order, link text, ARIA where applicable.
Internationalization: test with non-ASCII parameters and RTL where relevant.

Test harness

The following sections render the sandbox template against curated inputs. Each testcase shows:

Parameters passed to the template
Expected output (as plain wikitext target)
Actual output (rendered via sandbox transclusion)

Testcase A: Minimal invocation

Parameters: {{TEMPLATE_NAME}}

Expected output: [Minimal successful output with defaults: e.g., a neutral message or basic box]

Actual output (sandbox):

Character and language test sandbox

This sandbox is used to test how Template:TEMPLATE NAME behaves with special characters (such as Greek letters) and language-specific spans.

Basic examples

Greek letter (direct character): α
Greek letter (HTML entity): γ
German span example: A

Within the template

Below are example calls of the template using these characters as parameters.

{{TEMPLATE NAME | title = Greek test: α γ | summary = Demonstrating Greek letters: α, β, γ, and entities like γ. | attr1 = Direct Greek: α β γ δ | attr2 = Entity Greek: α β γ δ | attr3 = German label: A, English label: A }}

Preview the page to check if:

Greek characters (α, β, γ, δ) display correctly.
HTML entities (α, β, γ, δ) render as the expected symbols.
The A is kept as a German-language span and does not break the layout.

Notes

Use this sandbox to experiment with different scripts (Greek, Cyrillic, etc.).
Test right-to-left scripts by adding spans with lang="ar" or lang="he".
If the template trims or escapes some of these, adjust the template code accordingly.

Testcase B: Common parameters

Parameters: {{TEMPLATE_NAME | param1 = Alpha | param2 = Beta | flag = yes }}

Expected output: [Example: shows "Alpha" and "Beta" in designated slots; flag toggles enhanced styling]

Actual output (sandbox):

Character and language test sandbox

This sandbox is used to test how Template:TEMPLATE NAME behaves with special characters (such as Greek letters) and language-specific spans.

Basic examples

Greek letter (direct character): α
Greek letter (HTML entity): γ
German span example: A

Within the template

Below are example calls of the template using these characters as parameters.

{{TEMPLATE NAME | title = Greek test: α γ | summary = Demonstrating Greek letters: α, β, γ, and entities like γ. | attr1 = Direct Greek: α β γ δ | attr2 = Entity Greek: α β γ δ | attr3 = German label: A, English label: A }}

Preview the page to check if:

Greek characters (α, β, γ, δ) display correctly.
HTML entities (α, β, γ, δ) render as the expected symbols.
The A is kept as a German-language span and does not break the layout.

Notes

Use this sandbox to experiment with different scripts (Greek, Cyrillic, etc.).
Test right-to-left scripts by adding spans with lang="ar" or lang="he".
If the template trims or escapes some of these, adjust the template code accordingly.

Testcase C: Edge values and escaping

Parameters: {{TEMPLATE_NAME | param1 = [[Linked target|Visible text]] | param2 = {{subst:CURRENTTIMESTAMP}} | raw = <code>escaped</code> }}

Expected output: [Links render correctly; timestamp subst is literal in expected; raw shows escaped markup]

Actual output (sandbox):

Character and language test sandbox

This sandbox is used to test how Template:TEMPLATE NAME behaves with special characters (such as Greek letters) and language-specific spans.

Basic examples

Greek letter (direct character): α
Greek letter (HTML entity): γ
German span example: A

Within the template

Below are example calls of the template using these characters as parameters.

{{TEMPLATE NAME | title = Greek test: α γ | summary = Demonstrating Greek letters: α, β, γ, and entities like γ. | attr1 = Direct Greek: α β γ δ | attr2 = Entity Greek: α β γ δ | attr3 = German label: A, English label: A }}

Preview the page to check if:

Greek characters (α, β, γ, δ) display correctly.
HTML entities (α, β, γ, δ) render as the expected symbols.
The A is kept as a German-language span and does not break the layout.

Notes

Use this sandbox to experiment with different scripts (Greek, Cyrillic, etc.).
Test right-to-left scripts by adding spans with lang="ar" or lang="he".
If the template trims or escapes some of these, adjust the template code accordingly.

Testcase D: Internationalization (i18n)

Parameters: {{TEMPLATE_NAME | lang = ja | text = こんにちは世界 }}

Expected output: [Text displays correctly for non-ASCII; applies lang attribute or rtl/ltr where applicable]

Actual output (sandbox):

Character and language test sandbox

This sandbox is used to test how Template:TEMPLATE NAME behaves with special characters (such as Greek letters) and language-specific spans.

Basic examples

Greek letter (direct character): α
Greek letter (HTML entity): γ
German span example: A

Within the template

Below are example calls of the template using these characters as parameters.

{{TEMPLATE NAME | title = Greek test: α γ | summary = Demonstrating Greek letters: α, β, γ, and entities like γ. | attr1 = Direct Greek: α β γ δ | attr2 = Entity Greek: α β γ δ | attr3 = German label: A, English label: A }}

Preview the page to check if:

Greek characters (α, β, γ, δ) display correctly.
HTML entities (α, β, γ, δ) render as the expected symbols.
The A is kept as a German-language span and does not break the layout.

Notes

Use this sandbox to experiment with different scripts (Greek, Cyrillic, etc.).
Test right-to-left scripts by adding spans with lang="ar" or lang="he".
If the template trims or escapes some of these, adjust the template code accordingly.

Testcase E: Error handling

Parameters: {{TEMPLATE_NAME | param1 = | required =  }}

Expected output: [Shows a gentle error or maintenance category; does not break page layout]

Actual output (sandbox):

Character and language test sandbox

This sandbox is used to test how Template:TEMPLATE NAME behaves with special characters (such as Greek letters) and language-specific spans.

Basic examples

Greek letter (direct character): α
Greek letter (HTML entity): γ
German span example: A

Within the template

Below are example calls of the template using these characters as parameters.

{{TEMPLATE NAME | title = Greek test: α γ | summary = Demonstrating Greek letters: α, β, γ, and entities like γ. | attr1 = Direct Greek: α β γ δ | attr2 = Entity Greek: α β γ δ | attr3 = German label: A, English label: A }}

Preview the page to check if:

Greek characters (α, β, γ, δ) display correctly.
HTML entities (α, β, γ, δ) render as the expected symbols.
The A is kept as a German-language span and does not break the layout.

Notes

Use this sandbox to experiment with different scripts (Greek, Cyrillic, etc.).
Test right-to-left scripts by adding spans with lang="ar" or lang="he".
If the template trims or escapes some of these, adjust the template code accordingly.

Maintenance

Add new testcases when introducing features or fixing bugs.
Keep “Expected output” updated; include rationale in edit summaries.
When deprecating parameters, add tests demonstrating legacy behavior and warnings.

Copy-paste skeletons

Below are ready-to-use skeletons for the sandbox and testcases subpages.

Skeleton: Template:TEMPLATE_NAME/sandbox

{{#if:{{{required|}}} |  <div class="tmpl"> {{{param1|}}} · {{{param2|}}} {{#if:{{{flag|}}}|✓|}} {{#if:{{{raw|}}}|{{{raw}}}|}} </div> |  TEMPLATE_NAME: missing required parameter [[Category:Pages with TEMPLATE_NAME errors]] }}

Skeleton: Template:TEMPLATE_NAME/testcases

; Minimal : {{TEMPLATE_NAME/sandbox}} ; Common params : {{TEMPLATE_NAME/sandbox | param1 = Alpha | param2 = Beta | flag = yes }} ; Edge and escaping : {{TEMPLATE_NAME/sandbox | param1 = [[Linked target|Visible text]] | param2 = 20250101T000000Z | raw = <code>escaped</code> }} ; I18n : {{TEMPLATE_NAME/sandbox | lang = ja | text = こんにちは世界 }} ; Error handling : {{TEMPLATE_NAME/sandbox | required = }}

Review checklist

Output is stable across re-parses; no expensive parser functions without need.
No unexpected categorization in mainspace; errors go to maintenance cats.
Template is documented at Template:TEMPLATE_NAME/doc with parameters, examples, and tracking.
Style is minimal; avoid inline CSS unless necessary; consider using existing module or template styles.

This box: view • talk • edit

Template:Terminate sentence ensures a sentence ends with a specified terminator (default: a period). It avoids adding duplicate terminators and can optionally trim trailing spaces. It attempts to ignore trailing closing quotes or brackets when deciding whether a terminator is already present.

Usage

Basic:

{{Terminate sentence|This is a sentence}}
→ This is a sentence.

Named parameters:

{{Terminate sentence
 |text=He said "Hello"
 |term=.
}}
→ He said "Hello".

Custom terminator:

{{Terminate sentence|text=Warning|term=!}}
→ Warning!

Avoid duplicate terminator:

{{Terminate sentence|text=Already done.|term=.}}
→ Already done.

Trim trailing spaces:

{{Terminate sentence|text=Ends with space   |trim=yes}}
→ Ends with space.

Skip processing:

{{Terminate sentence|text=No changes here|skip=yes}}
→ No changes here

Append a note:

{{Terminate sentence|text=Complete|note=(source: 2025)}}
→ Complete. (source: 2025)

Parameters

1 / text: The input text to terminate.
term: The terminator to enforce at the end. Default is .. Common choices: !, ?.
trim: If yes/true/1, strips trailing spaces before checking.
skip: If yes/true/1, returns text unchanged (still appends note if provided).
allowdup: If yes/true/1, allows duplicate terminators (e.g., ellipses). Default disallows duplicates.
note: Optional text appended after a space, unaffected by termination logic.

Behavior details

Terminator detection attempts to ignore trailing closing quotes/brackets (", ', ”, ), ], }).
If the last visible character equals term, no extra terminator is added unless allowdup=yes.
If trim=yes, trailing spaces are removed before detection.
If note is present, it is added with a leading space after the final text.

Examples

Quotes:

{{Terminate sentence|text=He whispered "hush"|term=.}}

 → He whispered "hush".

Parentheses:

{{Terminate sentence|text=Complete (verified)|term=.}}

 → Complete (verified).

Exclamation:

{{Terminate sentence|text=Alert|term=!}}

 → Alert!

Ellipsis (allow duplicates):

{{Terminate sentence|text=Wait...|term=.|allowdup=yes}}

 → Wait....

Best practices

Prefer using term that matches the sentence intent (., !, ?).
For complex punctuation, consider the Lua-powered variant below.
Document usage in your template’s /doc page where you incorporate this helper.

Lua-powered variant (optional)

For more robust detection (including multilingual quotes and punctuation), create Module:TerminateUtil with:

-- Module:TerminateUtil
local M = {}

local closing = {
  [")"] = true, ["]"] = true, ["}"] = true,
  ['"'] = true, ["'"] = true, ["”"] = true, ["’"] = true, ["»"] = true, ["›"] = true
}

local function trimRight(s)
  return (s:gsub("%s+$",""))
end

function M.lastVisibleChar(args)
  local s = args.s or ""
  s = trimRight(s)
  local i = #s
  while i > 0 do
    local c = s:sub(i,i)
    if closing[c] then
      i = i - 1
    else
      return c
    end
  end
  return ""
end

return M

Then update the template to call:

{{#invoke:TerminateUtil|lastVisibleChar|s=text}}

This improves detection for closing quotes and brackets.

Function

This template is primarily used to add a correctly formatted hatnote to a page. Often, but not always, this is a disambiguation link at the top of article pages. It places an HTML div- / div block around the text entered as its only argument, which provides standardized formatting (contents are indented and italicized in most displays); it also isolates the contained code to make sure that it is interpreted correctly.

This template is also used as the "meta-template" for additional specialized disambiguation link templates; see Category:Hatnote templates for a list.

The template does not automatically create links of any kind. Links and other desired formatting must be explicitly added, using normal Wikipedia markup.

Usage

Basic usage

{{hatnote|text}}

All parameters

{{hatnote|text|extraclasses=extra classes|selfref=yes|category=no}}

Parameters

This template accepts the following parameters:

1 - the hatnote text. (required)
extraclasses - any extra CSS classes to be added. For example, the {{see also}} template adds the classes |extraclasses=boilerplate seealso.
selfref - if set to "yes", "y", "true" or "1", adds the CSS class "selfref". This is used to denote self-references to Wikipedia. See Template:Selfref for more information.
category - if set to "no", "n", "false", or "0", suppresses the error tracking category (Category:Hatnote templates with errors). This only has an effect if the first positional parameter (the hatnote text) is omitted.

Example

{{hatnote|Example hatnote text}} →

Errors

If no hatnote text is supplied, the template will output the following message:

Error: no text specified (help).

If you see this error message, it is for one of four reasons:

No parameters were specified (the template code was {{hatnote}}). Please use {{hatnote|text}} instead.
Some parameters were specified, but the hatnote text wasn't included. For example, the template text {{hatnote|extraclasses=seealso}} will produce this error. Please use (for example) {{hatnote|text|extraclasses=seealso}} instead.
The hatnote text was specified, but that text contains an equals sign ("="). The equals sign has a special meaning in template code, and because of this it cannot be used in template parameters that do not specify a parameter name. For example, the template code {{hatnote|2+2=4}} will produce this error. To work around this, you can specify the parameter name explictly by using 1= before the hatnote text, like this: {{hatnote|1=2+2=4}}.
You tried to access Module:Hatnote directly by using {{#invoke:hatnote|hatnote|text}}. Use of #invoke in this way has been disabled for performance reasons. Please use {{hatnote|text}} instead.

If you see this error message and are unsure of what to do, please post a message on Template talk:Hatnote, and someone should be able to help you.

Pages that contain this error message are tracked in Category:Hatnote templates with errors.

Technical details

The HTML code produced by this template looks like this:

<div class="hatnote">hatnote text</div>

The code is produced by Module:Hatnote.

Hatnote templates

For the full guideline on hatnotes, see Wikipedia:Hatnote.

Hatnotes must be at the very top of the page or section.

Generic hatnote

{{Hatnote|CUSTOM TEXT}} →

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

If a link in a hatnote points to a disambiguation page, the link should include "(disambiguation)", even if that is a redirect. This indicates that the disambiguation link is intentional, and not an error (see WP:INTDABLINK):

Not {{hatnote|other uses|Springfield}}; but

{{hatnote|other uses|Springfield (disambiguation)}}, or

Other uses of the same title ("For …, see …")

"This page is about … For other uses …"

{{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}} →
{{About|USE1||PAGE2}} (When the disambiguation page has a different name – Note the empty second parameter) →
{{About|USE1|USE2|PAGE2}} (When there is only one other use) →
{{About|USE1|USE2|PAGE2|and|PAGE3}} (Two pages for USE2) →
{{About|USE1|USE2|PAGE2#SUBSECTION{{!}}PAGE2TITLE}} (Using the {{!}} magic word to give the link a different title) →
{{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) →
{{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) →
{{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) →
{{About|USE1|USE2|PAGE2|USE3|PAGE3|other uses|PAGE4|and}} →
{{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|||PAGE1|and|PAGE2}} →

Note: {{for||PAGE1|PAGE2}} produces the same result.

{{About|USE1|section=yes}} →

Note: this hatnote says "section", instead of "article" or "page".

"This page is about … It is not to be confused with …"

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

{{About-distinguish|USE1|PAGE1}} → Template:About-distinguish
{{About-distinguish2|USE1|TEXT}} → Template:About-distinguish2

"For …, see …"

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

{{For|OTHER TOPIC}} →
For OTHER TOPIC, see Hatnote/doc (disambiguation).
{{For|OTHER TOPIC|PAGE1}} →
For OTHER TOPIC, see PAGE1.
{{For|OTHER TOPIC|PAGE1|PAGE2}} →
For OTHER TOPIC, see PAGE1. For PAGE2, see Hatnote/doc (disambiguation).
{{For|OTHER TOPIC|PAGE1|PAGE2|PAGE3}} →
For OTHER TOPIC, see PAGE1. For PAGE2, see PAGE3.
{{For||PAGE1|PAGE2}} →
For , see PAGE1. For PAGE2, see Hatnote/doc (disambiguation).

Variations: As with {{Other uses}}, there is a whole family of "for" templates. {{For2}} allows custom text, such as quotation marks or a link from part of the "CUSTOM TEXT"

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

"For other uses, see …"

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

{{Other uses}} →
{{Other uses|PAGE1}} →
{{Other uses|PAGE1|PAGE2}} →

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.

{{Other uses2|PAGE1}} → Template:Other uses2

Note: adds "(disambiguation)" to whatever is input as the PAGE1.

Note: {{Other uses|PAGE1 (disambiguation)}} produces the same result.

{{Two other uses|USE1|USE2|PAGE2}} → Template:Two other uses

Note: same as {{about}}, except it forces a second use to be noted if unspecified by parameters.

{{Two other uses|USE1|USE2|PAGE2|USE3|PAGE3}} → Template:Two other uses
{{Two other uses||USE2|PAGE2|USE3|PAGE3}} → Template:Two other uses
{{Three other uses|USE1|USE2|PAGE2|USE3|PAGE3}} Template:Three other uses
{{Three other uses||USE2|PAGE2|USE3|PAGE3}} → Template:Three other uses
{{Three other uses|USE1|USE2|PAGE2|USE3|PAGE3|USE4|PAGE4}} → Template:Three other uses

"For other uses of …, see …"

{{Other uses of}} → Template:Other uses of
{{Other uses of|TOPIC}} → Template:Other uses of
{{Other uses of|TOPIC|PAGE1}} → Template:Other uses of

"… redirects here. For other uses, see …"

{{Redirect|REDIRECT}} →
{{Redirect|REDIRECT||PAGE1}} →
{{Redirect|REDIRECT|USE1|PAGE1}} →
{{Redirect|REDIRECT|USE1|PAGE1|USE2|PAGE2}} →
{{Redirect|REDIRECT|USE1|PAGE1|USE2|PAGE2|USE3|PAGE3}} →
{{Redirect|REDIRECT|USE1|PAGE1|and|PAGE2}} →
{{Redirect|REDIRECT|USE1|PAGE1|USE2|PAGE2|and|PAGE3}} →
{{Redirect6|REDIRECT|USE1|PAGE1}} → Template:Redirect6
{{Redirect6|REDIRECT|USE1|PAGE1||PAGE2}} → Template:Redirect6

Variations

For two sources:
{{Redirect2|REDIRECT1|REDIRECT2}} →

{{Redirect2|REDIRECT1|REDIRECT2|USE}} →

{{Redirect2|REDIRECT1|REDIRECT2||PAGE1}} →

{{Redirect2|REDIRECT1|REDIRECT2|USE|PAGE1}} →

{{Redirect2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2}} →

{{Redirect2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2|USE3|PAGE3}} →

{{Redirect2|REDIRECT1|REDIRECT2|USE1|PAGE1|USE2|PAGE2|USE3|PAGE3|USE4|PAGE4}} →

{{Redirect4|REDIRECT1|REDIRECT2}} → Template:Redirect4

{{Redirect4|REDIRECT1|REDIRECT2|USE|TEXT}} → Template:Redirect4
For three sources:
- {{Redirect7|"REDIRECT1", "REDIRECT2", and "REDIRECT3"|USE1|PAGE1|USE2|PAGE2}} → Template:Redirect7
- {{Redirect10|REDIRECT1|REDIRECT2|REDIRECT3}} → Template:Redirect10
- {{Redirect10|REDIRECT1|REDIRECT2|REDIRECT3|USE|TEXT}} → Template:Redirect10
To specify the text following "redirects here.":
- {{Redirect3|REDIRECT|TEXT}} or {{Redirect text|REDIRECT|TEXT}} → Template:Redirect3
- {{Redirect-synonym|TERM|OTHER TOPIC}} → Template:Redirect-synonym

... Not to be confused with ...

{{Redirect-distinguish|REDIRECT|PAGE1}} → Template:Redirect-distinguish
{{Redirect-distinguish|REDIRECT|PAGE1|PAGE2|PAGE3|PAGE4}} → Template:Redirect-distinguish
{{Redirect-distinguish2|REDIRECT|TEXT}} → Template:Redirect-distinguish2

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

Other people

{{Other people}} → Template:Other people
{{Other people|NAME}} → Template:Other people
{{Other people|NAME|PAGE}} → Template:Other people
{{Other people|NAME|PAGE|named=titled}} → Template:Other people
{{Other people2|PAGE}} → Template:Other people2
{{Other people3}} → Template:Other people3

Note: same as {{About}} except uses "other people" instead of "other uses" if only 1 parameter is used

{{Other people3|PERSON1}} → Template:Other people3
{{Other people3|PERSON1|PERSON2}} → Template:Other people3
{{Other people3|PERSON1|PERSON2|PAGE2}} → Template:Other people3
{{Other people3|PERSON1||PAGE2}} → Template:Other people3
{{Other people5|NAME1|NAME2|NAME3|NAME4}} → Template:Other people5

Note: defaults to "named" as in {{Other people}}, exists for options like "nicknamed", "known as", etc.

Other places

{{Other places}}, analogous to {{Other uses}} → Template:Other places
{{Other places|PAGE}}, analogous to {{Other uses2}} → Template:Other places
{{Other places3|PAGE}}, analogous to {{Other uses}} → Template:Other places3

Other ships

For articles on ships:

{{Other ships|SHIP1}} → Template:Other ships

Distinguish

"Not to be confused with …"

{{Distinguish|PAGE1}} →
{{Distinguish|PAGE1|PAGE2|PAGE3|PAGE4}} →
{{Distinguish2|TEXT}} → Template:Distinguish2
{{Distinct|PAGE1|PAGE2|PAGE3|PAGE4}} or {{Distinct|[[PAGE1]]|[[PAGE2]]|[[PAGE3]]|[[PAGE4]]}} → Template:Distinct
{{Distinct|TEXT [[PAGE1]]}} → Template:Distinct

"… redirects here. It is not to be confused with …"

{{Redirect-distinguish|REDIRECT|PAGE1}} → Template:Redirect-distinguish
{{Redirect-distinguish|REDIRECT|PAGE1|PAGE2|PAGE3|PAGE4}} → Template:Redirect-distinguish
{{Redirect-distinguish2|REDIRECT|TEXT}} → Template:Redirect-distinguish2
- Also may be used as {{Redirect-distinguish2|REDIRECT}} → Template:Redirect-distinguish2

"For technical reasons, … redirects here. For … , see … ."

{{Technical reasons|REDIRECT}} →
{{Technical reasons|REDIRECT|PAGE}} →
{{Technical reasons|REDIRECT|DESCRIPTION|PAGE}} →
{{Technical reasons|REDIRECT|DESCRIPTION1|PAGE1|DESCRIPTION2|PAGE2}} →
{{Technical reasons|REDIRECT|DESCRIPTION1|PAGE1|DESCRIPTION2|PAGE2|DESCRIPTION3|PAGE3}} →

Family names

Further information: Category:Hatnote templates for names

Miscellaneous (hurricanes, Pope Stephen, Wiki selfref)

These hatnotes are topic-specific. They are documented at their template page.

Lists

Further information: [[::Category:Hatnote templates for lists]]

User pages

{{This user talk|TOPIC|PAGE1}} →

Template:This user talk

Notes

This template should not be substituted. Do not use subst: with these templates, as that will prevent:

propagating changes as the template is modified; and the
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:

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.
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.
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.

v t e Hatnote templates
Wikipedia:Hatnote Wikipedia:Disambiguation Wikipedia:Redirect
Generic	`{{hatnote\|TEXT}}` `{{selfref\|TEXT}}`
Other uses	`{{about\|USE1}}` Variations: `{{other uses}}` `{{other uses2\|PAGE}}`
For (other topic)	`{{for\|OTHER TOPIC}}` `{{for2\|OTHER TOPIC\|CUSTOM TEXT}}` `{{about\|\|USE}}`
Further information	`{{further\|OTHER PAGE}}` `{{further2\|CUSTOM TEXT}}`
See also	`{{see also\|OTHER TOPIC}}`
Other people	`{{other people}}` `{{other people2\|PAGE}}` `{{other people3\|USE1\|USE2}}`
Other places	`{{other places}}` `{{other places3}}`
Other topics	`{{other hurricanes}}` `{{other ships}}`
Other uses of (topic)	`{{other uses of\|TOPIC\|PAGE}}`
Redirect	`{{redirect\|REDIRECT}}` `{{redirect\|REDIRECT\|\|PAGE}}` `{{redirect\|REDIRECT\|USE\|PAGE}}` `{{redirect2\|REDIRECT1\|REDIRECT2}}` `{{redirect2\|REDIRECT1\|REDIRECT2\|USE\|PAGE}}` `{{redirect3\|REDIRECT\|TEXT}}` `{{redirect4\|REDIRECT1\|REDIRECT2}}` `{{redirect6\|REDIRECT\|USE1\|PAGE1\|\|}}` `{{redirect10\|REDIRECT1\|REDIRECT2\|REDIRECT3}}`
"Not to be confused with..."	`{{distinguish\|PAGE}}` `{{distinguish2\|TEXT}}`
Hatnote categories	Hatnote templates for category pages for [family] names for lists for user pages
{{Hatnote templates documentation}}

Template documentation

Template sandbox and testcases for TEMPLATE_NAME

Overview

Quick links

How to test

Previewing tips

Test harness

Testcase A: Minimal invocation

Basic examples

Within the template

Notes

Testcase B: Common parameters

Basic examples

Within the template

Notes

Testcase C: Edge values and escaping

Basic examples

Within the template

Notes

Testcase D: Internationalization (i18n)

Basic examples

Within the template

Notes

Testcase E: Error handling

Basic examples

Within the template

Notes

Maintenance

Categories

Copy-paste skeletons

Skeleton: Template:TEMPLATE_NAME/sandbox

Skeleton: Template:TEMPLATE_NAME/testcases

Review checklist

Usage

Parameters

Behavior details

Examples

Best practices

Lua-powered variant (optional)

See also

Function

Usage

Parameters

Example

Errors

Technical details

Hatnote templates

Generic hatnote

More pages on the same topic ("Further information ...")

"Main article: …"

"For more details on …, see …"

"See also …"

"Further information: …"

Other uses of the same title ("For …, see …")

"This page is about … For other uses …"

"This page is about … It is not to be confused with …"

"For …, see …"

"For other uses, see …"

"For other uses of …, see …"

"… redirects here. For other uses, see …"

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

Other people

Other places

Other ships

Distinguish

"Not to be confused with …"

"… redirects here. It is not to be confused with …"

"For technical reasons, … redirects here. For … , see … ."

Family names

Miscellaneous (hurricanes, Pope Stephen, Wiki selfref)

Categories

Lists

User pages

Notes

See also