Help:Template

In MediaWiki, a template is a page which can be inserted into another page via a process called transclusion. It can be considered a wiki subroutine facility and is comparable to a #include statement or macro that is expanded at page view time. Substitution allows templates to be used as a macro facility.

This page and its extension Help:Advanced templates provide a reference manual on templates in MediaWiki. For an introduction, see A quick guide to templates and mw:Help:Templates. For syntax often used within templates, see ParserFunctions and other "Advanced functioning" help pages listed below.

Note: The master version of this page is the page m:Help:Template on Meta-Wikipedia; template demos work there, but may not work if you are viewing a copy of this page on another project.

General
The template namespace is the namespace with prefix "Template:" (this prefix can be used in all languages, but the canonical prefixes in languages other than English include Vorlage, Modèle, Sjabloon, with colon; the site WikiFAQ calls it Snippet).

A page in this namespace is called a template. The contents of such a page (either fixed or depending on parameters and/or variables) is designed to be useful for insertion in other pages (transclusion, creating a compound document).

The syntax for insertion of the page "Template:name" is. This is called a template tag.

Example: abcdef

Gives: abcdef.

This reference in the wikitext causes insertion of the template content when the referring page is rendered. Various equivalent terms are:
 * calling the template
 * including the template
 * transcluding the template
 * using the template
 * embedding the template

Depending on context "including" can be used as opposed to substituting the template.

To create a hyperlink to a template page, use the usual wikilink syntax Template:name.

If the page "Template:name" does not exist, then works as  Template:name , a link to a non-existing page, leading to the edit page. Thus, one way of making a template is putting the tag first, and then following the link.

If name starts with a valid namespace prefix, or a colon, then it is not prefixed with "Template:". This way any page can be used as template (a colon at the start refers to the main namespace).

Also it provides an alternative way of calling a template, which can be used in the case of a name conflict with a variable, e.g. Template:Ns:3 and Template:PAGENAME.

Using a page outside the template namespace as template can be useful for:
 * quoting interface messages in the MediaWiki namespace
 * templates for personal use in subpages of one's userpage, e.g. for experimenting
 * inclusion of pages in other pages in the same namespace, e.g. having an extra page associated with each page, such as a to-do list, with a simple name correspondence; it can be created and included with.

As usual the template name is case sensitive except (on most projects) for the first letter, and a blank space is equivalent with an underscore (as opposed to parameter names, see below: they are case-sensitive, even with respect to the first letter, and spaces are distinguished from underscores).

One can call a template that calls another template. If a template calls itself directly or indirectly, inclusion works only on one level for each template. However, with templates redirecting to the template that one would want to call recursively, one can achieve recursion without having to make copies of the whole template content, with the number of levels limited by the number of redirects. See also Repetition within a page and.

A variable in a template is evaluated after insertion in the referring page, i.e. if occurs in the wikitext of a template, it is rendered as the name of the referring page, not the name of the template.

A list of pages embedded in a page (as recorded in the templatelinks table), all with links, is given on the edit page. Notes:
 * on a section edit page first the whole list is given, i.e. also the templates used in other sections; after pressing preview only those in the section, updated for the edits made, if any; preview on first edit gives the full list;
 * similarly, when editing an old version of a page, the list is first given for the current version, while after pressing preview the templates that used to be included are shown, updated for the edits on the old version made in the current session, if any;
 * if a page is conditionally embedded through #if, #ifeq, #ifexist, #ifexpr, or #switch, it is counted as embedded, even if the condition is not fulfilled
 * if the name of an embedded page is an expression, e.g., currently giving , the current template name is shown.

Thus, to use "What links here" to find the pages that actually embed template A, instead of using e.g.



one has to use an alternative, e.g., duplicating the condition:



or, using :



Only with the first of the two alternatives "What links here" also finds the pages that actually embed template B. In the second alternative the page is anyway considered embedded. If we replace "b" by " " the page is never considered embedded.

(Supported in version 1.4 and higher.)

When saving a page without newline at the end, and going to the edit page again, there is a newline at the end. However, this does not seem to have effect, see the example above and the following example:

using Template:Numbered list demo, gives

In a template name the character "#" and any characters after that are ignored: gives. This is used in hif.

A wikitext with consecutive double opening braces and consecutive double closing braces is interpreted as containing a template parameter tag with triple braces. To avoid that, use a space in at least one of the two quadruples. For example, gives, while  gives.

With Special:ExpandTemplates one can view the expanded wikitext a template call produces, as intermediate step toward rendering. The same is also produced with a URL like.

