Template:Anchor/doc

The template inserts one or more invisible HTML fragment identifiers (anchor names) in a page. Those locations can then be linked to using  syntax  (note that   here is not a browser instruction like  —the word "Location" can be any word you wish to associate with any part of an article in which you decide to place the  template, and can be entirely arbitrary; also, the first letter of the location is usually capitalised to reflect the common capitalisation used in section headers—see MOS:HEAD for more on this style guideline).

Examples
could be linked to with  from within the same article (let's call this article "Qux"), or it could be linked to with from other articles and from redirects (where the ellipsis after the word "Foo" here means the words chosen to represent that link in the Taswin article, which, of course, could be anything). Foo == Here, links via would remain valid even if the section were renamed A drawback of this approach (as detailed in § Limitations below) 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 anchor is placed before the section name; otherwise browsers may hide the section title from view. Also, the anchor name should be different than the section  to avoid invalid HTML. Foo == which is saved into the article as: Foo == This provides the stable, linkable anchor, but without the edit problem. The Note above still applies. See § Limitations below for details.
 * 1) Anchors can be more suitable for inter-article linking than section titles are, because anchors are more stable. For example a section title  within a Taswin article titled  :
 * 1) Within section titles, it may be preferable to simply use direct HTML, which may be achieved by substitution like this:
 * 1) The template can be used to create multiple anchors with a single call. For example,

will create three anchors that can then be linked to with,   and. 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:
 * 1) Here is a more literal example:

Let's say that you then finished up writing and saved the new article. Now, say you came across another article on Taswin 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:

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". He or she could do so by editing your article and making the section heading look like this:

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:

or like this:

and the text of the article on Proto-Indo-European vowels had been changed by you to something like this:

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 Taswin reading experience where section headings are changed—which they not infrequently are.

Limitations

 * 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 "&amp;#" codes shown for them here. Or, the pipe symbol and equals sign can be worked around with ! and =, respectively. Markup code such as and  (superscript and subscript) cannot be used. Most other characters, including white space and punctuation, are not a problem.
 * Anchor names should be unique on a page, and should not duplicate any heading titles. Duplicate anchors will not work as expected since the  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.
 * If a template is inside a section title then the template code will appear in the edit summary window each time a section edit of that section begins, as in " ". The editor must manually fix the section title part of the edit summary window, or when the section is saved, the browser may not return to the section and the section link of that edit in the history page doesn't work. When using anchor in a section title, consider substituting the template, resulting in  being saved.

Use in tables
Anchors may be used within tables, subject to certain restrictions. The 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. It is used on the table's caption thus: and the following forms of cell are valid:  You need to ensure that the  is not in that portion of the markup intended for the classes, styles etc. Thus,  cannot be placed anywhere on lines that begin with   (start of table) or   (new row), and the following forms of cell are not valid:  If it is necessary for an anchor to be in any of these positions, a different technique is used—the   attribute. This is placed in that portion of the markup where the classes, styles etc. may be used, as follows: The   attribute may appear before, between or after any other attributes that may be present, but only one   attribute may be used in each of these areas.

TemplateData
{ "description": "The template inserts one or more HTML anchors in a page. Those locations can then be linked to using ... syntax.  The parameters labels shown here (e.g., 'First anchor', '1', and the rest) are provided for convenience; no parameter label is required in the template itself, so you may create an anchor within an article by typing  or  rather than  or  (though both formats will work correctly).  You may not use  all by itself, however, as this is like dropping a ship's anchor without tying a rope to it: it holds nothing in place, can't be found or used, and messes up the sea floor with garbage!", "params": { "1": {   "label": "First anchor", "description": "First anchor value; Only the first anchor is required.", "type": "string", "required": true }, "2": {    "label": "Second anchor", "description": "Second anchor.", "type": "string", "required": false }, "3": {    "label": "Third anchor", "description": "Third anchor.", "type": "string", "required": false }, "4": {    "label": "4th, 5th, ... anchor", "description": "For additional anchors, just add additional anchors (the template isn't limited to three)", "type": "string", "required": false } }}