Template:Anchor

Template documentation[view] [edit] [history] [purge]

The template {{anchor}} inserts one or more invisible anchor names (HTML fragment identifiers) in a page.

The basic format is {{anchor|Anchor name}}. To link to an anchor from within the same page, use [[#Anchor name|display text]]. To link to an anchor from another page, use [[Article name#Anchor name|display text]]. See Help:Section linking for more details.

Note that #Anchor name, used by the MediaWiki software to (usually) direct users to sections within a page, is not a wikitext directive like #redirect.

Anchors are most useful with sections, since links to a section will not work if a section is renamed. However, anchors can be used as needed anywhere in an article. The anchor name can be arbitrary, but the first letter should generally be capitalized in keeping with header style (see Manual of Style: Section headers for more information).

Basic format

You can define one or more anchor names, separated by |. This can be useful for alternative spellings, such as "humor" and "humour."

In general, if the intended target of an anchor is a section title, then it should be placed at the end of the section header by substitution:
== Section header{{subst:anchor|Anchor name}} ==

which will be saved in the article as:
== Section header

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Anchor

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

==

Anchor names are case sensitive, so [[#Anchor name]] and [[#Anchor Name]] are not equivalent. When making an anchor, in general capitalize the first letter of the anchor name, and follow the same capitalization guidelines as headers (see Manual of Style: Headers for more information).

Limitations

Character	Code	Template	Meaning
"	" "	—	(double) quotation mark
#	#	{{hash}}	hash
|	|	{{!}}	pipe
=	=	{{=}}	equals

• Anchor names that contain any character shown in the table on the right will not work as expected. However, any of these characters can be replaced with the "&#" codes shown for them here. Or, the pipe symbol and equals sign can be worked around with {{!}} and {{=}}, respectively. Markup code such as <sup> and <sub> (superscript and subscript) cannot be used. Most other characters, including white space and punctuation, are not a problem.
• Anchor names must be unique on a page, and must not duplicate any heading titles. Duplicate anchors will not work as expected since the #location links go to the first anchor with that name. Duplicate anchors result in invalid HTML; you can check for duplicate anchors by running the page through the W3C Markup Validation Service.
• Anchor links are case-sensitive in some browsers, so treat all anchor links as case-sensitive when creating links to them. For example, if you create the anchor with === Baz{{subst:anchor|Bar}} ===, link to it with [[pagename#Bar]], not [[pagename#bAR]]. However, because some browsers are not case-sensitive, do not create section titles or anchors that differ only in case from others on the page. That is, do not create both === Abcd{{subst:anchor|Baz}} === and === Efgh{{subst:anchor|bAZ}} ===.
• If a template is left unsubstituted inside a section title (which should never be done), then the template code will appear in the edit summary window each time a section edit of that section begins, as in /* Limitations{{anchor|Issues}} */ New issue. The editor must manually remove the anchor template from the edit summary window, or else when they save the section, the browser may not return to the section and the section link of that edit in the history page won't work.

Use in tables

Anchors may be used within tables, subject to certain restrictions. The {{anchor}} template may be used in the caption and cells of a table, but not those portions of a table that are outside the caption and cells. Unlike in section headings, the template does not have to be substituted. It is used on the table's caption thus: <syntaxhighlight lang=text> |+ A table caption </syntaxhighlight> and the following forms of cell are valid: <syntaxhighlight lang=text> ! A header cell !style="background:white;" | A header cell with styling | A data cell |rowspan=2 | A data cell spanning two rows </syntaxhighlight> You need to ensure that the {{anchor}} is not in that portion of the markup intended for the classes, styles etc. Thus, {{anchor}} cannot be placed anywhere on lines that begin with {| (start of table) or |- (new row), and the following forms of cell are not valid: <syntaxhighlight lang=text> ! |A header cell !style="background:white;" |A header cell with styling | |A data cell |rowspan=2 |A data cell spanning two rows </syntaxhighlight> If it is necessary for an anchor to be in any of these positions, a different technique is used—the id= attribute. This is placed in that portion of the markup where the classes, styles etc. may be used, as follows: <syntaxhighlight lang=text>

A header cell	A header cell with styling	A data cell	A data cell spanning two rows </syntaxhighlight> The id= attribute may appear before, between or after any other attributes that may be present, but only one id= attribute may be used in each of these areas. If {{anchor}} is placed at the start of a vertically centered cell (which is the default for tables) then links to the anchor will jump to the start of the displayed content and not the top of the cell. This may require the reader to scroll up to fully see other cells in the row. It can be avoided by instead placing id= where the row code starts. Rationale for substitution in the header To show why substitution in the header is preferred, the following anchor is placed in the Basic format section header: == Basic format<span class="anchor" id="Foo"></span><span class="anchor" id="In-Foo"></span> == Since the anchor is actually used on this documentation page, the links #Basic format, #Foo and #In-Foo all work and can be tested to see the effect. For contrast, an anchor named #Under-Foo has also been placed underneath the Basic format section header and can be clicked to illustrate how this placement hides the section title when jumping to the linked target: == Basic format == {{anchor|Under-Foo}} Another anchor named #Above-Foo has been placed above the section header. This anchor does work correctly, but because the anchor is technically not in the section but before it, it makes editing counter-intuitive. {{anchor|Above-Foo}} == Basic format == Anchors should also never be left unsubstituted within a section header, as this violates MOS:HEADINGS and causes technical complications. Explanations and examples Reasons for the above being best practice are detailed in the following additional, numbered examples, as well as in § Limitations section: {{anchor|Foo}} could be linked to with [[#Foo|...]] from within the same article (let's call this article "Qux"), or it could be linked to with [[Qux#Foo|...]] from other articles and from redirects (where the ellipsis after the word "Foo" here means the words chosen to represent that link in the Wikipedia article, which, of course, could be anything). Anchors can be more suitable for inter-article linking than section titles are, because anchors are more stable. For example a section title == Foo == within a Wikipedia article titled Qux: == {{anchor|Foo bar}} Foo == Here, links via [[Qux#Foo bar]] would remain valid even if the section were renamed == {{anchor|Foo bar}} On foo and its many friends == A drawback of this approach (as detailed in § Limitations section) is that having a template in the section header causes problems with the edit summary window each time that a section edit is done for this section. The obvious solution is to place the anchor before the section name. This also prevents browsers from hiding the section title from view when jumping to the target. Note: The anchor name (Foo bar) should be different than the section (Foo) to avoid invalid HTML. Within section titles, it may be preferable to simply use direct HTML, which may be achieved by substitution like this: == Foo{{subst:anchor|Foo bar}} == which is saved into the article as: == Foo Usage Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do. If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}. The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes: However, {{code|a {{template}} call}} will still invoke the template: Use <nowiki>...</nowiki> around the template name to avoid this problem: When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text: is well spaced: foo    quux. versus: which is going to be visually confusing for many: foo quux. because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font. Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved. This template does not need to be substituted. Examples Markup Renders as Included templates Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template. Templates used inside {{code}} expose the rendered HTML— this can be useful. For example: Markup Renders as The above example shows the HTML rendered by the citation template, including the hidden metadata. TemplateData This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData. TemplateData for Anchor See also {{codett}}, wrapper for this template that removes background and border styling {{mono}}, monospaced font only {{param value}}, monospaced; friendly handling for blank space {{Syntaxhighlight}} {{kbd}}, for keyboard input Help:Wiki markup == This provides the stable, linkable anchor, but without the edit problem. The Note above still applies. See § Limitations for details. The template can be used to create multiple anchors with a single call. For example, {{anchor|Foo|Bar|baz}} will create three anchors that can then be linked to with [[#Foo]], [[#Bar]] and [[#baz]]. Here is a more literal example: Say you wrote an article about a recently discovered Indo-European language called "Yish Yash". The title of your article would probably be "Yish Yash language" (if there were already an article titled "Yish Yash" that covered the culture generally). Now let's say that within your article you wished to have a section titled "The placement of the tongue when producing Yish Yash vowel sounds". You would create a section heading that looked like this: == The placement of the tongue when producing Yish Yash vowel sounds == Let's say that you then finished up writing and saved the new article. Now, say you came across another article on Wikipedia titled "Proto-Indo-European vowels" which happened to have a section on the unique tongue placement used in Yish Yash. You decided it might be useful here for readers to be able to quickly access the section of your article on Yish Yash tongue placement when forming vowels; however, you don't want to send them to the beginning of the whole article on the Yish Yash language (you wanted to target them more specifically). So you create a link in the Proto-Indo European vowel article to the section within your article on the placement of the tongue in Yish Yash: you might do so by editing the text of the Proto-Indo-European vowel article and adding something like this to a relevant place within it: [[Yish Yash language#The placement of the tongue when producing Yish Yash vowel sounds|Yish Yash tongue placement]] is particularly interesting. That is some really long code, but it would create a direct link to the relevant section of the new Yish Yash language article and would look like this in the article on Proto-Indo-European vowels: "...Yish Yash tongue placement is particularly interesting..." Now let's say another editor came along and wished to change the heading of this section of your article for some legitimate reason—perhaps to "Yish Yash vowels and the tongue". They could do so by editing your article and making the section heading look like this: == Yish Yash vowels and the tongue == Unbeknownst to that editor, this would mean the link in the article on Proto-Indo-European vowels that you created earlier would now go by default to the top of the Yish Yash article instead of your carefully-chosen subsection! However, if an anchor were placed within the section heading of the Yish Yash article either when you created it or when the other editor came along and changed it—perhaps something like this: == The placement of the tongue when producing Yish Yash vowel sounds{{subst:anchor|Tongue}} == or like this: == Yish Yash vowel–tongue interaction{{subst:anchor|Tongue}} == and the text of the article on Proto-Indo-European vowels had been changed by you to something like this: [[Yish Yash language#Tongue|Yish Yash tongue placement]] is particularly interesting. then the link from the Proto-Indo-European article would continue to point to the relevant section of the Yish Yash article, even if the wording of the section heading there had changed completely and without the reader having to sort it out for themselves. The use of anchors can make for a cleaner, more efficient Wikipedia reading experience where section headings are changed—which they not infrequently are. TemplateData This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData. TemplateData for Anchor Add HTML anchors to a page. Make a link to your anchor with [[#Anchor on same page]] or [[Page you're linking to#Anchor on that page]]. Every anchor on a page must be different. Do not use the characters " or # or | or =. Template parameters This template prefers inline formatting of parameters. Parameter Description Type Status First anchor 1 Name of anchor Example Anchor name 1 String required Second anchor 2 Name of anchor String optional Third anchor 3 Name of anchor String optional Fourth anchor 4 To add more than four anchors, go to source editing. String optional See also {{Visible anchor}} {{Anchored list}} {{Anchor comment}} {{Shortcut}} WP:ANCHOR WP:TARGET {{Section link}} The above documentation is transcluded from Template:Anchor/doc. (edit | history) Editors can experiment in this template's sandbox (create | mirror) and testcases (create) pages. Add categories to the /doc subpage. Subpages of this template.