Use of templates across projects
A template only works when referred to from a page in the same project. To use it in another project, one has to copy it to there. 1126 is a request to lift that restriction, i.e. allow interwiki use of templates.

The adjustments needed in the copy, to work on the other project, can be reduced by using, localurl, and generic namespace names, and writing links in a way that works on multiple projects, e.g. m:Help:Table. For copying multiple templates, export and import can be helpful. It is also convenient if the template names can be the same on the other project. Therefore, when choosing template names, check which names are in use on other projects to which people might want to copy the templates. Note that if a template is referred to by something like abc, a project with different namespace names requires a different template name, or a redirect.

Transclusion across projects, hence changing contents from a central place, is only possible:
 * for content in the form of an image on Commons, to any page,
 * for editable content on an image page on Commons, including content transcluded from other pages on Commons, to the corresponding local image pages, if there is no local image with the same name

Templates on the central Wikia work in the separate Wikia projects, provided that the prefix "wikia:" is used, see shared templates on wikia. (Please note that these external Wikia projects are NOT hosted and managed by the Wikimedia Foundation.)

Sometimes multiple projects require pages which are partly the same and partly different. For example, on some projects "m:" is used as interwiki link to Meta, and on some projects "MetaWikipedia:". In this case a common wikitext can be used, calling project-specific templates. In the example the wikitext of the page could contain, and we would have on each wiki a Template:Meta containing the required prefix.

Parameters
Template parameters are either named or numbered. They are called-by-value, and therefore input parameters only.

In the template definition, the formal parameter (the placeholder for the parameter value) is a parameter name with three pairs of braces. So, for example, you would write for a template parameter which you wanted to call myVariableName.

In the template call, the syntax is either
 *   with tags   ,   , etc. in the template, or
 *   with tags   ,   , etc. in the template.

The default (optional, together with the pipe character in front) can be different for every occurrence, and applies if no value is specified when calling the template, not to be confused with the case that the empty value is specified.

A way to determine whether a parameter is defined is by comparing the results of two occurrences with different defaults, e.g. with  .

In the case of page substitution with an undefined parameter, not the default but the parameter itself with default is substituted into the wikitext.

Example: named parameter substitution
Let's create a template called Name-example (that is, the template will be Template:Name-example), with a parameter for the first name which we will call firstName, and a parameter for the last name which we will call lastName.

Type the following in the new Template:Name-example:


 * I am a template example, my first name is ' and my last name is '.
 * You can reference my page at,.
 * You can reference my page at,.

On a second page, type this:

The result is:

Because the template has no parameters.

But if we type this on the second page:

The result will looks like this:

To analyse the working, one can apply Special:ExpandTemplates to see the expanded wikitext as intermediate result:


 * I am a template example, my first name is John and my last name is Smith.
 * You can reference my page at Smith, John.
 * You can reference my page at Smith, John.

When this wikitext is applied directly the resulting rendering is the same.

Example: numeric parameter substitution
An example of how the contents of a parameter function.

The simplest case
Let us first define a template with the name t0, which will
 * expect a single argument
 * give back the text of that argument, with no spaces before or after it, between "start-" and "-end":
 *  start--end 

the definition of course being on page Template:t0.

If something like ' or in fact any ' is visible on an ordinary page it typically indicates that a mandatory parameter of a template used on this page isn't defined.
 * 1) Calling the template named t0 with a parameter value of "a", i.e.,
 * gives
 * 1) Calling the template named t0 with a parameter value of " " (a blank space), i.e.,
 * gives
 * 1) Calling the template named t0 with a parameter value of "" (an empty string), i.e.,
 * gives
 * 1) Calling the template named t0 and not passing any parameters, i.e.,
 * gives
 * 1) Calling the template named t0 with a parameter value of "" (an empty string), i.e.,
 * gives
 * 1) Calling the template named t0 and not passing any parameters, i.e.,
 * gives
 * 1) Calling the template named t0 and not passing any parameters, i.e.,
 * gives
 * gives

Calling the template named t0 with a parameter which consists of two newlines, i.e.,

gives

gives

.

Thus, unlike in the case of parser functions, there are no complications with spaces and newlines, compare conditional whitespace.

Declaring a default value
Now let us define a similar template with the name t which contains a single numbered parameter 1 with a default of pqr. The only difference between the effects of t and t0 appears when they are called with no parameter (and no "|"):


 *  start--end 

