Help:Templates

Templates are standard wiki transcluded (embedded) inside other pages.]] Templates follow a convention that the name is prefixed with, assigning it to that namespace.

Creation
Create a template just like any other wiki page.

As an example of how templates work, take a page called "Template:Welcome" with contents:

Hello! Welcome to the wiki.

Just creating this page has made a template, which can be included in any other page as follows:

When that page is viewed, the text "Hello! Welcome to the wiki." will appear instead of. The template content is "transcluded" into the other page, i.e. it is integrated in the page.

Insert  at any point of any page where someone is to be welcomed. Change the text in the template and the new text will appear in place of the original one on every page the template is used.

There are several additional features of transclusion that enrich this mechanism and make templates very useful.

Usage
Templates can be used in other pages in these ways:


 * , described above, 'transcludes' (i.e. includes a copy of) the content of the template (stored in the page Template:Name ) whenever the page containing the template transclusion is fetched and displayed; i.e. if the template is later changed, the displayed transcluding page will automatically change too.


 * replaces that string with the contents of the template, in the source of the transcluding page, when that page is saved; the copy of the template contents can then be edited normally (and separately from the original in the template page). Note: don't use this if looking to continually propagate changes from the source template to the page(s) that references it.


 * allows for substitution that doesn't break transclusion, see Help:Substitution on en.wikipedia.org.


 * includes the template in a form that displays it as raw wiki syntax (the way  does) when the page containing it is fetched.

In fact, an ordinary wiki page can also be used as a template, simply by specifying the namespace it resides in, so:
 * includes
 * includes
 * includes
 * replaces itself with the contents of

If no such namespace exists, the full title is assumed to be a template:
 * includes

Parameters
To enrich the mechanism of transclusion, MediaWiki allows parameters to be passed to a template when it is transcluded. Parameters allow the template to produce different contents or have different behaviors.

To insert a little thank you note in the talk page of other users, such as:

The thank you note will have a reason (in this case, "all your effort") and a signature ("Me"). The objective is that any user is able to thank any other user, for any reason whatsoever.

So that the note will look similar everywhere it is used, define a template called Template:Thankyou, for example. Although the note should look similar whenever a user thanks another user, its specific contents (i.e. the reason and the signature) will be different. For that reason, pass them as parameters. If we ignore the remaining elements to format the box and place the image, the core content of the template will be this:

A little thank you... for. hugs,

Notice the use of  and. 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.

When using the template on a page, fill in the parameter values, separated by a pipe char. MediaWiki allows parameters to be passed to the template in three ways.

Anonymous parameters
To pass in anonymous parameters (also known as unnamed parameters), list the values of those parameters sequentially: In this case, template  receives parameters   and   and produces:

Inverting the order of the parameters:

causes template  to receive parameters   and   and inverts the result:

So, the order in which anonymous parameters are passed in is crucial to its behavior.

Numbered parameters
To pass in parameters by number, identify each parameter when passing it:

This time, template  receives parameters   and , though they have been supplied in inverse order, and produces:

Named parameters
The third way of passing parameters is by name, instead of numbers. In this case, the template contents would be changed to:

A little thank you... for. hugs,

Within the template, we use  and   to identify each parameter, instead of a number. To pass these parameters by name, identify each parameter when passing it:

In this case, template  receives parameters   and   and produces:

The advantage of using named parameters in a template, besides also being flexible in the order parameters can be passed, is that it makes the template code much easier to understand if there are many parameters.

Default values
Transclude a template that expects parameters, without providing them, in this way:

in the numbered parameters example above you would get the following:

Since no parameters were passed in, the template presents the parameters themselves, instead of their respective values. In these cases, it may be useful to define default values for the parameters, i.e. values that will be used if no value is passed in. For example, if the template contents are changed to:

A little thank you... for. hugs,

then  defines that if no parameter   is provided, then the value   will be used. Similarly,, defaults parameter   to value. Now, transcluding the template again without passing any parameter, results in the following:

Very often inside templates there are references to parameters in this form:

Here the default value is an empty string, which will be used if no value is passed when calling the template.

Parameter values containing special characters
Because the characters  and   have special meanings when calling templates, particular care must be taken when passing a parameter value containg one or both of these symbols. The templates and  (or the HTML entities   and  ) can be used for this purpose.

