Template:anchor/documentation: Difference between revisions
Jump to navigation
Jump to search
TheNightAvl (talk | contribs) (Created page with "Creates an anchor ID which can be called in links. * {{para|1|req=1}}: anchor ID * {{para|2}}: span content") |
TheNightAvl (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
Creates an anchor ID which can be called in links. | Creates an anchor ID which can be called in links. | ||
* {{para|1|req=1}}: anchor ID | * {{para|1|req=1}}: anchor ID | ||
* {{para|2}}: | * {{para|2}}: anchor content (inline) | ||
== Anchor naming == | |||
When linking with {{temp|m}}, {{temp|m+}} or {{temp|l}}, anchors will be assumed to begin with the language code, followed by the specified anchor parameter. Hence, anchor IDs in Radestrian entries should begin with <code>rad</code>. The following systematic approach is also recommended: | |||
* Etymology sections should be labelled with a number: <code>rad1</code> | |||
* Senses should be labelled with a number following an underscore <code>rad_1</code> | |||
** Hence, <code>rad3_2</code> should refer to Sense 2 of Etymology 3. | |||
Linking can then be done by using {{temp|m|rad|word|'''anchor=3_2'''}}, for example. |
Revision as of 20:12, 4 April 2024
Creates an anchor ID which can be called in links.
|1=
(required): anchor ID|2=
: anchor content (inline)
Anchor naming
When linking with {{m}}
, {{m+}}
or {{l}}
, anchors will be assumed to begin with the language code, followed by the specified anchor parameter. Hence, anchor IDs in Radestrian entries should begin with rad
. The following systematic approach is also recommended:
- Etymology sections should be labelled with a number:
rad1
- Senses should be labelled with a number following an underscore
rad_1
- Hence,
rad3_2
should refer to Sense 2 of Etymology 3.
- Hence,
Linking can then be done by using {{m|rad|word|anchor=3_2}}
, for example.