the definition of course being on page Template:t.
 * 1) Calling the template named t with a parameter value of "a", i.e.,
 * a
 * gives
 * "a".
 * 1) Calling the template named t with a parameter value of " ", i.e.,
 * undefined
 * gives
 * "undefined".
 * 1) Calling the template named t with a parameter value of "", i.e.,
 * undefined
 * gives
 * "undefined".
 * 1) Calling the template named t with named parameter 1=, i.e.,
 * no surprise
 * gives
 * "no surprise".
 * 1) Calling the template named t with 1= after an unnamed parameter, i.e.,
 * no
 * gives
 * "no".
 * 1) Calling the template named t with 1= before an unnamed parameter, i.e.,
 * surprise
 * gives
 * "surprise".
 * 1) Calling the template named t and no parameter at all, i.e.,
 * undefined
 * gives
 * "undefined".
 * 1) Calling the template named t and no named or unnamed parameter 1, i.e.,
 * undefined
 * gives
 * "undefined".

Restrictions on parameter values

 * If a parameter value contains an equals sign, the parameter name must be put explicitly, even when it is 1, 2, 3, etc.


 * If the expression for a parameter value contains two consecutive closing braces which are not part of a variable or parameter tag, they have to be put in nowiki tags.


 * The expression for a parameter value cannot contain the variable localurl with query string, due to the pipe character.


 * A parameter value can be quite long, see Help:Long parameter demo.


 * A parameter value can contain pairs of square brackets or text to be used within a link, but not a closing part of one link and an opening part of another link: using  gives  rather than the expected aabc]]def[[ghib.

Pipe character
To define a parameter value containing a pipe character (|) which is not part of a template call, parser function call, piped link or image tag, use Template:! containing " | ". Using, compare giving ,  giving  and  giving. The difference between the first and the second is that in the first case the expanded wikitext is start-a|b-end, while in the second case it is start-a&amp;#124;b-end. This is rendered the same in final output but makes a difference when used in table syntax: this requires the "real" pipe character. For examples see m:Help:Template.

Equals sign in parameter value
When a parameter value contains an equals sign, the parameter name must be stated explicitly, otherwise the part of the parameter value before the equals sign is taken as the parameter name. If that happens accidentally, this parameter is likely to be unused, hence harmless, but the intended implicit parameter 1, 2, or 3, etc., gets no value.


 * Example:   gives  (unused parameter a is assigned the value b, the first parameter value for which no parameter name is specified is assigned to  the parameter with the implicit name "1" &mdash;   it reads like so: Use template TTT, assign "b" to the parameter "a", use the value "c" for your first implicit parameter  .), while  gives  (the first parameter is assigned the value "a=b" &mdash; it reads like so: Use template TTT, assign "a=b" to the expressed parameter "1", assign "c" to the expressed parameter "2").  gives, "d" is assigned to "1" as first implicit parameter, overwriting the value "a=b".

A parameter definition (between pipe characters or a pipe character and template end tags) may depend on a template, parser function, variable, or template parameter. The explicit or implicit name of the parameter is determined after expansion. For example, a template call  assigns the value of  to implicit parameter 1 if that value does not contain an equals sign, but if it has the value "b=c", c is assigned to b. If we anyway want to assign the value of  to 1 we have to use an explicit parameter 1:.

Compare:


 * (using ) gives.
 * (using ) gives.

Similarly, parameter definition =b where has value "c=d" results in "d=b" being assigned to c, for example:
 * (using ) gives.

Mix of named and unnamed parameters
In the case of a mix of named and unnamed parameters in a template tag, the unnamed parameters are numbered 1,2,3,.., so they are not numbered according to the position in the mixed list as a whole.

For example, using  gives.

When parameters do not expand
Parameters do not get expanded when they are inside tags (HTML, wiki, or extension), or between tags

The following will not work within a template, because the parameter is not expanded

 ... 

This continues to be true into version 1.8.2, though Template:Hidden provides a puzzling exception. Any explanation?

Template mechanism
The template mechanism involves the following steps:


 * The pipe characters in template calls determine the separation into template name and parameter definitions. This separation does not depend on possible pipe characters in the expanded form of the text between the opening and closing braces of the template. For example, using  gives, not the result of  which is . This is because "t2demo|a" is not a valid template name (not to be confused with a template with a valid name that does not exist), so the template call is not expanded.


 * Note that in this case partial or successive substitution does not give the same result as without substitution: gives the wikitext , rendered as.


 * The template name and each of the parameter definitions is evaluated. The leftmost equals sign, if any, in each parameter definition separates the parameter name from the parameter value.
 * The values are assigned to the parameters from left to right (the result can not be directly viewed), meaning that a named or numbered parameter may be specified several times, the last one being the actual value that will be kept when passing the parameter during the final instantiation of the template below.
 * Template calls are replaced by template content, where the parameter tags with matching names are replaced by their values or defaults (the result of this step can be viewed by applying subst either again, or directly to the template and the variables).

The process is applied recursively until there are no more template calls to replace.

All whitespaces before and after a parameter value are ignored if "=" is used.


 * "a" gives "a".
 * "a" gives "a".
 * "a" gives "a".
 * "a" gives "a".

A parameter value can contain a piped link; the "|" in such a link is not taken as parameter separator.


 * Example: "a|b" gives "a|b".
 * Example: "a|b" gives "a|b".

(In this case the space has effect.)

On rendering, surplus parameter values (including named parameters that do not occur in the template) are ignored: b gives b.

Parameters without names (i.e. that don't contain an equal sign) are numbered implicitly starting by 1, from left to right.


 * Example: "b" is equivalent to "a"

Numbered parameters can also be skipped or can be specified in alternate order by numbering them explicitly.


 * Example: "a" is equivalent to "a"
 * Example: "b" is equivalent to "a"

This also makes it possible to apply a default value for parameter 1, while specifying a value for parameter 2:

, using, gives.

Template calls can contain multiple occurrences of the same named parameter, and a numbered parameter can be specified multiple times by using its number explicitly. The effective value of parameters is the value of the last occurrence (from left to right) of the parameter with the same name, once the parameter names have been evaluated.


 * Example: "b" is equivalent to "B"

The final list of formal parameters before the template itself is instantiated is then unordered because the list is indexed by the evaluated parameter named (this list is an associative array).

When ParserFunctions were not available yet, multiple assignments of parameters with the same name (and thus allowing parameter overrides) were ingeniously used to perform branching, e.g. in the now deleted en:Template:If defined.

See also Help:Parameter default.

Template tag lay-out
To have a desired template tag lay-out, especially in the case of many parameters, additional dummy parameters can be used with a newline, spaces, and/or comments. In the case of unnamed parameters, this means that some parameter numbers are not used in the template content, so that their values, present in the template tag, do not affect the rendering of the template. For example, using ,

gives:

If parameters are named, dummy parameters can easily be inserted at any time. If they are unnamed, then, to avoid renumbering, one can insert named parameters: any text including an equals sign will do, if the text on the left is not one of the parameter numbers: this text is interpreted as the name of an unused parameter, hence ignored.

Example:

Using

which gives

In this example, the 1 to 8 row numbers and a to h column numbers (as well as their surrounding spaces and newlines) in the parameter list are hidden within a dummy parameter (with an empty name before the equal sign).

The template generates a HTML table where each cell contains an image whose name is dynamically generated from the 64 first automatically numbered parameters (there are intermediate parameters within the numbered list, but as these dummy parameters are named explicitly, they don't increment the parameter number used to generate default parameter names. So the parameter with autogenerated name "1" effectively contains the "rd" value).

The template is then called with a parameter list that contains:
 * 65 parameters automatically named from "1" to "65" (64 parameters for the cells content, and the 65th for the image width),
 * and a dummy named parameter (whose name is an empty string, and whose effective value results from the last assignment with the chessboard column names a to h and the surrounding spaces and newlines), which is not used in the internal template content.

Note also that all parameters are trimmed, so the parameter with autogenerated name "9" (at position a7 on the chessboard above) is assigned the empty string value.

Template page
Without noinclude and includeonly parts the following are identical:
 * the rendering of the wikitext of the template (this is on the template page, and would be the same in other pages with that wikitext, except for page-dependent variables)
 * the rendering of the template on a page that calls it without parameters

Thus the defaults are shown, e.g. shows the same as : "".

Template page if no defaults have been specified
In simple cases this corresponds to treating the parameter tags as ordinary text, for example:

"" (using Template:t2demo containing ) gives

Similarly, if part of the parameters is undefined, only those show up as.

However, some templates produce an error message when called without parameters, so unless includeonly is used (see below) the template page also shows this message, suggesting that there is something wrong with the template. For example, a template that doubles parameter with the wikitext  gives. In such cases includeonly can be used to avoid uninformative and messy rendering on the template page, but either way a disadvantage during template development is that preview does not (meaningfully) reflect changes in the parts of the page outside the noinclude tags (i.e. the included parts). Therefore it can be useful to provide representative default values, even if that is only done temporarily during development of the template.

Note also that variable tags are not shown, but evaluated.

With noinclude an informative template page can be produced, containing more demos and test cases than just the single default set. Typically, the noinclude-part of a template page contains examples including or substituting the template. Changes in the working of the template (i.e. changes outside the noinclude-part) are not yet effective in these examples in preview and, in the case of substitution, in "show changes". However, they are reflected in the rendered page after saving.

Some formatting aspects may show up which are not readily seen from the edit box.

A parameter value depending on parameters
As mentioned above, if a parameter is left undefined, the triple braced parameter name in the result does not function as a parameter if the page is called as a template from another page; if it should, do not omit the parameter value but specify it in terms of a parameter of the calling page; compare:
 * (using Template:t2ademo containing ) gives
 * (using Template:t2a1 containing ) gives.
 * Similarly, (using Template:t2a2 containing ) gives . See also below.

The most straightforward way of expressing a parameter value in terms of a parameter is using the same name and making it equal, e.g. in Template:Lan is mr.

Empty vs. undefined
makes the first parameter equal to the empty string rather than leaving it undefined: it gives. By treating the second unnamed parameter as a parameter with the name "2", the first unnamed parameter can be left undefined.


 * Example:  gives.

If the parameter is used in a tag like the default text may give invalid code that is conveniently ignored, rather than resulting in perhaps ugly code being rendered (but this may depend on the browser). See e.g. Template talk:Fontsize.

Parameter names (as opposed to template names) are case-sensitive, even with respect to the first letter, and spaces are distinguished from underscores. The empty string is also a valid parameter name, see Template:T empty string as parameter name.

Parameter 02 is distinguished from parameter 2: using, gives

Note that parameters in the MediaWiki namespace (interface messages) are written differently: as $1, $2, etc., see Meta-Wikimedia:MediaWiki namespace text.

msgnw
The prefix msgnw (short for "message, nowiki") is used to display the uninterpreted wikitext of a template (the same thing you'd see if you were editing the page) on another page. An exception is that numbered and unnumbered lists are rendered as such instead of displaying # or * signs. Parameter values are ignored.

With the introduction of noinclude and includeonly tags, allowing template pages to take care of definition as well as displaying information, msgnw displays no longer just the technical information about what the template does when included, but a mix of that with wikitext for rendering the template page itself, with the tags. This limits the usefulness of applying this.

Examples:

Template:en
 * gives
 * gives

gives

...which is much more than just the formal info about what the template does when included:
 * start--end

Template:Numbered list demo

gives:

gives:

The edit box for Template:Numbered list demo shows:
 * 1) Amsterdam
 * 2) Rotterdam
 * 3) The Hague

Usage
Templates are useful for any text for which one wants a copy in two or more pages, and there is no need for each copy to be edited independently to adapt it to the page it is in. Since parameters can be used, versions may to that extent even be different, and parameter values can be edited independently for each. Templates are not only convenient, but they can also "force" a useful uniformity. See also advantages of subprograms.

Typical applications are:
 * template messages such as w:en:Template:stub
 * Navigational templates such as w:en:Template:europe, sometimes listed in a directory such as w:Wikipedia:navigational templates
 * infoboxes, each time showing the same kind of information in the same format, but each time for a different case, using parameters, e.g. the w:en:Template:Infobox Countries.
 * provide cross-language portability of texts which are largely internationally the same, but contain some standard terms different in each language; the standard terms are replaced by referring to template pages which have the same name but localised content in each language. This is applied in Wiktionaries for names of languages, terms like "noun", etc.; it is also applied for taxoboxes, see e.g. w:en:Template:Familia and w:fr:Modèle:Familia.
 * allow a composite image, composed of a table of images, to be specified by a template tag which itself has a corresponding table-like lay-out, see w:Template:Chess position and w:Template:Game of Go Position (the latter example also shows that the number of parameters a template can have is quite large, in this case 362). Newlines in parameter values provide the lay-out of the template tag, but they are not allowed in image names, therefore they are put within comment tags; alternatively, dummy parameters could be used on these positions.

Various combinations are possible. E.g., the last two could be combined, so that e.g. every language version of Wikipedia has the same Infobox Countries template (for each project a copy, because the template mechanism can not import across projects), which has parameters for the data, and refers to templates with translations of standard terms.

See also Help:Advanced templates.

Composite pages
The wikitext of a page may (partly or fully) consist of tags for the inclusion of component pages. The "templates" are not necessarily in the template namespace, and may be more or less self-contained pages by themselves. An advantage of putting the components in the template namespace is that they are then included in the list of templates used on the composite page, all with links, on its edit page. On the other hand, the component page may, by itself, be of a nature that it belongs in e.g. the main namespace, while the prefix would suggest otherwise; also the prefix would clutter the pagename.

Examples are:
 * m:Help:A simple composite example
 * w:Wikipedia:Village pump with six component pages, e.g. w:Wikipedia:Village pump (technical)
 * daily a page like w:en:Wikipedia:Votes for deletion/Log/2005 May 31 where each component page consists of the discussion on the deletion of one Wikipedia page, e.g. w:en:Wikipedia:Votes for deletion/Sp3tt (for this day there are 75 of such component pages)
 * m:Meta:Translation/Coordination, mainly containing
 * m:Meta:Translation/Coordination/List/Meta
 * m:Meta:Translation/Coordination/List/Main
 * - rejection of composite page by w:en

This allows the user the choice between viewing the component pages separately or combinedly. One may want to view a page separately if one has a slow connection; also sometimes people have sentimental reasons for having a separate page about a topic, e.g. a village. Viewing the combined page is much more convenient if there are many small component pages; even if a subbtopic page does not provide additional info, if it exists anyway, and is linked to, it is useful to display the content (making clear that the whole content is shown), it saves the trouble of checking the contents by following the link.

In the latter case the search function of the browser can be used for searching in the combined page. Similar to the section editing feature, it allows editing a component page; however, there is no possibility to have the combined wikitext in the edit box.

Edit history, recent changes, watching pages, and "what links here" work separately for the component pages and the composition page, not for the composite page. Related changes works for the component pages and for the composite page. Page protection can be set for selected component pages and for the composition page, not directly for the composite page.

The talk page of a composition page is used to talk about the composition and the page in general, and could in addition be a composite page of the talk pages of the component pages.

A composite page has an integrated TOC and section numbering; the numbering is not reset for each component page.

Editing a section of a component page can be done directly from the composite page, see editing sections of included templates. After saving, one ends up at the page for the component page to which the section belongs.

On projects with the interlanguage link feature the composite page shows the combined interlanguage links of all component pages, hence possibly multiple links for one language or even for one page.

For easy access to the component pages, links to them on the composite page (for example by self-links on the component pages) are convenient. Alternatively, access is through section editing, or, if the component pages are in the template namespace, through the list of templates called from the composite page, at its edit page.

Conversely, for easy access from a component page to the composite page(s) that call(s) it (if there are not too many of them) it is convenient to link the component page to them (on a composite page one becomes a self-link).

See also w:Wikipedia talk:Template namespace.

Pages with a common section
A section on the relationship of the subjects A and B, or a subtopic equally relevant for A as for B, can be put both in page A and in page B, by making it a separate page C, called as a template from A and B. Remarks:
 * For readers reading both A and B, it is useful that the duplication be indicated by a message or a special lay-out; otherwise it is confusing and inconvenient. One can for example use :
 * After saving one ends up viewing the template page. For easy access to the calling pages it is convenient to link the called page to them (on a calling page one becomes a self-link). This may well be integrated in the message about the duplication. It is even more convenient than the two-step link as shown above.
 * The section level of the embedded section(s) has to be the same in each embedding page. The same applies to lay-out and style.
 * Pages like C can be put in
 * the same namespace as A and B; advantage:
 * the kind of content of C is the same as that of A and B
 * the template namespace; advantages:
 * C appears in the list of templates called from A and B, at their edit pages
 * C by itself may not satisfy the standards for pages in the namespace of A and B, such as providing context (however, the message about the duplication explains it)

Examples:

For various remarks which also apply here, see also the previous section.

Repetition within a page
For a succession of similar pieces of content, as in a list, a computer program would use a loop. What comes closest in MediaWiki is putting the loop body in a template, and calling the template repeatedly, usually with a varying parameter value. This is somewhat primitive for a loop:
 * instead of "for i=1 to 5" we need to enumerate the values 1, 2, 3, 4, 5; on the other hand, this gives the versatility to use just as easily less regular values such as de, en, fr (collection-controlled loop).
 * repetition of code is minimized by the template, but the template call itself has to be repeated each time (but see also the next section)

Example:
 * Template:List of Languages - the "loop body" is in Template:Lang def; compared with putting the content of the latter directly in the list the advantage is that the variable part (the value of "code") occurs once each time in the code, although it is used twice. This is important because the fixed part of the list item code can be copied while the variable part is typically inserted manually.

For repetition of the same text the loop body can be a parameter, e.g. Template:X5 (see list).

A double loop is achieved by a second template that repeatedly calls the first. Similarly for a triple loop, etc. See e.g. w:Template:Ld, w:Template:L2d, and w:Template:L3d.

An example where the same template is used for different loop levels is Template:Loop 2. Because the software has a built-in protection against infinite nesting (if there is, there will be an error e.g. ), a redirect is used for each level. The number of levels that the template can handle is determined by the number of parameters specified in the two template calls it comprises (because going up a level requires an extra parameter) and the number of existing redirects.

Similarly Template:Lanlp 1 is used for both the inner and the outer of a double loop. Adding an item (here a language) adds to each row and also adds an extra row.

Providing effective repetition without repetition of similar template calls in the wikitext

A technique for repetition of similar template calls without actually putting this list in the wikitext is demonstrated in, and a more primitive method described below.

Example :

gives:

Description of the old :

For an arbitrary template with up to three nameless parameters, it is equivalent to calling the template repeatedly, with the first parameter varying, and the possible other parameters fixed: one specifies the name, the values of the fixed parameters, and the list of values the first parameter should have in consecutive template calls, with a sequential number each, and ending with "end". The technique requires redirects like Template:List of template calls 3, as many as the maximum number of repetitions.

If e.g. the second parameter varies, or two parameters, then a similar template can be made, but each version requires its own set of redirects.

Example :

gives:

The empty parameters are needed in accordance with the maximum number of parameters the repeated template can have (currently three) and the maximum number of repetitions. Putting more empty parameters than needed at the end does not matter, but the number of empty parameters in the beginning of the list should be correct.

Ambiguity of a reference to "this page"
If a page is included in another page, a reference to "this page" on the included page is ambiguous. Use noinclude or includeonly tags depending on what is meant. Alternatively, mention the page name explicitly, without using.

Internal links
In the case of an internal link in a template with the target depending on a parameter, and in the case of a link with the target depending on a template, existence detection works as usual.

Examples:
 * gives
 * cd gives cd


 * (using Template:tli) gives
 * cd (using Template:tciit and Template:tciil) gives cd


 * gives:


 * Template:Pvn

Templates and external links
Examples:
 * } gives
 * } gives ""; note that brackets separated from the http:// are not recognized as belonging together:
 * [ label] gives [ label]
 * [] gives []
 * } gives
 * [http://ab cd] gives [http://ab cd]
 * http://ab gives "http://ab"
 * [http://ab] gives [http://ab]

However, a URL can not be composed of:
 * a first part in a parameter and a second part added by the template (although we have seen above that reversed it works: a second part in a parameter and a first part prefixed by the template)
 * a first part in a template and a second part after the template (although we have seen above that reversed it works: the second part in a template and the first part before the template)

Example of first restriction:
 * } gives

Examples of second restriction:
 * [add at the end] }  gives [add at the end]
 * " add at the end " gives "add at the end"