To see how this works, consider the following mistakes a template user might make when trying to use special characters in template calls, and how they could be corrected. Each case begins with an indication of how the user wants the parameters to be parsed, followed by the user's unsuccessful template call (in which the parameters are actually parsed differently, as indicated in parentheses), and finally various successful template calls that would be parsed in the desired way. (The template being called is a hypothetical one named "".)


 * One anonymous parameter containing an equals sign
 * (parsed as a parameter named foo being assigned the value bar)


 * One anonymous parameter containing a pipe symbol
 * (parsed as two anonymous parameters with values foo and bar)


 * One named parameter with value containing a pipe symbol
 * (parsed as a parameter named foo being assigned the value bar, followed by an anonymous parameter with value buzz)


 * One named parameter with value containing equals sign
 * (parsed as intended, as a parameter named foo being assigned the value bar=buzz)

Note that there is no such thing as a parameter name containing  or , only parameter values. (Well, OK, technically parameter names can contain, but this probably isn't worth worrying about.)

Controlling template inclusion
By default, the whole content of a template will be processed and displayed both when the template page is being viewed directly and when the template is being included in another page. However, it is possible to control template inclusion by the use of  and tags.

Anything between  and   will be processed and displayed only when the template's page is being viewed directly, and will not be processed and displayed when it is included in another page. The application of this is to do things to the template page that should not be similarly done to the pages where it is included:


 * Categorizing the template.
 * Placing in the template interlanguage links to similar templates in other languages.
 * Presenting explanatory text about how to use the template.

Anything between  and   will be processed and displayed only when the page is being included, and will not be processed and displayed when the template page is being viewed directly. The application of this is to do things in the pages where the template is included that should not be similarly done in the template page:
 * Categorizing only the pages where the template is included. Note that when changing the categories applied by a template in this fashion, the categorization of all the pages where that template is included may not be updated until some time later: this is handled by the job queue. To force the re-categorization of a particular page, open the page for edit and save it without changes.
 * Ensuring that the template's code is not executed when viewing the template page itself. Normally this is because it isn't receiving any parameters and its execution without parameters has an undesired aspect.

Of course, everything outside  and tags is processed and displayed both when the template page is being viewed directly and when the template is being included in another page.

Adding documentation and categories
For templates to be effective, users need to find them, and find out how to use them.

To find templates users may:
 * 1) Click Special Pages > All Pages.
 * 2) In the Namespace list, choose Template and click Go.

But it is better if users can navigate a category structure to find appropriate templates for their task.

To provide users with this ability, and to give them helpful usage information, place the Documentation template at the bottom of any template created:

After saving, there will be a prominent "Documentation" section heading with a "[create]" link to the right of it. Following that link will create a documentation subpage preloaded with some default documentation. Modify the documentation as appropriate, describing the template and its usage — and don't forget to add one or more appropriate template categories near the bottom (inside of the element), so users can find the template.

The Documentation template also provides links to create a template sandbox and a list of test cases. (These "create" links will be visible on the page for the template itself, not on the "/doc" subpage.)

Copying from one wiki to another
Templates often require CSS or other templates, so users frequently have trouble copying templates from one wiki to another. The steps below should work for most templates. (Make sure the wiki bing copied from has a license compatible with ours.)

MediaWiki code
If in possession of import rights on the new wiki:
 * 1) Go to Special:Export on the original wiki, and download an .xml file with the complete history of all necessary templates, as follows:
 * 2) * Enter the name of the template in the big text box.
 * 3) * Check the box "Include templates".
 * 4) * Uncheck the box "Include only the current revision".
 * 5) * Click Export.
 * 6) Go to Special:Import on the new wiki and upload the .xml file.

If not in possession of import rights on the new wiki:
 * 1) Go to Special:Export on the original wiki, and download an .xml file with the latest version only of all necessary templates, as follows:
 * 2) * Enter the name of the template in the big text box.
 * 3) * Check the box "Include templates".
 * 4) * Check the box "Include only the current revision".
 * 5) * Click Export.
 * 6) Open the file in a text editor and manually copy the text inside the   tag of each listed template into a similarly named template in the destination wiki. In the edit summary of each template, link to the original page for attribution.

This will copy the entire code necessary, and will suffice for some templates.

Extensions
Check if the template depends on any extension. Only sysops can install an 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, admin privileges will generally be required, because system messages will need to be edited in the "MediaWiki:" namespace.


 * 1) Look for the use of CSS classes (text like  ) in the template text. If those classes appear in "MediaWiki:Common.css" or "MediaWiki:Monobook.css" on the original wiki, copy them to "MediaWiki:Common.css" on the new wiki and check if the template is now fine.
 * 2) 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,  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 first browsing the code to identify and select the parts that seem relevant. Find comments that can serve as clues to identify the functionality of each part. When in doubt, copy all the code to the new wiki.