ߘߍ߬ߡߍ߲߬ߠߌ߲:ߞߙߊߞߏ
ߦߟߌߣߐ: ߣߴߌ ߞߊ߬ ߞߐߜߍ ߣߌ߲߬ ߡߊߦߟߍ߬ߡߊ߲߫߸ ߌ ߘߌ߬ߢߍ߬ߣߍ߲߫ ߦߴߌ ߟߊ߫ ߓߟߏߡߊߜߍ߲ ߠߊߓߌ߬ߟߊ ߡߊ߬ CC0 ߟߊߓߌ߬ߟߊ ߘߐ߫. ߖߊ߬ߡߊ ߟߊ߫ ߘߌ߲߬ߞߌߙߊ ߘߍ߬ߡߍ߲߬ߠߌ߲߬ ߞߐߜߍ ߘߐߜߍ߫ ߞߌ߬ߓߊ߬ߙߏ߬ߦߊ߬ ߜߘߍ߫ ߞߏ ߘߐ߫. |
ߣߌ߫ ߛߓߍߟߌ߫ ߞߟߊ߬ߟߊ߬ߡߊ ߘߏ߫ ߦߵߌ ߓߟߏ߫ ߌ ߦߋ߫ ߡߍ߲ ߠߊߘߏ߲߬ ߞߏ ߘߐ߫ ߞߐߜߍ߫ ߛߌߦߊߡߊ߲߫ ߠߎ߫ ߟߊ߫߸ ߡߋߘߌߦߊߥߞߌ ߞߙߊߞߏ ߟߊߓߊ߯ߙߊ ߘߌ߫ ߣߊ߬ ߞߍߟߌ߫ ߞߊ߲ߡߊ߬. ߘߐ߬ߥߙߊ߬ߟߌ ߣߌ߫ ߟߊߛߋߢߊߥߙߍ ߞߐߕߐ߮ ߟߎ߬ ߛߋ߲߬ ߕߴߊ߬ ߘߐ߫߸ ߓߊߏ߬ ߡߊ߬ߞߍ߬ߦߙߐ ߕߊ߲ߓߊ߲ ߕߍ߫ ߞߙߊߞߏ ߦߋ߫. ߞߙߊߞߏ ߟߎ߬ ߦߋ߫ ߞߍ߫ ߟߊ߫ ߛߓߍߣߍ߲߫ ߞߎߘߊ ߟߋ߬ ߘߌ߫ ߥߟߴߊ߬ ߟߊߞߎ߲߬ߘߎ߬ߣߍ߲߬ ߦߋ߫ ߞߍ߫ ߓߊߟߌߟߌ ߓߊ߯ߙߊ߫ ߞߍߣߍ߲߫ ߞߘߐ ߘߊߞߘߐ߫߸ ߡߍ߲ ߟߊߝߏ߬ߦߌ߬ߣߍ߲߬ ߦߋ߫ ߞߊ߬ ߝߘߊ߫ ߥߞߌ߫ ߜߘߍ߫ ߟߊ߫ ߟߊߒߡߊ߫ ߘߐ߫ ߥߞߌߔߋߘߌߦߊ߸ ߊ߬ ߣߌ߫ ߞߵߊ߬ ߟߊߛߣߍ߫ ߕߊ߯ߦߙߐ߫ ߥߞߌ ߘߐ߫. Templates can be newly written or, to save duplicating work already done, exported from another wiki e.g. Wikipedia, and then imported into the target wiki.
Basic usage
ߞߙߊߞߏ ߟߎ߬ ߦߋ߫ ߥߞߌ ߞߐߜߍ߫ ߞߟߊ߬ߟߊ߬ߡߊ ߟߋ߬ ߘߌ߫ ߡߍ߲ ߠߎ߬ ߞߣߐߘߐ ߟߎ߬ ߘߐߓߍ߲߬ߣߍ߲߬ ߦߴߊ߬ ߟߊ߫ ߴߴߥߊ߬ߟߊ߲߬ߞߌ߬ߴߴ (ߟߊߘߏ߲߬ ߠߊ߫) ߞߊ߲ߡߊ߬ ߞߐߜߍ ߕߐ߭ ߟߎ߬ ߟߊ߫. ߞߙߊߞߏ (ߕߊ߲ߔߑߟߋߕ) ߦߋ߫ ߓߍ߲߬ߡߊ߬ߞߊ߲ ߠߋ߬ ߟߊߓߊ߬ߕߏ߬ ߟߊ߫ ߡߍ߲ ߕߐ߮ ߦߋ߫ ߢߍߣߙߊ ߘߌ߫ ߴߴߞߙߊߞߏ:
ߴߴ ߦߋ߫ ߡߍ߲ ߠߊ߫߸ ߣߴߊ߬ ߦߋ߫ ߘߍ߬ߡߍ߲߬ߘߌ߬ ߟߊ߫ ߕߐ߯ߛߓߍߞߣߍ ߣߌ߲߬ ߠߊ߫: ߣߴߏ߬ ߕߍ߫ ߘߏ߲߬߸ ߌ ߘߌ߫ ߛߋ߫ ߊ߬ߟߎ߬ ߛߌ߲ߘߌ߫ ߟߊ߫ ߦߏ߫ ߥߞߌ߫ ߞߐߜߍ ߕߐ߭ ߟߎ߬.
To transclude a template, you used double open & close curly brackets {{template name}}
.
ߞߙߊߞߏ ߟߊߓߊ߯ߙߊߟߌ ߣߐ߰ߡߊ߲߬ߓߊ ߟߋ߬ ߦߋ߫ ߢߊ ߢߌ߲߬ ߠߎ߬ ߞߊ߲߬. ߣߴߌ ߞߊ߬ ߞߐߜߍ ߘߏ߫ ߛߌ߲ߘߌ߫ ߡߍ߲ ߦߋ߫ ߞߟߌ߫ ߟߊ߫ ߞߏ߫ "ߞߙߊߞߏ:ߌ ߣߌ߫ ߛߣߍ߫" ߞߣߐߘߐ ߟߎ߬ ߘߌ߫:
ߌ ߣߌ߫ ߕߎ߬ߡߊ߬߹ ߌ ߣߌ߫ ߛߣߍ߫ ߥߞߌ ߞߊ߲߬.
ߌ ߓߘߴߌ ߟߊ߫ ߞߙߊߞߏ߫ ߝߟߐ ߛߌ߲ߘߌ߫߹ ߏ߬ ߘߐ߫ ߣߴߌ ߞߊ߬ ߘߏߞߊ߲ (ߞߐߘ) ߠߊߘߏ߲߬:
{{Welcome}}
ߦߋ߫ ߞߐߜߍ ߛߎ߯-ߎ-ߛߎ߫ ߘߐ߫߸ ߣߌ߫ ߞߐߜߍ ߏ߬ ߦߌ߬ߘߊ߬ ߘߊ߫ ߛߓߍߟߌ "ߌ ߣߌ߫ ߕߎ߬ߡߊ߬߹ ߌ ߣߌ߫ ߛߣߍ߫ ߥߞߌ ߞߊ߲߬." ߏ߬ ߘߌ߫ ߓߐ߫ {{ߟߊ߬ߛߣߍ߬ߟߌ}}
ߘߌ߫ ߞߋߟߋ߲ߘߌ߫ ߘߌ߫. ߏ߬ ߓߊ߯ ߞߍ߫ ߞߙߊߞߏ ߞߣߐߘߐ ߟߎ߬ ߘߌ߫ "ߟߊߥߊ߬ߟߊ߲߬ߞߌ߫" ߞߐߜߍ߫ ߜߘߍ ߏ߬ ߘߐ߫߸ ߊ߬ ߢߊߝߐߟߌ߫ ߜߘߍ߫ ߘߐ߫߸ ߊ߬ ߘߌ߫ ߓߌ߬ߟߊ߬ ߞߐߜߍ ߏ߬ ߟߊ߫.
ߌ ߘߌ߫ ߛߋ߫ {{ߟߊ߬ߛߣߍ߬ߟߌ}}
ߟߊߘߏ߲߬ ߠߊ߫ ߞߐߜߍ ߛߎ߮ ߓߍ߯ ߦߙߐ ߘߏ߫ ߟߊ߫ ߌ ߦߴߊ߬ ߝߍ߬ ߞߵߊ߬ ߟߊߘߏ߲߬ ߡߍ߲ ߠߊ߫ ߡߐ߱ ߘߏ߫ ߟߊߛߣߍ߫ ߞߊ߲ߡߊ߬. ߡߍ߲ ߞߊߞߊ߲߫ ߞߊ߬ ߟߊߓߊ߯ߙߊ߫ ߞߐߜߍ߫ ߁߀߀ ߟߎ߫ ߟߊ߫. ߣߴߌ ߘߏ߲߬ ߞߊ߬ ߞߙߊߞߏ ߞߣߐߘߐ ߟߎ߬ ߡߊߦߟߍ߬ߡߊ߲߫ ߞߵߊ߬ ߞߍ߫:
ߌ ߣߌ߫ ߕߎ߬ߡߊ߫ ߦߋ߲߬߹ ߌ ߣߌ߫ ߛߣߍ߫ ߥߞߌ߫ ߡߊߞߓߊߣߍ߲ ߞߊ߲߬.
ߌ ߓߊ߯ ߥߊ߫ ߓߐ߫ ߞߐߜߍ߫ ߁߀߀ ߏ߬ ߟߎ߬ ߛߎ߯-ߎ-ߛߎ߫ ߞߊ߲߬߸ ߌ ߣߊ߬ ߞߙߊߞߏ ߟߊߘߏ߲߬ ߠߊ߫ ߡߍ߲ ߠߎ߬ ߟߊ߫߸ ߌ ߘߌ߫ ߥߊ߫ ߛߓߍߟߌ߫ ߞߎߘߊ߫ ߕߍ߬ߘߍ߫ ߦߋ߲߬ ߡߍ߲ ߣߴߌ ߟߊ߫ ߟߊ߬ߘߏ߲߬ߣߍ߲ ߕߍ߫ ߞߋߟߋ߲߫ ߘߌ߫. ߒ߬ߓߊ߬ ߢߊ ߏ߬ ߡߊ߬߸ ߌ ߓߘߊ߫ ߞߐߜߍ߫ ߁߀߀ ߏ߬ ߟߎ߬ ߓߍ߯ ߞߣߐߘߐ ߡߊߦߟߍ߬ߡߊ߲߫ ߠߵߏ߬ ߘߌ߫ ߞߵߊ߬ ߕߘߍ߬ ߌ ߡߴߊ߬ߟߎ߬ ߡߊߦߟߍ߬ߡߊ߲߫߸ ߓߊߏ߬ ߞߙߊߞߏ ߓߘߊ߫ ߟߊߥߊ߬ߟߊ߲߬ߞߌ߫ ߞߐߜߍ ߏ߬ ߟߎ߬ ߟߊ߫.
ߏ߬ ߟߋ ߦߋ߫ ߕߙߏ߬ߞߏ߬ߦߊ ߓߊߖߎߡߊ ߘߌ߫. ߟߥߊ߬ߟߊ߲߬ߞߌ߬ߟߌ ߓߊ߯ߙߊ߫ ߢߊ ߡߞߊ߬ߝߏ߬ߟߌ ߥߙߍߓߊߓߊ ߟߋ߬ ߦߋ߫ ߦߋ߲߬߸ ߡߍ߲ ߠߎ߬ ߦߋ߫ ߕߙߏ߬ߞߏ߬ߦߊ ߏ߬ ߘߝߊ߫ ߟߊ߫ ߞߊ߬ ߞߙߊߞߏ ߞߍ߫ ߟߊߓߊ߯ߙߕߊ߫ ߞߏߟߌߞߏߟߌ ߘߌ߫.
Ways to invoke a template
ߞߙߊߞߏ ߘߌ߫ ߛߋ߫ ߟߊߓߊ߯ߙߊ߫ ߟߊ߫ ߞߐߜߍ߫ ߜߘߍ߫ ߟߎ߫ ߟߊ߫ ߛߌߟߊ ߣߌ߲߬ ߠߎ߫ ߝߍ߬:
{{ߕߐ߮}}
- ߞߍ߫ ߕߐ߯ߛߓߍߣߍ߲ ߘߌ߫ ߛߊ߲ߝߍ߬߸ ߛߘߌ߬ߜߋ߲ ߏ߬ ߘߌ߫ [[ߞߙߊߞߏ:ߕߐ߮]] ߣߐ߬ߘߐߓߌ߬ߟߊ߬ ߖߝߊߕߌ߫߹ ߕߎ߬ߡߊ߬ ߟߊ߫߸ ߞߙߊߞߏ ߛߘߌ߬ߜߋ߲ ߴߴߟߊߘߏ߲߬ߣߍ߲߬ߴߴ ߦߋ߫ ߞߐߜߍ ߡߍ߲ ߠߎ߬ ߟߊ߫. ߛߘߌ߬ߜߋ߲ ߘߌ߫ ߞߍ߫ ߦߟߍ߬ߡߊ߲߬ߓߊ߬ߟߌ߬ߦߊ ߘߐ߫ ߞߐߜߍ ߟߎ߬ ߓߐߖߎ ߟߊ߫.
Because the template call remains in the pages's source, any subsequent change to Template:Name will be seen on the page containing the template call. Also, the page will be listed among those that "link to" the template.
{{subst:Name}}
— ߣߌ߫ ߞߙߊߞߏ ߣߌ߲߬ ߛߘߌ߬ߜߋ߲ ߟߊߓߊ߯ߙߊ߫ ߘߊ߫߸ ߊ߬ ߘߌ߫ ߣߐ߬ߘߐߓߌ߬ߟߊ߫ ߛߋ߲߬ߧߊ߬ ߞߋߟߋ߲߫ ߊ߬ ߣߌ߫ [[ߞߙߊߞߏ:ߕߐ߮]] ߞߣߐߘߐ ߓߍ߯ ߝߣߊ߫ ߟߴߊ߬ ߣߌ߫ ߕߎ߬ߡߊ߬ ߟߊ߫߸ ߣߌ߫ ߛߘߌ߬ߜߋ߲ ߴߴߠߊߞߎ߲߬ߘߎ߬ߵߵ ߘߊ߫: [[ߞߙߊߞߏ:ߕߐ߮]] ߞߣߐߘߐ ߓߊߞߎߘߊ ߘߌ߫ ߣߐ߬ߘߐߓߌ߬ߟߊ߬ ߞߙߊߞߏ ߛߘߌ߬ߜߋ߲ ߠߊ߫. ߏ߬ ߓߊ߯ ߞߍ߫ ߞߣߐߘߐ ߓߘߊ߫ ߞߍ߫ ߞߐߜߍ߫ ߛߋ߲߬ߓߐߣߍ߲ ߘߌ߫߸ ߊ߬ ߣߴߊ߬ ߘߌ߫ ߛߋ߫ ߡߊߦߟߍ߬ߡߊ߲߫ ߠߊ߫ ߢߊߓߘߍ ߡߊ߬߸ ߝߘߊߟߌߓߟߏߡߊ߬ ߞߐߜߍ ߓߐߛߎ߲ ߡߊ߬. ߴߴߞߟߏߜߍߴߴ: ߡߊ߬ߦߟߍ߬ߡߊ߲߬ߠߌ߲߬ ߜߘߍ ߡߍ߲ ߠߎ߬ ߞߍߕߐ߫ ߞߐߝߍ߬ ߞߙߊߞߏ ߓߐߛߎ߲ ߘߐ߫߸ ߏ߬ ߟߎ߬ ߕߍߣߊ߬ ߟߊߖߍ߲ߛߍ߲߫ ߠߊ߫ ߞߙߊߞߏ ߛߘߌ߬ߜߋ߲ ߞߐߜߍ ߟߎ߬ ߘߐ߫.
That is, a copy of the contents of Template:Name will be substituted for the template call. No link is maintained between the page and the template, so each can be edited further without affecting the other. In effect, there is little difference between substituting the content in this way and simply typing it into the page's source "manually". See Help:Substitution for more information.
{{safesubst:ߕߐ߮}}
- ߦߋ߫ ߟߊߘߏ߲߬ ߠߊ߫ ߟߋ߬ ߞߊ߬ ߣߘߐ߬ߓߌ߬ߟߊ߬ߟߌ ߟߊߘߤߊ߬ ߡߍ߲ ߕߍ߫ ߥߊ߬ߟߊ߲߬ߞߌ߬ߟߌ߬ ߗߌߙߏ߲ߣߍ߲߫ ߘߌ߫߸ ߣߌ߲߬ w:en:Help:Substitution#The safesubst: modifier ߘߐߜߍ߫.
See Help:Substitution for more information.
{{msgnw:name}}
ߦߋ߫ ߟߊߘߏ߲߬ ߠߊ߫ ߞߙߊߞߏ ߟߊ߫ ߟߋ߬ ߛߴߊ߬ ߘߌ߫ ߓߐ߫ ߖߙߎߡߎ߲߫ ߘߐ߫ ߡߍ߲ ߦߋ߫ ߓߊ߯ߙߊ߫ ߟߊ߫ ߥߞߌ ߟߊߞߊ߬ߝߏ߬ߣߍ߲ ߠߊ߫ ߞߊ߬ (syntax) ߛߍ߲ߕߊߞߛ (ߦߏ߫<nowiki>
ߦߋ߫ ߡߍ߲ ߞߍ߫ ߟߊ߫) ߣߵߊ߬ ߦߋ߫ ߞߐߜߍ ߘߴߏ߬ ߘߴߊ߬ ߖߊ߬ߛߏ߲߬.
For example, {{msgnw:Template:Thankyou}}
displays:
<noinclude> <languages/> </noinclude> '''A little thank you...''' for {{{reason|{{{1}}}}}}. hugs, {{{signature|{{{2}}}}}} <noinclude> [[Category:Template examples{{#translation:}}|{{PAGENAME}}]] </noinclude>
ߞߍߟߌ ߘߐ߫߸ ߥߞߌ߫ ߡߊߟߐ߲ߣߍ߲ ߞߐߜߍ ߟߎ߬ ߝߣߊ߫ ߘߌ߫ ߛߋ߫ ߟߊߓߊ߯ߙߊ߫ ߟߊ߫ ߞߙߊߞߏ ߘߌ߫߸ ߞߊ߬ ߕߐ߯ߛߓߍߞߣߍ ߞߙߍߞߙߍ߫ ߜߊ߲߯ߛߊ߲߫ ߠߊ߫ ߊ߬ ߢߊߞߍߣߍ߲߫ ߡߍ߲ ߘߐ߫߸ ߏ߬ ߘߐ߫ ߞߊ߬:
{{ߞߙߊߞߏ:ߞߐߜߍ ߕߐ߮}}
ߟߊߘߏ߲߬[[ߞߙߊߞߏ:ߞߐߜߍ ߕߐ߮]]
{{ߞߎߡߊ߫:ߞߐߜߍ ߕߐ߮}}
ߟߊߘߏ߲߬<[[ߞߎߡߊ߫:ߞߐߜߍ ߕߐ߮]]
{{}}
ߟߊߘߏ߲߬[[ߞߐߜߍ ߕߐ߮]]
{{subst::ߞߐߜߍ ߕߐ߮}}
ߣߐ߬ߘߐߓߌ߬ߟߊ߫ ߊ߬ ߖߘߍ߬ ߟߊ߫[[ߞߐߜߍ ߕߐ߮]]
ߞߣߐߘߐ ߟߊ߫.
ߣߌ߫ ߕߐ߯ ߞߣߍ߫ ߛߎ߮ ߏ߬ ߡߊ߫ ߞߍ߫ ߦߋ߲߬߸ ߞߎ߲߬ߕߐ߮ ߏ߬ ߟߎ߬ ߟߊߞߊ߬ߝߏ߬ߣߍ߲ ߞߊߞߊ߲߫ ߞߊ߬ ߞߍ߫ ߞߙߊߞߏ ߘߌ߫:
{{Foo:bar}}
ߟߊߘߏ߲߬[[ߞߙߊߞߏ:ߝߎ:ߓߊߙ]]
Regardless of what syntax is used, the name of the template can be relative to the current page
For example, if {{/bar}}
is called on page foo, it will transclude the page foo/bar.
It can also be generated dynamically.
For example, {{ {{foo}} }}
calls Template:foo and interprets the result as the name of another template to call.
ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ
ߖߐ߲߬ߛߊ߫ ߞߊ߬ ߟߥߊ߬ߟߊ߲߬ߞߌ߬ߟߌ ߕߙߏ߬ߞߏ߬ߦߊ ߘߝߊ߫߸ ߡߋߘߌߦߊߥߞߌ߫ ߦߋ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߎ߬ ߟߊߘߌ߬ߢߍ߬ ߟߊ߫ ߞߊ߬ ߞߍ߫ ߞߙߊߞߏ ߘߌ߫ ߣߴߊ߬ ߟߊߥߊ߬ߟߊ߲߬ߞߌ߫ ߘߊ߫. ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߎ߬ ߦߋ߫ ߞߙߊߞߏ ߟߊߘߌ߬ߢߍ߬ ߟߊ߫ ߞߊ߬ ߞߣߐߘߐ߫ ߓߐߣߍ߲ߢߐ߲߯ߡߊ ߟߎ߬ ߟߊߥߟߏ߫ ߤߊߡߊ߲߫ ߞߊ߬ ߗߋߘߊ߫ ߜߘߍ߫ ߟߎ߫ ߟߊߛߐ߬ߘߐ߲߫.
ߌ ߞߊߞߊ߲߫ ߞߊ߬ ߌ ߣߌ߫ ߗߋ߫ ߞߎ߲߬ߕߐ߮ ߞߟߏ ߟߊߘߏ߲߬ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ߫ ߞߐߜߍ ߟߎ߬ ߟߊ߫ ߞߎߡߊ߫ ߞߐߜߍ ߘߐ߫߸ ߦߏ߫ ߕߊ߲߫:
A little thank you...
for ߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫.
hugs, ߒߠߋ
ߌ ߣߌ߫ ߗߋ߫ ߛߓߍߟߌ ߞߎ߲߭ ߦߋ߫ (ߦߙߐ ߣߌ߲߬ ߠߋ ߘߌ߫߸ ߴߴߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫ߴߴ) ߊ߬ ߣߌ߫ ߞߟߊ߬ߣߐ (ߒߠߋ). ߌ ߟߊ߫ ߝߋ߲ ߏ߬ ߦߋ߫ ߟߋ߬߸ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ ߓߍ߯ ߘߌ߫ ߛߋ߫ ߌ ߣߌ߫ ߗߋ ߗߋ߫ ߟߊ߫ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ߫ ߜߘߍ߫ ߡߊ߬߸ ߞߎ߲߬ ߜߘߍ ߛߎ߯-ߎ-ߛߎ߫ ߣߌ߫ ߦߙߐ ߛߎ߯-ߎ-ߛߎ߫ ߘߐ߫.
ߏ߬ ߘߐ߫ ߛߍߓߟߌ ߟߎ߬ ߘߌ߫ ߡߎߣߎ߲ߧߊ߫ ߦߙߐ ߓߍ߯ ߘߐ߫ ߊ߬ ߟߊߓߊ߯ߙߊߣߍ߲߫ ߡߍ߲ ߘߐ߫߸ ߌ ߘߌ߫ ߛߋ߫ ߞߙߊߞߏ ߘߏ߫ ߡߊߕߍ߰ ߟߊ߫ ߡߍ߲ ߦߋ߫ ߞߟߌ߫ ߟߊ߫ ߞߏ߫ Template:Thankyou , ߞߵߏ߬ ߞߍ߫ ߟߊߒߡߊ ߘߌ߫. ߛߓߍߟߌ ߘߌ߫ ߡߎߣߎ߲߫ ߢߐ߲߯ ߠߊ߫ ߕߋ߲߬ ߝߛߊߦߌ߫߹ ߣߌ߫ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ ߘߏ߫ ߞߊ߬ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ߫ ߓߏߙߌߞߊߓߌߟߊ߫߸ ߊ߬ ߞߣߐߘߐ߫ ߞߙߍߞߙߍߣߍ߲ ߠߎ߬ (ߏ߬ ߞߘߐ ߦߋ߫ ߡߍ߲ ߘߌ߫߸ ߊ߬ ߞߎ߲߭ ߣߴߊ߬ ߞߟߊ߬ߣߐ) ߟߎ߬ ߘߌ߫ ߝߘߏ߬ ߢߐ߲߮ ߡߊ߬. ߞߎ߲߭ ߏ߬ ߟߋ ߞߏߛߐ߲߬߸ ߌ ߞߊ߲ߞߊ߲߫ ߞߵߊ߬ߟߎ߫ ߟߊߕߊ߬ߡߌ߲߬ ߞߵߊ߬ߟߎ߫ ߞߍ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߎ߬ ߘߌ߫. ߣߴߊ߲ ߞߊ߬ ߝߛߌ߬ ߘߎ߲ߡߊߣߍ߲ ߘߏ߫ ߡߊߓߌ߬ߟߊ߬ ߞߏ߲߬ߘߏ ߛߏ߯ߙߏߟߌ ߣߌ߫ ߖߌ߬ߦߊ߬ߓߍ ߓߌ߬ߟߊ߬ߞߏ ߘߐ߫߸ ߞߙߊߞߏ ߞߣߐߘߐ ߕߍߡߟߊ ߘߌ߫ ߞߍ߫ ߣߌ߲߬ ߘߌ߫:
'''ߌ ߣߌ߫ ߗߋ߫ ߘߋߣߍ߲...'''
{{{߁}}} ߢߍ߫.
ߘߐ߬ߘߌ߰ߟߌ߸ {{{߂}}}
Notice the use of {{{1}}}
and {{{2}}}
. This is the way to identify, within templates, the parameters that will be passed in when the template is used. Note that, within the template, each parameter is surrounded by three braces: {{{ }}}
. This is different from normal template name usage.
ߣߴߌ ߦߋ߫ ߞߙߊߞߏ ߟߊߓߊ߯ߙߊ ߞߊ߲߬ ߞߐߜߍ ߞߊ߲߬߸ ߌ ߦߋ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߡߐ߬ߟߐ߲ ߟߝߊ߫߸ ߡߍ߫ ߕߍߝߘߊߣߍ߲߫ ߦߋ߫ ߔߌߔ (ߔߊߔ$) ߟߊ߫. ߡߋߘߌߦߊߥߞߌ߫ ߘߌ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߊߘߌ߬ߢߍ߬ ߞߊ߬ ߛߋ߫ ߕߊ߬ߡߌ߲߬ ߠߊ߫ ߞߊ߬ ߞߍ߫ ߞߙߊߞߏ ߘߌ߫ ߛߌߟߊ߫ ߛߊ߬ߓߊ߫ ߞߊ߲߫: ߕߐ߯ߒߕߊ߲ߧߊ ߘߐ߫߸ ߝߙߍߕߍߦߊ ߘߐ߫߸ ߊ߬ ߣߌ߫ ߕߐ߯ߦߊߟߌ ߘߐ߫.
ߕߐ߯ߒߕߊ߲ߧߊ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ
ߞߊ߬ ߕߊ߬ߡߊ߬ߡߌ߲߬ ߕߐ߯ߒߕߊ߲ߧߊ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߘߐ߫߸ ߏ߬ ߟߎ߫ ߡߐ߬ߟߐ߲ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߎ߬ ߖߟߐ߬ߞߐ߬ߦߊ߬ߣߍ߲ ߠߋ߬:
{{ߌ ߣߌ߫ ߗߋ߫|ߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫|ߒߠߋ}}
ߛߋ߲߬ߧߊ ߏ߬ ߘߐ߫߸ ߞߙߊߞߏ {{ߌ ߣߌ߫ ߗߋ߫}}
ߟߊߛߐ߬ߘߐ߲߬ߠߌ߲ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ {{{1}}}=ߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫
ߊ߬ ߣߌ߫ {{{2}}}=ߒߠߋ
߸ ߟߊߥߟߏߟߌ:
A little thank you...
for ߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫.
hugs, ߒߠߋ
ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߕߐ߯ߒߕߊ߲ ߦߋ߫ ߕߊ߬ߡߌ߲߬ ߠߊ߫ ߖߊ߬ߡߊߙߌ߬ ߛߊߣߌߡߊ߲ ߏ߬ ߟߋ ߟߴߊ߬ ߞߏߟߊߕߊ߯ߡߢߊ ߘߐ߫. ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߖߊ߬ߡߊߙߌ ߏ߬ ߘߌ߫ ߛߋ߫ ߞߐߦߟߍ߬ߡߊ߲߬ ߠߊ߫߸ ߦߏ߫ ߕߊ߲߬:
{{ߌ ߣߌ߫ ߗߋ߫|ߒߠߋ|ߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫}}
ߏ߬ ߘߌ߫ ߞߐߝߟߌ ߣߌ߲߬ ߠߊߥߟߏ߫:
A little thank you...
for ߒߠߋ.
hugs, ߌ ߟߊ߫ ߛߋߞߏߦߊ ߓߍ߯ ߟߊ߫
{{{1}}}
ߘߌ߫߸ ߊ߬ ߣߌ߫) ߓߊ߯ߙߊ߫ ߘߐߙߐ߲߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߕߐ߯ߒߕߊ߲ ߘߌ߫.ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߛߎ߯-ߎ-ߛߎ߫ ߡߊߟߐ߲ߣߍ߲߫ ߦߋ߫ ߕߐ߮ ߡߊ߬ ߦߴߊ߬ ߦߌ߬ߘߊ߬ߣߍ߲߬ ߦߋ߫ ߘߎ߰ߟߊ ߘߐ߫ ߢߊ ߡߍ߲߸ ߏ߬ ߟߎ߬ ߕߍߣߊ߬ ߛߋ߫ ߟߊ߫ ߛߋ߲߬ߕߘߍ߬ ߟߊ߫ ߞߙߊߞߏ߫ ߘߐ߫߸ ߡߍ߲ ߦߋ߫ ߝߙߍߕߍ ߘߏ߲߬ߖߟߎ߬ߡߊ߬ߣߍ߲ ߝߙߍߕߍ ߟߊߓߊ߯ߙߊ߫ ߟߊ߫. ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߛߎ߯-ߎ-ߛߎ߫ ߡߊߟߐ߲ߣߍ߲߫ ߦߋ߫ ߕߐ߮ ߟߊ߫߸ ߦߴߊ߬ ߦߋ߫ ߘߎ߰ߟߊ ߘߐ߫ ߢߊ ߡߍ߲ ߣߌ߲߬߸ ߏ߬ ߟߎ߬ ߕߍ߫ ߣߊ߬ ߡߊߛߐ߬ߘߐ߲߬ ߠߊ߫ ߞߙߊߞߏ߫ ߟߎ߫ ߓߟߏ߫߸ ߡߍ߲ ߠߎ߬ ߦߋ߫ ߝߙߍߕߍ ߟߊߓߊ߯ߙߊ߫ ߟߊ߫.
ߝߙߍߕߍߦߊ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ
ߞߊ߬ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߊߕߊ߬ߡߌ߲߫ ߝߙߍߕߍ߸ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߓߍ߯ ߡߊߟߐ߲߫߸ ߊ߬ ߟߊߕߊ߬ߡߌ߲߫ ߕߎߡߊ.
{{ߌ ߣߌ߫ ߗߋ߫|߂=ߒߠߋ|߁=ߌ ߟߊ߫ ߕߋߙߌߦߊ ߟߊ߫}}
ߛߋ߲߬ߧߊ ߣߌ߲߬ ߘߐ߫߸ ߞߙߊߞߏ {{ߌ ߣߌ߫ ߗߋ߫}}
ߓߘߊ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ {{߁}}=ߌ ߟߊ߫ ߕߋߙߌߦߊ ߟߊ߫
ߟߊߛߐ߬ߘߐ߲߫߸ ߊ߬ ߣߌ߫ {{߂}}=ߒߠߋ
߸ ߊ߬ ߓߘߊ߫ ߡߊߛߐ߫ ߊ߬ ߢߊߖߎ߮ ߡߊ߬ ߕߋ߲߬ ߝߛߊߦߌ߫߸ ߊ߬ ߣߌ߫ ߟߊߥߟߏ߫ ߕߊ߲߫:
A little thank you...
for ߌ ߟߊ߫ ߕߋߙߌߦߊ.
hugs, ߒߠߋ
- ߟߊߒߡߊ߫ ߘߐ߫
{{ߌ ߣߌ߫ ߗߋ߫|߁=ߒ“=“|߂=ߝߙߊ߬ߟߌ ߟߊ߫}}
ߟߊ߬ߥߟߏ߬ߟߌ:
ߕߐ߯ߟߊߟߌ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ
ߛߌߟߊ߫ ߛߓߊߣߊ߲ ߡߍ߲ ߦߋ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߊߕߊ߬ߡߌ߲߫ ߠߊ߫߸ ߏ߬ ߦߋ߫ ߕߐ߮ ߟߋ߬ ߘߴߌ ߞߘߐ߫ ߝߙߍߕߍߦߊ ߡߊ߬. ߛߋ߲߬߬ߧߊ ߏ߬ ߘߐ߫߸ ߞߙߊߞߏ ߞߣߐߘߐ ߘߌ߫ ߡߊߝߊ߬ߟߋ߲߫ ߞߊ߬ ߞߍ߫:
'''ߌ ߣߌ߫ ߗߋ߫ ߘߋߣߍ߲...''' {{ߊ߬ ߞߎ߲߭}} ߦߋ߫. ߛߘߌ߬ߟߌ߸ {{{}}}
ߒ߬ ߧߋ߫ {{ߊ߬ ߞߎ߲߭}}
ߟߊߓߊ߯ߙߊ߫ ߟߊ߫ ߞߙߊߞߏ ߡߍ߲ ߠߎ߬ ߘߐ߫߸ ߊ߬ ߣߌ߫ {{ߞߟߊ߬ߣߐ}}
ߞߊ߬ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߎ߬ ߓߍ߯ ߡߊߟߐ߲߫ ߝߙߍߕߍ ߞߘߐ߫. ߞߊ߬ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߏ߬ ߟߊߕߊ߬ߡߌ߲߫ ߕߐ߮ ߘߌ߫߸ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߓߍ߯ ߡߊߟߐ߲߫ ߊ߬ ߟߊߕߊ߬ߡߌ߲߫ ߕߎߡߊ:
{{ߌ ߣߌ߫ ߗߋ߫|ߞߟߊ߬ߣߐ=ߒߠߋ|ߊ߬ ߞߎ߲߭=ߞߵߊ߬ ߞߍ߫ ߖߐ߲߫ ߦߴߌߟߋ ߘߌ߫}}
ߛߋ߲߬ߧߊ ߏ߬ ߘߐ߫߸ ߞߙߊߞߏ {{ߌ ߣߌ߫ ߗߋ߫}}
ߘߌ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ {{{ߊ߬ ߞߎ߲߭}}}=ߞߵߊ߬ ߞߍ߫ ߖߐ߲߫ ߦߴߌߟߋ ߘߌ߫
ߟߊߛߐ߬ߘߐ߲߫߸ ߊ߬ ߣߌ߫ {{{}}}=ߒߠߋ
ߊ߬ ߣߌ߫ ߞߊ߬ ߥߟߏ߫:
Template:ߌ ߣߌ߫ ߗߋ߫ ߟߊ߫.
ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ߫ ߕߐ߯ߡߊ ߟߎ߬ ߖߊ߬ߙߌ߬ߒ߬ߕߋ߫ ߟߋ߬ ߞߍߟߌ ߘߐ߫߸ ߏ߬ ߘߐ߫:
{{ߌ ߣߌ߫ ߗߋ߫|ߞߟߊ߬ߣߐ=ߒߠߋ|ߊ߬ ߞߎ߲߭=ߞߵߊ߬ ߞߍ߫ ߌߟߋ ߦߋ߫ ߡߎ߲߬ ߘߌ߫|ߊ߬ ߞߎ߲߭=ߞߵߊ߬ ߞߍ߫ ߔߕߊ߫-ߖߊߙߌ߲ߕߋ ߘߌ߫}}
ߟߊ߬ߥߟߏ߬ߟߌ:
A little thank you...
for ߞߵߊ߬ ߞߍ߫ ߔߕߊ߫=ߖߊߙߌ߲ߕߋ ߘߌ߫.
hugs, ߒߠߋ
ߝߌ߬ߛߊ߬ߡߊ߲߬ߕߋ߬ߦߊ ߡߍ߲ ߦߋ߫ ߡߐ߬ߟߐ߲߬ߦߟߍ߬ߡߊ߲߫ ߕߐ߯ߡߊ ߟߴߌ ߟߊ߫ ߞߙߊߞߏ ߘߐ߫߸ ߏ߬ ߟߋ ߦߴߊ߬ ߞߍ ߘߌ߫ ߥߟߊߞߌ (ߞߊ߬ ߦߟߍ߬ߡߊ߲߫ ߊ߬ ߖߘߍ߬ ߢߍ߫) ߘߌ߫ ߞߍ߬ߙߍߝߍ߬ ߡߐ߬ߟߐ߲߬ߦߟߍߡߊ߲ ߡߊߞߟߌ ߘߐ߫߸ ߏ߬ ߘߌ߫ ߛߋ߫ ߟߊߕߊ߬ߡߌ߲߫ ߠߊ߫߸ ߏ߬ ߟߋ ߦߴߊ߬ ߞߍ߫ ߟߊ߫ ߞߙߊߞߏ ߘߏߝߙߍߕߍ ߝߊ߰ߡߎ߲ ߣߐ߰ߡߊ߲߫ ߞߏߛߓߍ߫ ߣߌ߫ ߡߐ߬ߟߐ߲߬ߦߟߍ߬ߡߊ߲߫ ߦߙߌߞߊ ߞߍ߫ ߘߊ߫ ߦߋ߲߬ ߞߊ߬ߣߌ߲߬.
Spaces and newlines are automatically stripped from the start and end of named parameter names and values, but are preserved in unnamed parameters.
Mixing named and unnamed parameters
If the template supports it, both kinds of parameters can be used in one call.
For example, {{Thankyou|supporting both parameter types|signature=Me}}
results in:
A little thank you...
for supporting both parameter types.
hugs, Me
Be careful when doing this, because it can result in conterintuitive results as unnamed parameter counts are based only on the unnamed parameters, not the named parameters.
For example, {{Thankyou|Me|reason=supporting both parameter types}}
results in:
A little thank you...
for supporting both parameter types.
hugs, {{{2}}}
The template is coded to prefer the named parameter for the reason over the unnamed parameter, resulting in the "Me" being lost and no signature being given.
This results in a default value of {{{2}}} being shown, as explained below.
ߓߐߛߎ߲ ߡߐ߬ߟߐ߲
ߣߴߌ ߞߊ߬ ߟߊߥߊ߬ߟߊ߲߬ߞߌ߫ ߡߍ߲ ߞߍ߫ ߕߐ߫ ߦߋ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߊߛߐ߬ߘߐ߲߫ ߠߊ߫߸ ߞߏ߬ߣߵߊ߬ ߡߴߊ߬ߟߎ߬ ߟߊ߫ ߘߊߘߐߡߌߣߊߞߎ߲ߧߊ ߟߎ߬ ߡߊߛߐ߫߸ ߛߌߟߊ ߣߌ߲߬ ߝߍ߬:
{{ߌ ߣߌ߫ ߗߋ߫}}
ߝߙߍߕߍߦߊ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߘߐ߫߸ ߡߍ߲ ߞߏߟߊߒߞߏߡߊ ߦߋ߫ ߛߊ߲ߝߍ߬ ߌ ߘߌ߫ ߣߊ߬ ߟߊ߬ߓߊ߬ߕߏ߬ߟߌ ߣߌ߲߬ ߛߐ߬ߘߐ߲߫:
A little thank you...
for {{{1}}}.
hugs, {{{2}}}
ߣߌ߫ ߘߊߘߐߡߌߣߊߞߎ߲ߧߊ ߝߋ߲߫ ߡߊ߫ ߡߊߛߐ߫ ߡߎߣߎ߲߬߸ ߞߙߊߞߏ ߦߋ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߖߍ߬ߘߍ ߟߋ߬ ߦߌ߬ߘߊ߬ ߟߊ߫߸ ߞߵߏ߬ ߞߍ߫ ߒߕߟߋߡߊ߬ ߡߐ߬ߟߐ߲߬ ߡߊߟߐ߲ߣߍ߲ ߞߊ߲ߞߕߐߡߊ߬. ߛߋ߲߬ߧߊ ߏ߬ ߘߐ߫߸ ߓߐߛߎ߲ ߡߐ߬ߟߐ߲ ߘߌ߫ ߛߋ߫ ߡߊߛߐ߫ ߟߴߏ߬ ߘߐ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߘߌ߫߸ ߝߊ߲ߓߏ߲ ߣߌߘߐ ߡߐ߬ߟߐ߲ ߘߌ߫ ߛߋ߫ ߟߊߓߊ߯ߙߊ߫ ߟߊ߫ ߣߌ߫ ߡߐ߬ߟߐ߲߬ ߛߌ߫ ߟߊߘߏ߲߬ߣߍ߲߫ ߕߍ߫. ߟߊߒߡߊ߫ ߘߐ߫߸ ߣߌ߫ ߞߙߊߞߏ ߞߣߐߘߐ ߡߊߝߊ߬ߟߋ߲߬ ߘߊ߫ ߞߵߊ߬ ߞߍ߫:
'''ߌ ߣߌ߫ ߗߋ߫ ߘߋߣߍ߲...'''
ߦߋ߫ {{{reason|ߊ߬ ߡߎ߰ߡߍ}}} ߦߋ߫.
ߞߟߊ߬ߥߟߎ߸ {{{ߞߟߊ߬ߣߐ|ߒߠߋ}}}
ߏ߬ ߘߐ߫ {{{reason|everything}}}
ߏ߬ ߦߴߊ߬ ߦߌ߬ߘߊ߬ ߟߊ߫ ߟߋ߬ ߞߏ߫ ߘߊߘߐߡߌߣߊߞߎ߲ߧߊ ߝߋ߲߫ ߕߍ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߞߣߐ߫ {{{reason}}}߸ ߏ߬ ߓߊ߯ ߞߍ߫ ߡߐ߬ߟߐ߲ <code>everything</code> (ߊ߬ ߡߎ߰ߡߍ) ߘߌ߫ ߟߊߓߊ߯ߙߊ߫. ߏ߬ ߡߎߣߎ߲ߧߊ߸ <code><nowiki>{{{signature|me}}}
ߓߐߛߎ߲ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ {{{signature}}}
me
ߡߐ߬ߟߐ߲ ߘߌ߫. ߞߙߊߞߏ ߘߌ߫ ߛߋ߫ ߟߊߥߊ߬ߟߊ߲߬ߞߌ߫ ߟߊ߫ ߞߵߊ߬ ߕߘߍ߬ ߘߊߘߐߡߌߘߊߞߎ߲ߧߊ߫ ߛߌ߫ ߕߍ߫߸ ߢߊ ߢߌ߲߬ ߠߎ߫ ߞߊ߲߬:
A little thank you...
for everything.
hugs, me
{{foo|bar=}}
or {{foo|bar=|baz=qux}}
, the foo
template considers the bar
parameter to be ""
. This is different from omitting the parameter altogether, which leaves it undefined and triggers the default value mechanism described above.{{#if:{{{1|}}}|{{{1|}}}|undefined}}
returns undefined if the parameter is either undefined or empty, while {{{1|undefined}}}
does so only if the parameter is undefined.Often default values are used to specify alternate names of parameters.
ߟߊߒߡߊ߫ ߘߐ߫߸ ߣߌ߬ {{{a|{{{b|}}} }}}
ߦߴߌ ߓߟߏ߫߸ ߞߙߊߞߏ ߘߌ߫ ߛߐ߰ ߡߐ߬ߟߐ߲߬ߦߟߍ߬ߡߊ߲߫ ߕߐ߯ߡߊ a ߢߌߣߌ߲ ߝߟߐ߫ ߡߊ߬.
ߣߴߊ߬ ߢߊߓߐߣߍ߲߫ ߡߊ߫ ߞߍ߫߸ ߊ߬ ߘߌ߫ ߡߐ߬ߟߐ߲߬ߦߟߍ߬ߡߊ߲߫ ߕߐ߯ߡߊ b ߟߊߓߊ߯ߙߊ߫.
ߣߌ߫ "a" ߣߌ߫ "b" ߡߊ߫ ߘߊ߲߬ߠߊߕߍ߰߸ ߊ߬ ߕߍߣߊ߬ ߝߏߦߌ߬ ߦߋ߫ ߟߊ߫.
Passing parameters to other templates
If raw parameter syntax is generated by the above template call, and then passed through to another template, it is not interpreted as a parameter. This means that {{Thankyou2 }}, which just calls {{Thankyou }} with no parameters, does not work: {{thankyou2|everything|me}} → A little thank you... for {{{1}}}. hugs, {{{2}}}
You instead need to explicitly pass the parameter to the other template, i.e if {{Thankyou3 }} contains
{{thankyou|{{{1}}}|{{{2}}}}}
then works properly: {{thankyou3|everything|me}} → A little thank you... for everything. hugs, me
This example does not preserve emptiness vs. undefinedness in parameter values - you would need more complicated syntax if you wanted to do that.
Empty vs undefined parameters
The {{t2demo|| a }}
(refer to {{T2demo }} ), with a double pipe, sets the first parameter to an empty string instead of leaving it undefined.
It produces the output start--middle- a -end
, similar to how {{t2demo|1=|2= a }}
results in start--middle- a -end
.
On the other hand, explicitly setting the parameter "2" to "a," results in the first unnamed parameter being left undefined:
{{t2demo|2= a }} results in start-{{{1}}}-middle- a -end
If the second parameter should not be trimmed, it must be unnamed.
Therefore, you can assign an empty string to the first parameter, but you cannot leave it undefined.
Making emptiness and undefinedness equivalent
Good template coding practices result in passing an empty string to a parameter working the same as not assigning any value. This makes things easier and more consistent.
For example, using p=
can show that a template has a parameter "p" that doesn't have a value yet.
To make an empty string and an undefined value equivalent, use the following approaches:
- Use
{{{p|}}}
exclusively instead of{{{p}}}
orq
where "q" is a non-empty value. - Use conditional checks like
{{#if:{{{p|}}}|..{{{p}}}..|..}}
, to ensure{{{p}}}
is only used when it has a value.
If for some reason you want to treat undefined parameters differently from empty parameters or any other possible value you can compare the same parameter twice with different defaults, i.e {{#ifeq:{{{foo|bar}}}|{{{foo|baz}}}|parameter is defined|parameter is undefined}}
.
Using equals signs in unnamed parameters
Unnamed parameters can include equals signs, but this must be done indirectly. Here are some methods using template:T1demo:
- Default Value for Undefined Parameter
Assign a default value to an undefined parameter:
{{T1demo|{{{1| a=b }}}}}
This renders as: start a=b end
.
- Using the
{{=}}
parser function
Use a parser function that safely includes an equals sign:
{{T1demo| a{{=}}b }}
This renders as: start a=b end
.
- HTML Entities
Replace the equals sign with an HTML entity for display:
{{T1demo| a=b }}
This renders as: start a=b end
.
This renders correctly without affecting the other parameters.
Handling unmatched curly and square brackets
Unmatched curly brackets ({{
, }}
) or square brackets ([[
, ]]
) must be inside nowiki tags or use HTML entities:
- Rendering curly brackets have two options:
- Use
<nowiki>{{</nowiki>
or{
for{
- Use
<nowiki>}}</nowiki>
or}
for}
.
- Use
- Use
[
for[
and]
for]
.
Below are some examples:
- Unmatched curly brackets
{{T1demo| <nowiki>{{</nowiki>content<nowiki>}}</nowiki> }}
This correctly renders the braces without breaking the template.
- Unmatched square brackets
{{T1demo| text [link] more text }}
This correctly renders the braces without breaking the template.
This renders as:
start text [link] more text end
Unmatched pairs not placed in nowiki tags either prevent template expansion or are taken as closing braces for the template call.
Below are some examples:
{{T1demo|abc]]def[[ghi}}
This will not expand correctly because of unmatched brackets.
The correct use:
{{T1demo|abc<nowiki>]]</nowiki>def<nowiki>[[</nowiki>ghi}}
This renders as:
startabc]]def[[ghiend
Template-generated brackets
An alternate technique for passing arguments with unmatched brackets is to wrap them in another template
.
In that situation, (which exists with {{(( }} and {{)) }}) on this wiki), the unmatched brackets will be rendered literally, and not decoded as another template call. For example:
{{t1demo|{{((}}t1demo{{))}}}}
results in: start{{t1demo}}end
When substituting a template, template inclusions are parsed once when the subst happens (with the same caveats explained above) and then a second time when rendering the resulting wikitext. For example:
{{subst:((}}t1demo|foo}}
will expand on save to:
{{t1demo|foo}}
which will then render as:
startfooend
If the wikitext generated via the first subst itself includes "subst:" syntax it will not be processed on the same save, but may be on the next save.
This technique may be used to implement recursive substitutions that take multiple saves to evaluate.
Using pipes in parameter values
A parameter value cannot contain a pipe character (|), because it would be interpreted as the end of that parameter and the start of the next parameter.
This can be worked around by using the parser function {{!}}
, or the HTML entity &124;.
The two methods of doing this have slightly different behavior, which can be relevant in some corner cases like when a template is producing wikitable syntax.
Example:
{{T1demo|abc|def}}
produces:
startabcend
The "def" doesn't display because it is treated as part of another unnamed parameter, which the template does not use.
{{T1demo|abc{{!}}def}}
produces:
startabc|defend
The "def" displays properly.
{{T1demo|abc|def}}
produces:
startabc|defend
The "def" displays properly again.
Formatting template calls using extra parameters
Since templates ignore parameters they are passed but do not handle specifically, they can be used as a way of a adding extra whitespace or unused content to the template call.
For example:
{{template name|foo|bar|baz|mumble|quux}}
is equivalent to, assuming the template doesn't recognize SPACEN as a parameter name:
{{template name|SPACE1=
|foo|SPACE2=
|bar|SPACE3=Random stuff
|baz|SPACE4=
|mumble|SPACE5=
quux
}}
It is also possible to use the same name for each spacer (often the empty string), but this will populate Category:Pages using duplicate arguments in template calls, which many wikis prefer to keep empty to catch instances of user error.
This can be used to make the template render in a way similar to its output, like showing each row of w:Template:Chess position on its own like to make the wikitext also look like a chessboard.
Tracking parameter usage
It may be wise for a template to add a link or category to a page if a certain parameter or combination of parameters is used, to make if possible to easily determine what pages are using a given parameter, and thus what the impacts of changing that parameter in the template would be.
ߡߊ߬ߟߐ߲߬ߦߊ߬ߟߌ
ߝߘߏ߬ߓߊ߬ ߞߍߟߌ ߘߐ߫߸ ߞߙߊߞߏ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߦߋ߫ ߣߐ߬ߘߐߓߌ߬ߟߊ߬ ߟߊ߫ ߞߙߊߞߏ ߘߐ߫ ߝߍߙߍ߲ߝߍߙߍ߲ߠߌ߲ ߞߐ ߟߋ߬ ߘߐ߫߸ ߞߏ߬ߣߌ߲߬ ߦߏ߫ ߕߊ߲߬. ߊ߬ߟߎ߬ ߕߍߣߊ߬ ߖߊ߬ߕߋ߬ߓߐ߫ ߟߊ߫ ߝߏ߫ ߣߴߊ߬ߟߎ߫ ߟߊߓߊ߯ߙߊ߫ ߘߊ߫.
ߞߐߝߟߌ߫ ߞߋߟߋ߲߫ ߠߋ߬ ߦߴߏ߬ ߟߊ߫.
- If you have a
Template:Start
containing{{mytemplate
, and aTemplate:End
containing|foo=bar}}
, and put{{start}}{{end}}
on a page, mytemplate isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. ߌ ߘߌ߫ ߛߋ߫ ߞߙߊߞߏ ߟߊߓߊ߯ߙߊ ߕߏ߫ ߟߴߌ ߘߐ߫ ߞߊ߬ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߕߐ߮ ߞߙߐ߬ߛߌ߫߸ ߞߏ߬ߣߌ߲߬ ߌ ߕߴߛߋ߫ ߞߙߊߞߏ ߕߍߟߍ߲߫ ߠߊ߫ ߞߵߊ߬ ߞߟߌ߫ ߞߙߊߞߏ߫ ߓߊߟߌߣߍ߲ ߠߎ߬ ߘߐ߫. - ߞߐߝߟߌ߫ ߝߌߟߊߣߊ߲ ߡߍ߲ ߦߴߏ߬ ߟߊ߫ ߏ߬ ߟߋ ߦߋ߫ dead-code ߡߊߕߊ߯ߟߌ ߘߌ߫. If you make a template call like
{{foo|{{DISPLAYTITLE:Bar}} }}
, andTemplate:Foo
does not contain {{{1}}}, then theDISPLAYTITLE
is not used, since it is only evaluated when needed, and there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using Extension:ParserFunctions , and can be especially noticed when used in combination with theint:
magic word that varies by user language. This isn't perfect, and in some cases even if the result of expanding a template is not used (because it is part of an if statement condition, for example), the process of evaluating it can still have side effects. For example, any links produced or other templates used will still be added to Special:WhatLinksHere even if they are not displayed.
Template parameters are pass by value, which means a template cannot modify its arguments. Parameters are treated as associative array, and parameter names are evaluated before parameter values. If the same parameter name is given more than once (either as named or unnamed), only the last instace is used, and the page is added to Category:Pages using duplicate arguments in template calls.
Template calls starting with the magic word subst:
or safesubst:
are evaluated in a separate first pass that only happens at save time, along with ~~~~ and links using the pipe trick.
If they cannot be evaluated during the first pass, subst:
calls are ignored, and safesubst:
are treated as if a normal template.
Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker". This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.
ߖߘߍ߬ߞߍ߬ߒ߬ߞߏ߬ߘߌ ߞߙߊߞߏ ߟߎ߬ ߘߐ߫
ߤߊߟߌ߬ ߞߙߊߞߏ ߖߘߍ߬ߞߊߣߌ߲ ߕߴߛߋ߫ ߡߋߘߌߦߊߥߞߌ߫ ߝߏ߬ߦߌ߬ ߓߊ߲ߓߊߟߌߦߊ ߖߘߍ߬ߞߍ߬ߒ߬ߞߏ߬ߘߌ ߘߌ߫.
ߡߋߘߌߦߊߥߞߌ߫ ߘߌ߫ ߣߊ߬ ߖߘߍ߬ߞߍ߬ߒ߬ߞߏ߬ߘߌ ߟߎ߬ ߟߊߟߐ߬߸ ߡߍ߲ ߠߎ߬ ߞߙߊߞߏ ߕߐ߮ ߦߋ߫ ߛߓߍߘߋ߲߫ ߞߎ߲ߓߊ ߘߌ߫.
ߟߊߒߡߊ߫ ߘߐ߫߸ ߣߌ߫ ߞߙߊߞߏ ߞߣߐߘߐ "ߞߙߊߞߏ:Aaaa" ߦߋ߫ "a {{Aaaa}} z
" ߟߋ߬ ߘߌ߫߸ ߊ߬ ߘߌ߫ ߦߌ߬ߘߊ߬ "a a Template loop detected: Template:Aaaa z z" ߘߌ߫߸ ߊ߬ ߣߌ߫ ߞߊ߬ ߟߊߓߊ߯ߙߊ߫.
This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments.
In this forbidden example template:d
can either be called {{d|20200311}}
or {{d|y=2020|m=3|d=11}}
.
If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path.
{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}
If template:d
is modified to recurse into template:d/2
and template:d/2
is an identical manual copy of template:d
this idiom works fine as the self-recursion safeguard operates dynamically and not statically.
A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner.
If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour.
Tables in parameters
Since the pipe character (|
) and equality sign (=
) have different meanings in template calls and wikitables, in order to use table markup in the value of a template parameter one generally needs to "escape" those characters (i.e., protect them from interpretation as template markup) using special sequences:
- the built-in magic word
{{!}}
provides an "escaped" version of|
since MediaWiki 1.24 - the built-in magic word
{{=}}
provides an "escaped" version of=
since MediaWiki 1.39
Before the introduction of these magic words, many wikis used templates to accomplish the same things. On such a wiki, the magic words take precendence over the same-named templates.
Example table
A | B | C |
---|---|---|
A1 | B1 | C1 |
A2 | B2 | C1 |
Table code:
{| class=wikitable
!A!!B!!C
|-
|A1||B1||C1
|-
|A2||B2||C1
|}
Escaped table code:
{{{!}} class{{=}}wikitable
!A!!B!!C
{{!}}-
{{!}}A1{{!}}{{!}}B1{{!}}{{!}}C1
{{!}}-
{{!}}A2{{!}}{{!}}B2{{!}}{{!}}C2
{{!}}}
Note that the first left-brace ({
) is interpreted as a literal left-brace character because it is immediately followed by the {{!}}
magic word.
Similarly, the last right-brace (}
) is interpreted as a literal right-brace character because it is immediately preceeded by the same magic word.
However, in some cases these brace characters do cause problems, so some wikis provide templates for escaping these characters, as well:
- the template call
{{(}}
might provide an "escaped" version of{
- the template call
{{)}}
might provide an "escaped" version of}
Some wikis go even further and provide other convenience templates like {{(!}} ({|
), {{!)}} (|}
), {{!!}} (||
).
On such a wiki, the code can be simplified a bit to this form:
{{(!}} class{{=}}wikitable
!A!!B!!C
{{!}}-
{{!}}A1{{!!}}B1{{!!}}C1
{{!}}-
{{!}}A2{{!!}}B2{{!!}}C2
{{!)}}
ߞߙߊߞߏ ߖߘߍ߬ߞߍ߬ߒ߬ߞߏ߬ߘߌ ߡߊߡߊ߬ߙߊ
ߓߐߛߎ߲ ߡߊ߬߸ ߞߙߊߞߏ ߞߣߐߘߐ ߦߋ߫ ߟߊߓߊ߯ߙߊ߫ ߟߊ߫ ߊ߬ ߡߎ߰ߡߍ ߟߋ߬ ߘߌ߫ ߢߊ߫ ߝߌ߬ߟߊ߫ ߡߊ߬߸ ߌ ߓߊ߯ ߞߴߊ߬ ߖߍ߬ߘߍ ߘߐߜߍ߫ ߟߊ߫ ߒߕߟߋߡߊ߬߸ ߊ߬ ߣߌ߫ ߣߴߌ ߞߍ߫ ߘߴߊ߬ ߟߊߘߏ߲߬ ߠߊ߫ ߞߐߜߍ߫ ߜߘߍ߫ ߟߊ߫. ߏ߬ ߕߎ߬ߡߊ ߝߍ߬߸ ߌ ߘߌ߫ ߛߋ߫ ߞߙߊߞߏ ߝߊ߲߭ ߡߍ߲ ߠߎ߬ ߡߊߡߙߊ߬ ߟߊ߫߸ ߏ߬ ߟߎ߫ ߘߌ߫ ߦߋ߫ ߊ߬ ߣߌ߫ ߞߊ߬ ߟߊߘߏ߲߬ $noinclude ߟߊߓߊ߯ߙߊ ߟߊ߫߸ ߊ߬ ߣߌ߫ $includeonly ߣߌ߫ $onlyinclude ߟߎ߬ ߟߊ߫
The template's page when viewed directly appears exactly as the template would render without any parameters. If the template requires parameters to function properly, this will result in raw wikitext syntax or errors as a result of them being missing.
For example:
- If a parameter has no default value, it shows as the literal text {{{1}}}, indicating the template needs a parameter.
- If a parameter has an empty default value (it is written as {{{1|}}}), it displays nothing, which achieves the intended effect but lacks clarity for self-documentation. Using a non-empty default value like
{{{1|$1}}}
could clarify a parameter's role, especially for templates involving images. - If a parameter without a default is passed to the
#expr
parser function, it results in an error message: "Expression error: unrecognized punctuation character '{'." - If a template creates a table, it's helpful for the template page to show the table's structure rather than the wikitext used to make it. To do this, the table syntax isn't enclosed in tags, and each table element includes both
<noinclude>...</noinclude>
and<includeonly>...</includeonly>
parts where needed.
However, you can control which parts of a template will be seen and included by the use of the <noinclude>
, <includeonly>
and <onlyinclude>
tags.
ߝߋ߲ ߛߎ߯-ߎ-ߛߎ߫ ߦߋ߫ <noinclude>
ߣߌ߫ </noinclude>
ߕߍߟߊ ߘߐ߫߸ ߏ߬ ߟߎ߬ ߘߌ߫ ߞߍ߫ ߦߋߕߊ ߘߌ߫ ߘߐߙߐ߲߫ ߣߌ߫ ߞߙߊߞߏ ߞߐߜߍ ߞߍ߫ ߘߊ߫ ߦߋߕߊ ߘߌ߫ ߒߕߟߋߡߊ߬߸ ߒ߬ߞߵߊ߬ ߕߍ߫ ߘߋ߬ ߣߴߊ߬ ߞߍ߫ ߘߊ߫ ߟߊߘߏ߲߬ ߠߊ߫ ߞߐߜߍ߫ ߜߘߍ߫ ߟߊ߫. ߏ߬ ߦߋ߫ ߟߊߓߊ߯ߙߕߊ ߞߏߟߌߞߏߟߌ߫ ߟߋ߬ ߘߌ߫ ߣߴߌ ߞߍ߫ ߘߊ߫ ߛߓߍߟߌ ߥߟߊ ߘߏߞߊ߲ (code) ߟߊߘߏ߲߬ ߠߊ߫ ߞߙߊߞߏ ߘߏ߫ ߘߐ߫ ߌ ߕߍ߫ ߡߍ߲ ߝߘߎߝߘߎ߫ ߞߏ߫ ߘߐ߫ ߞߐߜߍ߫ ߛߌ߫ ߟߊ߫߸ ߊ߬ ߟߊߘߏ߲߬ߣߍ߲߫ ߦߋ߫ ߡߍ߲ ߠߎ߬ ߟߊ߫߸ ߦߏ߫ ߕߊ߲߬:
- ߦߌߟߡߊ ߛߘߌ߬ߜߋ߲ ߣߌ߫ ߞߙߊߞߏ ߖߍ߬ߘߍ ߞߍ߫ ߘߊ߫ ߦߌߟߡߊߦߊ߫ ߟߊ߫
- ߞߊ߲ߣߌߢߐ߲߯ߕߍ ߛߘߌ߬ߜߋ߲ ߞߙߊߞߏ߫ ߡߎߣߎ߲ߣߍ߲ ߠߎ߬ ߟߊ߫ ߞߊ߲߫ ߘߐ ߟߎ߬ ߘߐ߫
- ߘߊ߲߬ߕߍ߰ߟߌ߬ ߛߓߍ ߞߙߊߞߏ ߟߊߓߊ߯ߙߊߟߌ ߞߍߢߊ ߞߊ߲߬ It's a common pattern on some wikis to use a template like {{Documentation }} to transclude the documentation from a subpage of the template. For example, Template:Void is documented at Template:Void/doc.
ߊ߬ ߣߌ߫ ߝߣߊ߫߸ ߝߋ߲ ߛߎ߯-ߎ-ߛߎ߫ ߦߋ߫ <includeonly>
ߣߌ߫ </includeonly>
ߟߎ߫ ߕߍߟߊ ߘߐ߫߸ ߏ߬ ߟߎ߫ ߟߋ߬ ߦߋ߫ ߝߘߎߝߘߎ߫ ߟߴߊ߬ ߣߌ߫ ߞߵߊ߬ ߟߊߓߊ߯ߙߊ߫ ߘߐߙߐ߲߫ ߣߌ߫ ߞߐߜߍ ߞߍ߫ ߘߊ߫ ߟߊߘߏ߲߬ ߠߊ߫߸ ߒ߬ߞߵߊ߬ ߕߍ߫ ߘߋ߬ ߣߌ߫ ߞߙߊߞߏ ߞߐߜߍ ߟߎ߬ ߞߍ߫ ߘߊ߫ ߦߋߕߊ ߘߌ߫ ߒߕߋߟߋ߲ߡߊ߬߸ ߊ߬ ߣߴߊ߬ ߦߋ߫ ߟߊߓߊ߯ߙߕߊ߫ ߞߏߟߌߞߏߟߌ ߘߌ߫ ߟߌ߬ߤߟߊ ߟߎ߬ ߘߐ߫ ߦߏ߫ ߕߊ߲߬:
- ߞߐߜߍ ߟߎ߬ ߦߌߟߡߊߦߊߟߌ ߞߙߊߞߏ ߟߊߘߏ߲߬ߣߍ߲߫ ߦߋ߫ ߡߍ߲ ߠߎ߬ ߟߊ߫.
- ߞߟߏߜߍ: ߣߌ߫ ߞߙߊߞߏ ߟߊ߫ ߦߌߟߡߊ߫ ߟߊߘߏ߲߬ߣߍ߲ ߠߎ߬ ߞߍ߫ ߘߊ߫ ߡߊߝߊ߬ߟߋ߲߬ ߠߊ߫ ߞߍߢߊ ߣߌ߲߬ ߘߐ߫߸ ߞߐߜߍ ߟߎ߬ ߦߌߟߡߊߦߊߟߌ ߡߍ߲ ߠߎ߬ ߞߙߊߞߏ ߏ߬ ߟߎ߬ ߟߊߘߏ߲߬ߣߍ߲߬ ߦߋ߫ ߡߍ߲ ߠߎ߬ ߟߊ߫߸ ߏ߬ ߟߎ߬ ߕߍߣߊ߬ ߛߋ߫ ߟߊ߫ ߟߊߞߎߘߦߊ߫ ߟߊ߫ ߝߏ߫ ߣߌ߫ ߥߊ߯ߕߌ ߘߏ߫ ߕߊ߬ߡߌ߲߬ ߘߊ߫: ߏ߬ ߟߎ߬ ߦߋ߫ ߘߐߓߍ߲߬ ߠߊ߫ job queue ߟߋ߬ ߓߟߏ߫. ߞߊ߬ ߞߐߜߍ߫ ߞߙߍߞߙߍߣߍ߲ ߦߌߟߡߊߦߊߟߌ ߡߊߛߊ߬ߦߌ ߞߘߊߡߊ߫߸ ߞߐߜߍ ߏ߬ ߘߊߦߟߍ߬ ߡߊ߬ߦߟߍ߬ߡߊ߲߬ߠߌ߲߬ ߞߊ߲ߡߊ߬߸ ߊ߬ ߣߌ߫ ߞߵߊ߬ ߟߊߞߎ߲߬ߘߎ߫ ߞߵߊ߬ ߕߘߍ߬ ߌ ߡߊ߬ ߡߝߊ߬ߟߋ߲߬ߠߌ߲߬ ߞߍ߫.
- ߘߍ߲߬ߞߣߍ߬ߦߊ߫ ߝߟߐ߫ ߞߏ߫ ߞߙߊߞߏ ߘߏߞߊ߲ ߕߍߣߊ߬ ߟߥߊߟߌ߫ ߟߊ߫ ߞߙߊߞߏ ߞߐߜߍ ߖߍ߬ߘߍ ߡߊߝߟߍ ߓߊ߯ ߞߴߌ ߘߐ߫. ߊ߬ ߝߊ߲߬ߓߊ ߘߐ߫ ߏ߬ ߦߋ߫ ߟߋ߬ ߓߊ ߏ߬ ߓߌ߬ߟߊ߬ߣߍ߲߫ ߦߋ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߟߋ߬ ߡߊ߬߸ ߊ߬ ߣߴߊ߬ ߟߥߊߟߌ ߣߌ߫ ߟߊ߬ߓߍ߲߬ߢߐ߲߰ߡߦߊ߬ߘߊ ߕߍ߫߸ ߏ߬ ߦߋ߫ ߞߐߝߟߌ߫ ߘߐߞߕߌߓߊߟߌ ߟߋ߬ ߘߌ߫.
ߝߋ߲ ߛߎ߯-ߎ-ߛߎ߫ ߦߋ߫ <noinclude>
ߣߌ߫ <includeonly>
ߟߎ߫ ߞߐߞߊ߲߬ ߏ߬ ߟߎ߬ ߖߙߎߡߎ߲ ߦߋ߫ ߦߟߍ߬ߡߊ߲߬ ߠߴߊ߬ ߣߌ߫ ߞߵߊ߬ ߟߊߓߊ߯ߙߊ߫ ߊ߬ ߢߊߓߘߍ ߡߊ߬: ߏ߬ ߦߋ߫ ߝߌ߬ߟߊ߫ ߟߋ߬ ߘߌ߫߸ ߞߙߊߞߏ ߞߐߜߍ ߞߍ߫ ߘߊ߫ ߦߋ߫ ߟߊ߫ ߒߕߟߋߡߊ߬ ߊ߬ ߣߌ߫ ߣߌ߫ ߞߙߊߞߏ ߟߊߘߏ߲߬ ߘߊ߫ ߞߐߜߍ߫ ߜߘߍ߫ ߟߊ߫.
The focus is on what is inside these two tags.
ߝߋ߲ ߛߎ߯-ߎ-ߛߎ߫ ߦߋ߫ <onlyinclude>
ߘߎ߲ߛߓߍ ߞߐߞߊ߲߬߸ ߏ߬ ߓߍ߯ ߛߋ߲߬ߓߐ߫ ߕߐ߫ ߟߋ߬ ߟߥߊ߬ߟߊ߲߬ߞߌ߬ߟߌ ߘߐ߫.
ߤߊߟߌ߬ ߕߍߕߍ߮ ߡߍ߲ ߠߎ߬ ߞߏ߲߭ ߦߋ߫ includeonly ߘߐ߫߸ ߏ߬ ߟߎ߫ ߢߌ߬ߣߊ߬ߓߐ߬ߣߍ߲߫ ߠߋ߬ ߦߋ߫ ߟߥߊ߬ߟߊ߲߬ߞߌ߬ߟߌ ߘߐ߫ ߝߏߣߴߊ߬ߟߎ߫ ߝߣߊ߫ ߕߊ߯ߦߙߐ ߞߍ߫ onlyinclude ߘߐ߫.
The focus is only on what is inside this tag.
For example, if a page like Help:Templates/onlyinclude demo has the wikitext:
abc<onlyinclude>def</onlyinclude>ghi<includeonly>jkl</includeonly>
The result of transcluding it is def.
Nesting of these tags is also possible.
The three partial transclusion tags enable all possible combinations of what is processed and rendered.
Comments also fill a role.
Inclusion tags are respected when using {{subst:templatename}}
, but they are not respected when using {{msgnw:templatename}}
as that displays the raw wikitext without any processing.
Section transclusion
To transclude different sections of a template on different pages, you can wrap the content in onlyinclude tags and use an if statement on parameters to select which section.
Consider "Template:Example" with this wikitext:
== Section 1 ==
{{#ifeq:{{{1|1}}}|1|
Content of section one.
}}
{{#ifeq:{{{1|2}}}|2|
== Section 2 ==
Content of section two.
}}
This will render both sections on the example page itself, and allow other pages to transclude the first section with {{example|1}}
and the second section with {{example|2}}
.
Another approach is to use literal parameter syntax instead:
{{{section1|
== Section 1 ==
Content of section one.
}}}
{{{section2|
== Section 2 ==
Content of section two.
}}}
Transclude the first section with {{example|section2=}}
and the second section with {{example|section1=}}
.
If neither parameter is used, then both sections will display.
A third approach is to use Labeled Section Transclusion.
ߞߙߊߞߏ ߛߌ߲߬ߝߏ߲߬ߧߊ߬ߟߌ
ߟߊߒߡߊ߫ ߘߐ߫ ߛߴߊ߬ ߘߌ߫ ߞߍ߫ ߓߍ߲߬ߣߍ߲ ߘߌ߫߸ ߟߥߊ߬ߟߌ߬ߟߊ ߞߊ߫ ߞߊ߲߫ ߞߵߊ߬ߟߎ߬ ߢߌߣߌ߲߫߸ ߊ߬ ߣߌ߫ ߞߵߊ߬ߟߎ߬ ߟߊߓߊ߯ߙߊ߫ ߢߊ ߢߊߢߌߣߌ߲߫.
ߖߐ߲߬ߛߊ߫ ߞߵߊ߬ߟߎ߫ ߢߌߣߌ߲߫߸ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ ߘߌ߫:
- ߞߐߜߍ߫ ߞߙߍߞߙߍߣߍ߲ ߠߎ߬ > ߞߐߜߍ ߟߎ߬ ߓߍ߯ ߛߐ߲߬ߞߌ߲߫
- ߕߐ߯ ߛߓߍ ߞߣߍ: ߛߙߍߘߍ ߘߐ߫߸ ߞߊ߬ ߞߙߊߞߏ ߛߎߥߊ߲ߘߌ߫ ߊ߬ ߣߌ߫ ߥߊ߫ ߛߐ߲߬ߞߌ߲߫.
ߖߐ߲߬ߛߊ߫ ߞߊ߬ ߟߊ߬ߓߊ߰ߙߊ߬ߟߌ ߞߌ߬ߓߊ߬ߙߏ߬ߦߊ ߘߌ߫߸ ߟߊߒߡߊ߫ ߘߐ߫ ߦߏ߫ ߣߌ߲߬ ߦߋ߫ ߢߊ ߡߍ߲ ߞߙߊߞߏ ߞߐߜߍ ߘߐ߫:
<noinclude> ==ߟߊ߬ߓߊ߰ߙߊ߬ߟߌ== ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ ߣߌ߫ ߛߣߍ߫: {{Thankyou|reason=your reason=your signature}}</noinclude>
ߏ߬ ߓߊ߯ ߞߍ߫߸ ߛߓߍߦߟߊ ߘߌ߫ ߛߋ߫ ߞߏߟߊߒߞߏߡߊ ߓߊߓߌ߬ߟߊ߬ ߟߊ߫ ߞߵߊ߬ ߟߊߕߊ߬ߡߌ߲߫ ߞߵߊ߬ ߟߊߓߊ߯ߙߊ߫ ߞߙߊߞߏ ߘߌ߫.
While editing a page, a list of all templates used is available under the editing form, in a collapsible section titled "ߞߙߊߞߏ ߟߎ߫ ߟߎ߫ ߟߊߓߊ߯ߙߊ߫ ߘߊ߫ ߞߐߜߍ ߣߌ߲߬ ߘߐ߫" (also named "ߞߙߊߞߏ ߟߎ߬ ߟߋ߬ ߟߊߓߊ߯ߙߊ߫ ߣߍ߲߫ ߢߍߦߋߟߌ ߣߌ߲߬ ߘߐ߫", or "ߞߙߊߞߏ ߟߎ߬ ߟߋ߬ ߟߊߓߊ߯ߙߊ߫ ߣߍ߲߫ ߕߍߕߍ߮ ߣߌ߲߬ ߘߐ߫:" depending on the context). This list provides a convenient link to the template's page, as well as information about its protection status. Redirected templates are shown in italics, with the redirect target added as a separate list item.
ߛߘߌ߬ߜߋ߲߬ߦߊ߬ߟߌ ߞߙߊߞߏ ߘߏ߫ ߟߊ߫
ߞߙߊߞߏ ߞߐߜߍ ߘߌ߫ ߛߋ߫ ߞߍ߫ ߟߊ߫ ߛߘߌ߬ߜߋ߲ ߘߌ߫ ߦߏ߫ ߥߞߌ߫ ߞߐߜߍ ߕߐ߭ ߟߎ߬ ߦߋ߫ ߢߊ ߡߍ߲. ߟߊߒߡߊ߫ ߘߐ߫߸ Template:Navbar ߟߊߞߊ߬ߝߏ߬ߣߍ߲߬ ߦߋ߫ ߞߊ߬ ߥߞߌ ߘߏߝߙߍߕߍ ߟߊߓߊ߯ߙߊ߫ [[Template:Navbar]]
.
On many wikis, Template:Tl can be used to provide a link to a template formatted in a way that shows the "double curly-braces" wikicode necessary to transclude the template without actually doing the tranclusion. For example, the code {{tl|Navbar}}
may be used to create the link {{Navbar }}.
This construct is commonly used when referring to templates in template documentation, on help pages, and on talk pages.
The same effect can be achieved by using {{[[Template:Navbar|Navbar]]}}
, but the {{Tl }}
approach involves much less typing.
On any given wiki the Tl template, if it exists, may or may not render the text in a "code" element or as monospace type.
If not (as on this wiki), another similarly named template may do so.
See, for example, the "See also" section of our Template:Tl documentation.
Template naming
The name of a template is case-sensitive excluding the first character.
You make redirects for alternate capitalizations.
For example, if a template is named "AdminAbbr", you can create a redirect named "Adminabbr".
This way, the template can be called with either {{AdminAbbr}}
or {{adminabbr}}
.
If an editor prefers a mix of upper and lower case for clarity, they can use functions like lc or uc.
For instance, instead of {{CURRENTINTERNETTIME}}
, they could use {{ {{uc:CurrentInternetTime}} }}
Because template names are interpreted in the same way to the names of other pages, underscores are replaced with spaces, and any text after a number sign (what would be a anchor in a standard link) is ignored.
An underscore _
can be alternative to a blank space.
Possible uses of templates
Templates can be used for any situation in which one wants two or more pages to contain identical or similar content that is edited together rather than independently. They can be used to:
- Provide structured elements on many pages, like infoboxes, maintenance templates, navigational boxes, etc.
- Perform calculations used as a programming tool on various pages, like w:Template:Sum.
- Build composite pages that display the content of multiple existing pages together, like w:WP:Village pump (all) which includes content from each section of the village pump. The content of these pages can either be shown individually, or together, but the revision history, watchlist, etc. will only pick up changes to the transcluded pages and the raw wikitext of the composite page itself, not implicit changes to the composite page.
- Share some content between a few related pages. For example, the list at Help:Preferences#Beta features is duplicated at Beta Features#Current Beta Features. While on MediaWiki.org that is built using Extension:LabeledSectionTransclusion instead, it could have been done using a template.
- Store content referenced multiple times on the same page, so it only has to be written and calculated once. For example w:Template:Cite Monumentenregister/URL is called twice by w:Template:Cite Monumentenregister in two different places, and using another template means the URL pattern only has to be written once in the base template.
- Use templates as a programming element to generate a loop: if Template:A calls Template:B 10 times with different parameters, then that crudely simulates a for loop. If Template:B calls Template:C 10 times, then you have a nested loop of 100 calls of Template:C. But keep in mind that it is easy to run into the template limits when using templates as advanced programming constructs, and using Scribunto is generally clearer and easier to follow.
ߓߊߓߌߟߊߟߌ ߞߊ߬ ߓߐ߫ ߥߞߌ ߘߏ߫ ߘߐ߫ ߞߊ߬ ߕߊ߯ ߘߏ߫ ߜߘߍ߫ ߘߐ߫
It is possible, if allowed by the wiki configuration to transclude templates from other wikis. This configuration setting is disabled on Wikimedia wikis. Otherwise, you need to manually copy the template and its dependencies from the source wiki to the destination wiki to use it.
ߞߙߊߞߏ ߡߊ߬ߞߏ ߦߋ߫ ߞߍ߫ ߟߊ߫ CSS ߟߊ߫ ߞߍ߬ߣߍ߲ ߥߟߊ߫ ߞߙߊߞߏ߫ ߜߘߍ ߟߎ߫߸ ߏ߬ ߘߐ߫ ߟߊ߬ߓߊ߰ߙߊ߬ߟߊ ߦߋ߫ ߕߏ߫ ߟߊ߫ ߜߟߍ߬ߦߊ ߛߐ߬ߘߐ߲߬ ߠߊ߫ ߓߊߓߌߟߊߟߌ ߘߐ߫ ߛߐ߲߬ ߞߊ߬ ߓߐ߫ ߥߞߌ ߘߏ߫ ߘߐ߫ ߞߊ߬ ߕߊ߯ ߥߞߌ߫ ߜߘߍ߫ ߘߐ߫. ߒ߬ߓߊ߬ ߞߍߢߊ ߡߍ߲ ߠߎ߬ ߦߋ߫ ߘߎ߰ߟߊ߫ ߏ߬ ߟߎ߬ ߘߌ߫ ߛߋ߫ ߓߊ߯ߙߊ߫ ߟߊ߫ ߞߙߊߞߏ ߝߊ߲߬ߓߊ ߟߊ߫.
The steps below should work for most templates.
ߡߋߘߌߦߊߥߞߌ ߘߏߝߙߍߕߍ
ߣߌ߫ (ߟߊ߬ߛߣߍ߬ߣߍ߲ߟߊߦߍ߬ߟߍ ߞߙߍߞߙߍߦߊߟߌ «specifically inportupload») ߞߍ߫ ߘߴߌ ߓߟߏ߫ ߥߞߌ߫ ߞߎߘߊ ߟߊ߫:
- ߕߊ߯ $ߟߊ߬ߝߏ߬ߦߌ߬ߟߌ ߞߊ߲߬ ߥߞߌ ߓߊߞߘߐ ߟߊ߫߸ ߞߊ߬ .xml ߞߐߕߐ߮ ߘߏ߫ ߟߊߖߌ߰ ߌ ߞߎ߲߬ ߞߙߊߞߏ ߓߍ߯ ߘߐ߬ߝߐ߫ ߞߘߎ߬ߜߍߟߍ߲ ߠߎ߬ ߘߐ߫߸ ߦߴߊ߬ ߕߎ߲߰ߣߍ߲߫ ߦߋ߫ ߢߊ ߡߍ߲ ߡߊ߬ ߣߌ߲߬:
- ߞߙߊߞߏ ߕߐ߮ ߟߊߘߏ߲߬ ߞߟߏߘߋ߲߫ ߞߎ߲ߓߊ ߞߏ߲߬ߘߏ ߘߐ߫߸ ߊ߬ ߣߌ߫ (ߏ߬ ߟߊߡߎߣߎ߲ߧߊ ߟߎ߬)߸ "ߞߙߊߞߏ:ߣߌ߫ ߛߣߍ߫". ߒ߬ߓߊ߬ ߌ ߖߊ߲߬ߕߏ߫ ߞߏߟߌߞߏߟߌ߫ ߞߵߊ߬ ߞߟߏߘߋ߲ߞߎ߲ߓߦߊ߫ ߊ߬ ߣߌ߫ ߞߟߏ߫ ߞߙߍߞߙߍߣߍ߲ – ߣߌ߫ ߞߙߊߞߏ ߕߐ߮ ߓߍ߲߬ߣߍ߲߫ ߡߊ߫ ߞߴߊ߬ ߢߊ ߖߍ߬ߘߍߖߍ߬ߘߍ ߡߊ߬߸ ߟߊ߬ߝߏ߬ߦߌ߬ߟߌ ߘߌ߫ ߛߋ߫ ߞߍ߫ ߟߊ߫ ߞߏ߬ߣߌ߲߬ xml ߘߐ߬ߛߙߋ ߟߎ߬ ߕߍߣߊ߬ ߞߍ߫ ߟߊ߫ ߘߐ߬ߛߙߋ߬ ߦߋߕߊ ߘߌ߫.
- "ߊ߬ ߟߊߘߏ߲߬ ߞߙߊ߬ߞߏ ߘߐ߫" ߞߏ߲߬ߘߏ ߓߊߕߐ߬ߡߐ߲߫
- "Include only the current revision, not the full history" ߞߏ߲߬ߘߏ ߓߊߕߐ߬ߡߐ߲߫
- "ߟߊ߬ߝߏ߬ߦߌ߬ߟߌ" ߛߐ߲߬ߞߌ߲߫
- ߕߊ߯ ߞߙߍߞߙߍߣߍ߲:ߟߊ߬ߛߣߍ߬ߟߌ ߞߊ߲߬ ߥߞߌ߫ ߞߎߘߊ ߞߊ߲߬ ߊ߬ ߣߌ߫ xml ߞߐߕߐ߮ ߟߊߦߟߍ߬.
ߣߌ߫ ߟߊ߬ߛߣߍ߬ߟߌ ߤߊߞߍ߫ ߡߊ߫ ߞߴߌ ߓߟߏ߫ ߥߞߌ߫ ߞߎߘߊ ߞߊ߲߬:
- Go to the template you want to copy from the original wiki. Go to the edit page, and copy all the wikitext
- On the new wiki, go to the page with the same name as the template you copied. Hit create/edit and paste the wikitext you copied. In the edit summary of each template, link to the original page for attribution.
- Back in the original wiki at the edit window, below the edit box, look at the list of "Templates used on this page". For each template listed follow these instructions. Also do that for any template used by any of these templates, and so on.
This will copy the entire code necessary, and will suffice for some templates. Note that only page elements parsed in rendering the page get exported, consequently documentation subpages are not exported as part of this process. If it doesn't work also check for red links listed under "Pages transcluded onto the current version of this page:", below the edit box. If there are any repeat the above steps for these as well and also copy the code in the modules.
After successfully importing the template and all its linked templates from the other wiki, edit it to change customisations to suit your wiki. For example to change a logo, remove redundant categories or red links.
Extensions
An extension often used in templates is ParserFunctions. Visit page Extension:ParserFunctions and check if any of the functions listed there are used in the templates you've copied. If so, you have to install the ParserFunctions extension. To install it, you'll need system admin access to the server of your MediaWiki installation.
Another dependency that may be used in templates, especially those on Wikipedia, is Lua. Having {{#invoke: }}
in template code is a good sign for it.
In case it's used, you need to install the Scribunto extension and system admin access is required too.
See that page for more instructions about installing and using the extension.
CSS and JavaScript code
Besides MediaWiki code, many templates make use of CSS and some rely on JavaScript to work fully. If the copied templates are not behaving as expected, this may be the cause. To copy the required CSS and JavaScript to your wiki you'll normally need to have admin privileges, because you'll be editing system messages in the "MediaWiki:" namespace.
- Look for the use of CSS classes (text like
class="foobar"
) in the template text. If those classes appear in "MediaWiki:Common.css" or "MediaWiki:Monobook.css" on the original wiki, copy those classes to "MediaWiki:Common.css" on the new wiki and check if the template is now fine.
- If the copied template is still not working as expected, check if there is code in "MediaWiki:Common.js" or "MediaWiki:Monobook.js" on the original wiki. If so, you can try copying it to "MediaWiki:Common.js" on the new wiki. Normally, it is a good idea to only copy code from trusted sources, and browse the code to identify and select the relevant parts. You may find comments that can serve as clues to identify the functionality of each part.
Redirection
If a page uses a redirect as a template, the redirect is resolved before processing the template and the target is used instead. This won't work if the target doesn't exist (a broken redirect), or is itself a redirect (a double redirect).
A page that just includes another page as a template might look like a redirect, but there are several differences between them:
- The header of the result displays the title of the page it came from.
- No "Redirected from" message is shown.
- Buttons like edit, watch, talk, history, "what links here," and "last modified" point to the referring page. To access the target page, use a section edit link and navigate from there.
- Unless includeonly and/or noinclude tags are used, the referring page shares the same categories as the target page.
- "Double redirects" work when one or both are this type of pseudo-redirect.
Parser functions
MediaWiki also supports parser functions, which function similarly to templates but follow slightly different syntax:
- Parser functions utilize a ":" instead of the initial "|".
- An edit page does not display parser functions used on that page.
- There is no "What links here" feature for parser functions to identify the pages where they are utilized.
- Parser functions templates do not generally accept named parameters, so equal signs generally have no special significance. For example:
{{ #if: not blank | x=abc }}
givesx=abc
See also
General template usage
- Manual:Expr parser function syntax
- Help:Substitution
- w:Help:Template
- Manual:Advanced templates – describes even more advanced techniques such as dynamic template calls and variable parameter names
- Help:Multiple-instance templates - on the use of multiple instances of the same template on a page.
- Manual:Newlines and spaces#Automatic newline
Special constructs used in templates
- Help:Magic words – fancy stuff you may find in some templates
- Help:Extension:ParserFunctions – additional fancy control functions such as #if and #switch
- Help:Parser functions in templates – guidance on using parser functions in templates
- ߞߙߊߞߏ ߘߕߊ߫:ߘߍ߬ߡߍ߲߬ߠߌ߲
- Help:Extension:ParserFunctions
- Extension:Scribunto
Other relevant information
- Help:ExpandTemplates
- Help:External searches – a template special use case example
- Manual:Importing Wikipedia infoboxes tutorial
- Extension:PageTemplates
- Manual:Creating pages with preloaded text – Using templates as the starting text of a page
- Help:Transclusion – embedding pages from namespaces other than
Template:
- Manual:Template limits
- Help:What links here
- Special:Mostlinkedtemplates - shows the templates with the most uses
- Special:Unusedtemplates - shows templates with no uses (although they may be substituted)
- Manual:$wgEnableScaryTranscluding - using templates from other wikis
- w:WP:Anatomy of a template
- w:Wikipedia:Transclusion costs and benefits
- Manual:Parser.php
- Help:Extension:TemplateSandbox - for previewing your changes to a template as it renders elsewhere
ߞߐߞߊ߲߫ ߛߘߌ߬ߜߋ߲ ߠߎ߬
- Miraheze template repository - MediaWiki templates intended for general use.