Noinclude and includeonly
This feature is not available before version 1.6.

Anything between and will be processed and displayed only when the page is being viewed directly; it will not be included or substituted. Possible applications are:


 * 1) Categorising templates, see template documentation.
 * 2) Interlanguage links to similar templates in other languages.
 * 3) Pages in the MediaWiki namespace.

The converse is. Text between and will be processed and displayed only when the page is being included. Applications include:


 * 1) Adding all pages containing a given template to a category, but not the template itself.
 * 2) Avoiding messy rendering on the template page, e.g..

Note that spaces and newlines between the general content and the tagged part belong to the general content. If they are not desired the include tag should directly follow the content on the same line: &lt;noinclude&gt;this is &lt;/noinclude&gt;fine&lt;includeonly&gt;, closing tags are &lt;/includeonly&gt;&lt;noinclude&gt; less critical, but must be specified.&lt;/noinclude&gt;

Attempts to nest split pairs of these tags, or the similar &lt;nowiki&gt;</tt> and &lt;/nowiki&gt;</tt> pair, won't work as expected. If say &lt;nowiki&gt;</tt> begins within the general content, or in a "noinclude" part, or in an "includeonly" part, then it also has to be closed within the same part.

The code  will be displayed as  when the template is not included, ~ when the template is included, and it will be expanded as the active user when the template is subst'd.

