Wikipedia:Template namespace

This page documents an English Wikipedia
consensus. When in doubt, discuss first on the talk page.

This page in a nutshell:

The Template: namespace on Wikipedia contains templates created for consistent formatting, maintenance, and navigation.
Templates should not normally be used to store article text. Such content belongs in the article pages themselves.

Wikipedia data structure
Namespaces
Subject namespaces		Talk namespaces
0	(Main/Article)	Talk	1
2	User	User talk	3
4	Wikipedia	Wikipedia talk	5
6	File	File talk	7
8	MediaWiki	MediaWiki talk	9
10	Template	Template talk	11
12	Help	Help talk	13
14	Category	Category talk	15
100	Portal	Portal talk	101
118	Draft	Draft talk	119
710	TimedText	TimedText talk	711
828	Module	Module talk	829
Deprecated
2300	Gadget	Gadget talk	2301
2302	Gadget definition	Gadget definition talk	2303
Not installed
90	Thread	Thread talk	91
92	Summary	Summary talk	93
108	Book	Book talk	109
442	Course	Course talk	443
444	Institution	Institution talk	445
446	Education Program	Education Program talk	447
2600	Topic		2601
Virtual namespaces
-1	Special
-2	Media
Current list (API call)

The Template namespace on Wikipedia is used to store

User namespace

.

Templates help maintain consistent formatting and aid navigation between articles. They often include optional and/or variable elements controlled by

Help:Using talk pages

for how to participate in talk page discussions).

A template is transcluded into another page by including a template tag in that page's content. A template tag contains the template page name surrounded by double curly braces, e.g. {{Disambiguation}}. If the template's page name does not begin with a namespace and colon, it is assumed to be in the Template namespace.

Internal links to template pages may be made by using the Template: prefix, e.g. [[Template:Disambiguation]]. These links go to a page that directly contains a base template and often documentation.

Guidelines

Shortcuts

Templates should not normally be used to store article text, as this makes it more difficult to edit the content. They should also not be used to "collapse" or "hide" content from the reader.
Templates used in articles are designed to provide information to assist readers, such as navigation aids, formatting, or warnings that content is sub-standard. Templates that provide information only of service to editors should not appear on article pages – use the article's talk page or other non-article namespaces.
Template function should be clear from the
redirects
can be created to assist everyday use of very popular templates.
High-risk templates should be semi-protected, template protected, or fully protected as appropriate (see Wikipedia:Protection policy). This applies also to any high-use template redirects.
Templates should be clearly documented as to their usage and scope.
Templates should not be used to create lists of links to other articles when a
"See also" section list
can perform the same function.
Templates for short, temporary messages that will be removed quickly (such as on User_talk: pages) or that contain text which is not likely to ever be changed should be invoked with substitution (subst:). Typical templates that are intended for long-term use and are likely to require changes should be transcluded for easy future updates.
Templates that violate the guidelines on this page, have poorly defined function, are redundant, become orphaned or used on only one page, or violate any Wikipedia policies may be nominated for deletion at Wikipedia:Templates for discussion.

Suggested practices

Referencing templates

Sometimes you will want to refer to a template, rather than actually invoking it. An easy way to do this is to call

Template:Tlp; for example, {{tlp|Convert|1|m}} displays as {{Convert

|1|m}}.

Check the template documentation on

tlxi

|param1|param2}} (italic parameters), and many more.

Template names

Shortcut

WP:TPN

Template names can be made of one or more words, such as {{Train topics}}. The first character (only) is not case-sensitive, so {{cleanup}} and {{Cleanup}} are the same template, but {{cfd}} and {{cfD}} are not. Template names are easiest to remember if they follow standard English spelling, spacing, and capitalization (also see the

naming conventions

for articles). Avoid having templates whose names differ only in case, spacing, or punctuation.

Sandbox for experiments

If you wish to experiment with templates (and not have your experiments deleted before you are done with them), you may do so in the Template sandbox. You may also use the templates X1, X2, X3, X4, X5, X6, X7, X8, X9, X10, X11, and X12 for experimental purposes. To include a test template, use the form {{X1}} for template X1, {{X2}} for template X2, etc.

Existing templates often each have their own sandbox and test case pages (especially those that use {{Documentation}}). Changes should be thoroughly tested there before being applied to the main template, in order to prevent unintentional damage to many pages.

Readability

For templates that use a large number of parameters, it can be helpful to place each parameter on a separate line and align the equals signs. This helps future editors to more easily read the wikicode.

{{Example template name
| first_parameter  = Text of first_value
| second_parameter = Text of second_value
| third_parameter  = Text of third_parameter
| etc              = etc
}}

Line breaks

Some templates may accidentally cause extra line breaks in the rendered articles. This is especially true of

Wikipedia:Line-break handling

.

As a general guideline, avoid two line breaks together in your template. These may "add up" with other line breaks in the article and be displayed as unwanted white space.

