Sjabloon:Anchor

Template documentation

The template {{anchor}} inserts one or more HTML anchors in a page. Those locations can then be linked to using [[#location|…]] syntax.

Examples

1. {{anchor|Foo}}

could be linked to with [[#Foo|…]] from within the same article,

or it could be linked to with [[Article name#Foo|…]] from other articles and from redirects.

2. Anchors can be more suitable for inter-article linking than section titles are. For example:

== {{anchor|Foo}} Section title ==

Here, links via [[Article name#Foo]] would remain valid even if the section were renamed. Consider using {{subst:anchor comment}} after the section title to generate a HTML comment alerting other editors to the purpose of anchors used in this manner. See Limitations for the editing problems this use introduces.

The following is an example of what not to do:

== Section title {{anchor|Bar}} ==

Here, the link [[Article name#Bar]] would take the user to the section, but could undesirably hide the section title from view.

3. The template can be used to create up to ten 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]].

Specifying more than 10 anchors will cause an error message to be displayed.

Limitations

Character	Code	Template	Meaning
"	" "	N/A	(double) quotation mark
#	#	N/A	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.
• The template can create a maximum of 10 anchors. Specifying more than 10 anchors will result in an error message.
• Unlike with most templates, putting each anchor name on separate lines will not work as expected; for example:

{{anchor

|humpty
|dumpty}}

• Anchor names should be unique on a page, and should 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.
• If the template is added to a section title then the code will appear in the edit summary when that section is edited, as in "/* {{anchor|Issues}}Limitations */ New issue". This can be fixed by deleting the template code from the edit summary before the changes are saved. However, this fix breaks the section link in the article revision history. Consider using {{subst:anchor comment}} after the section title to generate a HTML comment alerting other editors to the purpose of anchors used in this manner, so they do not move the anchor out of the section heading when they notice the deleterious effects on their edit summary.
• Anchor links are case sensitive in some browsers, so treat all anchor links as case sensitive.

See also

• {{Visible anchor}}
• {{Anchored list}}
• {{Anchor comment}}
• {{Shortcut}}
• WP:ANCHOR
• WP:TARGET