Wiki markup at the beginning of a template
If the first included character of a template is one of the Wiki markup characters :;*#</tt>, then it's interpreted as being at the begin of the line (even when the template call is not).

To avoid this effect use &lt;nowiki&gt;#&lt;/nowiki&gt;</tt> or a NCR like say &amp;#58;</tt> for a colon, this NCR is also useful in conjunction with definition lists.

Substitution

 * Main article: Help:Substitution

Putting "subst:" after the double opening braces causes an automatic conversion of wikitext when the referring page is saved: the subst tag is replaced by the wikitext of the template, with the parameter values substituted for the parameters.

Redirection
When a page called for inclusion is a redirect page, the redirect target is included instead. As usual, a double redirect does not work.

A page that consists of nothing else than the inclusion of another page as a template, shows similarities to a redirect to that other page, but also many differences, including:


 * the result has as header the name of the referring page
 * there is no redirect message
 * the buttons such as edit (for editing the whole page), watch, talk, history, "what links here", and "last modified", etc., refer to the referring page (to go to the target page, a section edit link can be used, from there the whole page can be accessed)
 * the referring page is in the same categories as the target page, except when includeonly and/or noinclude tags are used.
 * "double redirects", with one or both being this kind of "pseudo-redirect", work.

Compare Help:Template namespace with Help:Template namespace - demo of alternative for redirect.