Substitution

Invoking a template using the form

{{subst:name of template (|parameters |...)}}

(that is, inserting subst: immediately after the opening pair of curly brackets) will make a copy of the template text and place it on the page, where it will be viewable in the source. The template is no longer transcluded and future changes to the template will not change the text. As a guideline, this method should be used for any short, temporary messages which are removed quickly, such as on User_talk: pages. The standard new user {{Welcome}} message is a good example.

Use subst: also if you need to edit the message after including it on the page. If you don't need to edit it, and would rather the message is automatically updated along with changes made to the template, don't use subst:.

Documentation

Because templates represent a step up in difficulty for the novice editor, documentation should be provided which describes its usage (optional parameters) and scope (where it should be used). There are two different ways to do this:

One alternative is to use <noinclude> to add a minor description direct into the template, for example:

'''This is a {{{1}}} article.'''<noinclude>
Place this template on any article that requires description. It 
takes one parameter, an adjective used to describe the article. 
For example, {{article-describe|bad}} produces the text, 
'''This is a bad article.'''
</noinclude>

Another alternative is to create a formal

/doc subpage for the documentation (preferred for templates with multiple parameters, etc.) and add <noinclude>{{Documentation

}}</noinclude> after the actual template. The first "noinclude" tag should be placed on the same line as the end braces of the actual template in the following manner:

{{(template name)
(piped parameters)
}}<noinclude>...

If the "noinclude" tag starts on the line below the template's closing braces, then unwanted whitespace is introduced at the bottom of the template when it is used in articles and on other pages.

Modules

Lua modules are sometimes used instead of templates to store reusable material. Reasons for this include usage of module-specific features such as loops or stored values, and complex code is often easier to read and maintain in a module. If a module is easily implementable in a template it generally should be, since there are more users with experience editing templates.

If a module is intended to be used in articles or talk pages, a template wrapper should generally be created to simplify usage without directly requiring the #invoke parser function. Documentation is then mostly located on the template's /doc page, with the module's documentation pointing to the template and/or explaining further technical details that are unnecessary at the primary template documentation.

There are sometimes reasons not to use a template wrapper, however, such as causing potential issues with

template limits

; a template wrapper that passes too many parameters to a module is much less efficient compared to a direct invocation. Additionally, it is generally not desirable to use template wrappers in other templates.

History

Historically, an "msg:" prefix had to be added in front of the template name when it was used on a page. For example, {{msg:stub}} was typed instead of {{stub}}. This is no longer necessary.

In Wikipedia's first 35 months, there was no template or transclusion mechanism at all. The page Wikipedia:Boilerplate text was created in September 2002 to collect frequently used text in various Wikipedia processes. The MediaWiki namespace was introduced with MediaWiki 1.2.6 on December 6, 2003, and was used not only for the user interface but also for creating boilerplate text messages to be inserted in articles using the {{msg: ...}} syntax. This function was replaced with the Template namespace during the software upgrade to MediaWiki 1.3 on May 30, 2004. As a function of the "Template namespace initialisation script", all non-system messages were moved to the new namespace. The initialisation script also replaced MediaWiki: references in articles with Template: to bypass the redirects created by the moves.

For a short time, Wikipedia:Articles for deletion (then known as votes for deletion or VfD) used MediaWiki: messages named in the format "MediaWiki:VfD-articlename". These were moved to the Template: space in June 2004 and were named "Template:VfD-articlename". This usage is deprecated now in favor of subpages.

Around 2005, growing complexity of template functions and the desire to consolidate similar templates led to the creation of extremely complex conditional hacks such as nested templates and CSS tricks. These undesirable methods led to the development of m:Extension:ParserFunctions, added in 2006 with MediaWiki 1.7. By 2009, many problems with template readability and complexity still remained (On templates and programming languages). In 2013, in order to address page load times, mostly due to slow template renders, Lua was enabled, creating a Module: namespace for programmers to make use of (New Lua templates bring faster, more flexible pages to your wiki).

Searching for templates

Use this form to search in the Template: or Template_talk: namespaces. See Help:Searching for more information.

Pages which contain information on commonly used templates:

Wikipedia:Template index for an index of text-based templates.
Wikipedia:Navigation templates for a partial list of various subject-class navigational elements.
Wikipedia:List of infoboxes for infoboxes, which are small panels that summarize key features of the page's subject.
Wikipedia:Categorization for templates used for categories
Wikipedia:Citation templates for templates used to format article references and citations

If you're unable to find an existing template for your situation, but don't feel comfortable creating one yourself, you can ask for help at Wikipedia:Requested templates.

Notes

^ Namespaces from which transclusion is not allowed are specified on a wiki by the variable $wgNonincludableNamespaces

[1] Namespaces from which transclusion is not allowed are specified on a wiki by the variable $wgNonincludableNamespaces