In a page that in turn includes such a referring page there is no difference.

Note that embedding works for all pages where redirecting works, and it also fails for all pages where a redirect won't work.

Comparison of linking and embedding
Linking and embedding have in common:
 * if the page does not exist, a link to the edit page is shown; the links are identical if it is not a piped link; the link does not show parameters and does not show whether, after creation, the new page will be linked or embedded.
 * the name can depend on variables and parameters

Predefined templates
Variables and parser functions can be considered predefined templates. They do not have a page that defines in terms of wikitext what they do, because their action is something extra that cannot be constructed from more basic wikitext functionality.

Some additional differences:
 * Parser functions use ":" instead of the first "|".
 * An edit page does not list predefined templates used on the page.
 * No "What links here" is available for predefined templates, to find the pages where they are used.
 * Apart from #switch, predefined templates don't allow you to define named parameters, and therefore equal signs generally have no special effect, comparison:
 * {&#123; #if: not blank | 2=abc &#125;}</tt> gives 
 * {&#123; ifdef | not blank | 2=abc &#125;}</tt> gives 
 * It's however possible to corrupt the value shown for undefined parameters without default, for more examples see :
 * {&#123; #if: {&#123;ns:0&#125;} | 2=xy | {&#123;{2|blank}&#125;} &#125;}</tt> gives 
 * {&#123; #if: {&#123;ns:0&#125;} | 2=xy | {&#123;{2     }&#125;} &#125;}</tt> gives 
 * {&#123; #if: {&#123;ns:0&#125;} | oops | {&#123;{1|blank}&#125;} &#125;}</tt> gives 
 * {&#123; #if: {&#123;ns:0&#125;} | oops | {&#123;{1     }&#125;} &#125;}</tt> gives 

Ordinary and predefined templates have in common that their parameter values can depend on ordinary and predefined templates. In the case of named parameters, the names used in the template call can also depend on ordinary and predefined templates. This applies also for the named parameters of #switch.

Code execution
"Evaluating" a template call internally involves, to start with, evaluating the template name, the parameter names, and the parameter values. Evaluating a predefined template involves the same, as far as applicable. This is relevant even if the wikitext resulting from these subevaluations cannot have effect on the overall wikitext, as in the case of #ifexpr etc. for either the then-part or the else-part, and in the case of an unused template parameter:


 * Subevaluations involving template calls add to the pre-expand include size (see w:Wikipedia:Template limits).
 * Side effects:
 * Subevaluations producing links add on the target page to the list of incoming links (What links here), based on the pagelinks table, even if there is no link on the resulting page.
 * Subevaluations involving template calls add on the template page in "What links here" and on the edit page of the page concerned to inclusion items, based on the templatelinks table.
 * Some extensions may perform some action during a subevaluation, e.g. with VariablesExtension a subevaluation may involve assignment of a value to a variable.

Thus evaluates  and  regardless of the condition. On the other hand, just evaluates the expression for the template name (by evaluating the condition, and resulting in a or b) and the parameters, and the actually included template.

See also ParserFunctions.

Version 1.6

 * More magic words and the parameter default mechanism were added.
 * &lt;noinclude&gt;</tt> and &lt;includeonly&gt;</tt> (see above) were added.

Version 1.5

 * More magic words were added.

Version 1.4

 * Including the same template more than five times in the same page works from version 1.4, now on all Wikimedia sites. Also new was that subst can be used with parameters.

Version 1.3

 * See, among other things, [#Default_values_of_parameters default values of parameters]. Starting with version 1.3 the prefix "msg:" is generally optional.

Version 1.2.6

 * In MediaWiki version 1.2.6, make a page MediaWiki:mytemplate and refer to it with . In this version parameters are not possible.
 * Compatibility with 1.3, in the sense of having the content in Template:mytemplate, is possible with a redirect from MediaWiki:mytemplate to Template:mytemplate on the 1.2.6 project.

Revision history of pages containing templates
Pages in the stored page history consist of wikitext with possible references to templates and images. When viewing an old version of a page, these refer to the current versions of the templates and images, if these still exist. Thus the former composite page is not reconstructed.