![]() | This is aninformation page. It is not anencyclopedic article, nor one ofWikipedia's policies or guidelines; rather, its purpose is to explain certain aspects of Wikipedia's norms, customs, technicalities, or practices. It may reflect differing levels ofconsensus andvetting. |
Transclusion refers to the inclusion of the content from one document within another document byreference. In Wikipedia, transclusion means theMediaWiki software retrieving the content from asourcepage, often atemplate, and incorporating it into the content of atarget page.
Similar to creating awikilink using double square brackets (
), a page can be transcluded as a template by enclosing its title in double curly braces or double curly brackets:[[Pagename]]
{{Namespace:Pagename}}
. Any changes made to the source page, or template, are automatically reflected on all pages that include the transcluded content.[a]
If nonamespace is specified, it is assumed to be in theTemplate namespace. To refer to a page in theMain article namespace, it is necessary to prefix it with a colon (:
). For example:
{{Pagename}}
is the same as{{Template:Pagename}}
{{Stochastic processes}}
will transclude from the pageTemplate:Stochastic processes{{:Stochastic process}}
will transclude from the pageStochastic process (an article, in the Main namespace){{Wikipedia:Assume good faith}}
will transclude from the pageWikipedia:Assume good faithTransclusion and what content it includes or excludes can be modified by using the invisiblewikitext tags<noinclude>
,<onlyinclude>
,<includeonly>
, and<section>
on thesource page, as further outlined in§ Transclusion markup.[b] The first three tags enable§ Partial transclusion, as opposed to the default behavior of double curly braces, which will transclude the entire source page's content. For§ Selective transclusion, the<includeonly>
or<section>
tags can be used and sections of the source page named, then usingparser functions the template can be called with the section name as aparameter:{{#section:Pagename|Sectionname}}
.
Transclusion events occur each time thetarget page is loaded and the template is rendered. A related event isSubstitution, where a template call is replaced with its transcluded source content at the time it is invoked in aone-time inclusion of the content. Unlike transclusion, which continuously updates the target page with changes from the source, substitution results in aone-time inclusion of the content, meaning that subsequent updates to the source contentwill not be reflected in the target page. For example, a template call for{{Pagename}}
with thesubst:
prefix results in the substitution template call{{subst:Pagename}}
. When invoked, this template is replaced, also referred to as substituted, with the actual wikitext of the source page at the time of the call, thereby making it a permanent part of the target page.[c]
It is possible totransclude content from Wikidata into Wikipedia articles or other wikis.
To transclude content from asource page within a single MediaWiki project (such as English Wikipedia) onto atarget page, use{{SOURCEPAGE}}
in thetarget page's code.
Whenever{{SOURCEPAGE}}
is included on a target page, the WikiMedia software retrieves and embedes the entire content ofSOURCEPAGE
(i.e.,Template:SOURCEPAGE) at that location on the target page.
Consider an example, complemented by the illustration below, with target pagesA,P, andQ, and source pageB.
If source pageB is transcluded intoA, the content fromB (for instance, the word "foo") will appear in place of the{{B}}
code in pageA. When transcluded, this content is not highlighted or boxed on the target page – it is integrated directly into the page's text (highlighted here only for illustration).
Transclusion creates a 'live' link between a source page and all target pages where its content is transcluded to and used. Editing the source page automatically updates its content on all target pages that include it.
For example, if you create a source page with details about a Wikimedia event and transclude it onto the talk pages of 50 editors you wish to invite, any updates you make to the source page (such as changing the event location) will immediately reflect on all 50 talk pages.
Edits to a source page can impact all target pages using it. If a source pagealso contains its own transclusions from other source pages, avoid changes that may break these links, as this would affect the source page you are editing and all target pages that transclude it. This is known as 'breakage', and it is best to ensure any updates maintain the integrity of transcluded content across all pages. For example,Main Page is a large page that transcludes its content from multiple embed source pages such asWikipedia:Today's featured list.
The generalsyntax for transclusion on Wikipedia follows the format{{Namespace:Pagename}}
, whereNamespace:Pagename
specifies thetitle of a Wikipedia page.
Similar to creating awikilink using double square brackets (
), a page can be transcluded as a template by enclosing its title in double curly braces:[[Pagename]]
{{Namespace:Pagename}}
. Any changes made to the source page, or template, are automatically reflected on all pages that include the transcluded content.[d]
Wikipedia is structured usingnamespaces, which organize pages based on their function. For example, a page titledWikipedia:Tips belongs to the Wikipedia namespace, withWikipedia:
as its namespace andTips
as its pagename. However, articles in theMain namespace, such asPotato, do not require a namespace prefix when linked using
, as Wikipedia assumes any wikilink without a specified namespace belongs to the Article namespace.[[Potato]]
When transcluding pages, if no namespace is specified, Wikipedia defaults to theTemplate namespace. To reference a page in the Article namespace within transclusion syntax, itmust be explicitly prefixed with a colon: (e.g.,{{:Potato}}
).
{{Namespace:Pagename}}
will transclude the page titledNamespace:Pagename
. For example, if a page has the wikitext{{Wikipedia:Notability}}
in it, it will transclude the pageWikipedia:Notability into it. Please note that{{WP:Notability}}
would do exactly the same thing, asWP:
is anamespace alias, which isautomatically translated by the Wikipedia servers toWikipedia:
.{{:Pagename}}
, the mainspace articlePagename
will be transcluded. For example,{{:Notability}}
will transclude the article [[Notability|Notability]].{{Pagename}}
, theTemplate:Pagename
will be transcluded. For example{{Notability}}
, and also{{Template:Notability}}
, will both transclude the [[Template:Notability|Template:Notability]].Additionally, specific§ Template parameters and§ Transclusion modifiers allowparameters to be passed to templates, alter how transclusion occurs, and therefore the output customized. This is explained in more detail below.
Subpages, identifiable by a/
prefixed in their page names, are pages related to a 'parent' page (e.g.,Namespace:Pagename/Subpagename
is a subpage ofNamespace:Pagename
). This feature is disabled in the Main, File, and MediaWiki namespaces, but not on their corresponding talk namespaces.
To transclude subpages:
{{Namespace:Pagename/Subpagename}}
. With exception:{{/Subpagename}}
.{{Pagename/Subpagename}}
.{{:Pagename/Subpagename}}
.For example, to transcludeTemplate:Like/doc, you could use{{Template:Like/doc}}
or{{Like/doc}}
. Note that subpage names are case sensitive, and{{Like/Doc}}
would lead to a different page.
The most common use of transclusion on Wikipedia is fortemplates. Templates are specially designed pages intended to be included in other pages using either transclusion orsubstitution. The standard syntax for transcluding a template titledTemplate:Pagename is{{Pagename}}
.
Additionally, many templates supportparameters, which are variables that allow templates to function in different ways by passing specific values, also termedarguments. Templates may have no parameters, use a fixed number of parameters, or support a variable number of parameters. The number of parameters a template can accept ranges from one to multiple, depending on its design.
The exact syntax for using parameters varies by template. However, for a hypothetical template titledTemplate:Pagename that accepts three parameters, the general format would be:
{{Pagename|parameter1|parameter2|parameter3}}
Where each parameter in a template can be substituted with either avalue
or a|parameter name=value
format when used in practice. Notice that each parameter is separated by avertical bar (|
). Parameters that take the formvalue
are calledunnamed orpositional parameters, while those in the form|parameter name=value
are known asnamed parameters. With unnamed parameters, the first, second, and third parameters correspond to|1=
,|2=
,|3=
, respectively, etc., intemplate documentation. Unnamed parameters must be provided in the correct order and are best placed before named parameters.[e]
For example, using theTemplate:Collapse top with two unnamed parameters and one named parameter:
{{Collapse top|This is the title text|This is a custom warning line|left=true}}
{{Collapse top|left=true|1=This is the title text|2=This is a custom warning line}}
{{Collapse top|left=true|This is the title text|2=This is a custom warning line}}
In this case,This is the title text
andThis is a custom warning line
are the values of unnamed parameters|1=
and|2=
, whiletrue
is the value assigned to the named parameter|left=
. The last example shows how unnamed parameters should not be used after named parameters without their 'name'. Although this example includes three parameters,Template:Collapse top can accept a variable number of parameters.
For more details, seeHelp:Template. Additionally,Wikipedia:Template index provides a categorized list of templates, including those for mainspace and other namespaces, along with a search function. Template parameters also play a role in the§ Parametrization method of§ Selective transclusion, allowing for more dynamic content inclusion.
Transclusion events occur each time the target page is loaded and the template is rendered. A related event is Substitution, where a template call is replaced with its transcluded source content at the time it is invoked in aone-time inclusion of the content. Unlike transclusion, which continuously updates the target page with changes from the source, substitution results in aone-time inclusion of the content, meaning that subsequent updates to the source contentwill not be reflected in the target page. For example, a template call for{{Pagename}}
with thesubst:
prefix results in the substitution template call{{subst:Pagename}}
. When invoked, this template is replaced, also referred to as substituted, with the actual wikitext of the source page at the time of the call, thereby making it a permanent part of the target page.[f]
For example, when{{subst:Like}}
is inserted in a page and the changes published, it would substitute that wikitext with the actual wikitext fromTemplate:Like. In practice, subsequent updates toTemplate:Likewill not be reflected in the page it was substituted into.
Magic words are not examples of transclusion. But some have a near identical double curly bracket syntax and similar action to transclusion. For example,{{FULLPAGENAME}}
renders the fullpage name of any Wikipedia page, for example it returnsHelp:Transclusion on this page. Like templates, some magic words can also take parameters, which are separated using a colon (:
); for example{{TALKPAGENAME:Help:Transclusion}}
returnsHelp talk:Transclusion.
Templates do exist for some magic words, for exampleTemplate:FULLPAGENAME; but these just invoke the related magic word and pass parameters using the verticle bar (|
) to the magic word in anycase; for example like{{FULLPAGENAME|value}}
. But magic words parameters are best passed directly by using a colon, which bypasses the unnecessary use of a template call too. For example,{{FULLPAGENAME|value}}
is synonymous with{{FULLPAGENAME:value}}
, where the latter is preferred.
Atransclusion modifier is a type of specialist magic word for altering transclusion in some manner. An example of which is thesubst:
modifier discussed above in§ Substitution. Another example is{{:Notability}}
, where the colon character (:
) forces transclusion to the main namespace. There are additional transclusion modifiers such assafesubst:
,int:
,msg:
,msgnw:
, andraw:
. For more details on their usage, seemw:Help:Magic words § Transclusion modifiers. Also see the modified commands#section:
,#section-x:
and#section-h:
used for labeled section transclusion, seeHelp:Labeled section transclusion and the section§ Using the labeled section method.
Transclusion is commonly used intemplates, allowing content to be embedded dynamically across multiple pages. However, it is also applied in other contexts, particularly within project space, where it facilitates the management of structured content.
Composite pages are created by transcluding multiple component pages, either entirely or in part, into a central page. The wikitext of a composite page may includeHTML tags to embed content, typically from standalone pages that are not part of the template namespace. The primary purpose of composite pages is to consolidate related content for easier access.
The use of composite pages allows users to view multiple related pages in one location rather than navigating through individual links.
Composite pages function independently from their component pages in several ways. While changes made to a component page are reflected on the composite page, the composite page maintains its own edit history, recent changes log, page-watch settings, and protection levels, separate from those of its transcluded content.
The talk page of a composite page is used specifically for discussions about the composite itself rather than for the individual component pages it includes. However, in some cases, a composite talk page may also transclude discussions from its component pages, allowing for acentralized discussion space.
When editing, users can modify sections of a component page directly from the composite page, seeHelp:Section § Editing sections of included templates. Once changes are saved, they are applied to the original component page, ensuring consistency across all instances where the content appears.
For projects that supportinterlanguage links, a composite page aggregates all interlanguage links from its component pages. This can sometimes lead to multiple links pointing to the same language or page, reflecting the structure of the transcluded content.
When two pages need to discuss the same material in the same way, they can share a section. For example, a section of an existing page may be transcluded to other pages. This may also involve creating a third page and transcluding that page onto both pages. This third page may be a standalone page in its own right for another purpose, or a subpage of either of the other two – except in the mainspace, wheresubpages are not allowed. The third page may be placed in the same namespace as the other pages or in template namespace – again, except for use in mainspace, where templates should not be used to storearticle text, as this makes it more difficult to edit the content (seeWP:TG). Common sections like this should be marked with an explanatory header, such as using the templates{{Transcluding article}} or{{Transcluded section}} to createhatnotes above the transcluded content, and/or given a special layout, to inform the reader that this section of the page is in a different location, since transcluding shared article sections can easily confuse novice editors and readers alike if left unmarked. All templates can be found atCategory:Transclude page content templates.
This can be very useful when twodisambiguation pages share content,[disputed –discuss] or alist page and a disambiguation page share content (see third example below).
Examples:
{{Help:Editing sections of included templates}}
. By including a heading in the included article, a user clicking the "Edit" link on that heading inHelp:Section is automatically directed to editHelp:Editing sections of included templates.On pages where there is a lot of repetitive information — various kinds of lists, usually — it is sometimes useful to make a template that contains the repeating text, and then call that template multiple times. For example,Template:EH listed building row is used repeatedly to construct tables in many articles.
Simple repetition of the same text can be handled with repetition of a parameter in a single template: e.g.,{{3x}}, where{{3x| howdy!}}
produces howdy! howdy! howdy!
.
For more information on repetition, see alsom:Help:Recursive conversion of wikitext.
For more information on the current template system, seeWikipedia:Template namespace.
By using<noinclude>
,<includeonly>
and<onlyinclude>
markup, it is possible to transcludepart of a page, rather than all of it. Such partial transclusions can be achieved by transcluding from any pages, including subpages. It is often useful to exclude part of a page in a transclusion, an example being with template documentation.
For an example of how this technique can be applied to simplify the creation ofsummary articles, see how part of theHistory of pathology (see the diffhere) was transcluded intoPathology (see the diffhere) using the{{:History of pathology}}
markup. The Pathology article at that time (seehere) mainly consisted of transcludedlead paragraphs and other sections from a number of articles. Since then, the Pathology article has been rewritten, and does not include all these transclusions.
Another example can be found in the transclusion of part ofHitRecord (introductory paragraph only) into a same-named summary section inJoseph Gordon-Levitt.
In transclusion, a source page is transcluded into a destination page. But with partial transclusion, only part of that source page will be transcluded into a destination page. But in addition, what is transcluded to a destination page does not have to be visible on the source page.
Page rendering of a source page can be defined as the rendering of that source page when it is saved, which will be the same as thepreview. We can call this renderinghere.
Transclusion rendering of a source page can be defined as the rendering of a destination page that has a source page transcluded into it; but only that part of the destination page that was transcluded from the source page. The preview of the transclusion rendering will again be identical. We can call this renderingthere.
There are three pairs of tags involved in cases where page renderinghere should differ from transclusion renderingthere. As described earlier, these are<noinclude>
,<includeonly>
and<onlyinclude>
. These tags are invisible, but affect both page renderinghere and transclusion renderingthere. These tags pair-off to demarcate sections that will create differences. Each tag will describe exceptions to transcluding the whole page named.
<noinclude> This section is visible here; but this section is not visible there. Sections outside of these tags will be visible both here and there. </noinclude><onlyinclude> This section is visible here; this section is also visible there. Sections outside of these tags will be visible here, but will not be visible there. </onlyinclude> <includeonly> This section is not visible here; but it is visible there. Sections outside of these tags will be visible both here and there. </includeonly>
Wikitext | What is renderedhere (source page) | What is transcludedthere (destination page) |
---|---|---|
<noinclude>text1</noinclude> text2 | text1 text2 | text2 |
<onlyinclude>text1</onlyinclude> text2 | text1 text2 | text1 |
<includeonly>text1</includeonly> text2 | text2 | text1 text2 |
An important point to note is that<noinclude>
and<onlyinclude>
do not affect what is page renderedhere at all, unlike<includeonly>
. The<noinclude>
tags stops text inside the tags being transcludedthere, while<onlyinclude>
has the opposite effect: it stops text outside of the tags from being transcludedthere.
Only<includeonly>
stops text from being page renderedhere. But naturally enough it is transcludedthere. Text outside of the tags will be both renderedhere and transcludedthere.
There can be several such sections. Also, they can be nested. All possible differences betweenhere andthere are achievable.
One example is a content editor who picks an<onlyinclude>
section, and then takes a<noinclude>
section out of that; but then picks out yet another<onlyinclude>
section to append tothere; but none of this affects their article in any way.
Another example is the template programmer, who will<includeonly>
the code section and<noinclude>
the documentation section of a page.
Selective transclusion is the process ofpartially transcluding one selected section of a document that has more than one transcludable section. As noted above, if only one section of a document is to be transcluded, this can be done by simply surrounding the section of interest with<onlyinclude> …</onlyinclude>
tags, and transcluding the whole page. However, to selectively transclude one section from a template or document into one page, and another section from the same template or document into a second page and/or a different section of the same page, requires a way to:
This section describes how to accomplish this. There are three ways of doing this: (1) Section header-based transclusion, (2) Labeled section transclusion, and (3) the parametrization method.
![]() | This method may cause line break insertion: Standard section transclusion may introduce a leading or trailingline break or newline, depending on the markup in the source and target pages. To prevent this,wrap the transclusion code in a{{trim}} template. Seeexamples below. |
Standard section transclusion uses{{#section-h:PAGENAME|SECTIONNAME}}
. One can easily transclude the content within a section from one page to another using the ubiquitous headline-basedsection headers used throughout Wikipedia. To transclude thelead section of an article with this method, one can use{{#section-h:PAGENAME}}
. This method is simpler than other selective transclusion methods, which require specialmarkup in the source article or page to specify what content should be included or excluded.
Standard section transclusion may introduce a leading or trailingline break or newline, depending on the markup in the source and target pages. To prevent this,wrap the transclusion code in a{{trim}}
template. For example:
{{trim|{{#section-h:PAGENAME|SECTIONNAME}}}}
{{trim|{{#section-h:PAGENAME}}}}
To indicate on thetarget page where selectively transcluded content originates (its source), a{{Transcluded section}}
hatnote must be placed at the top of the corresponding section in thetarget page where the content is being transcludedto.[g][h] Use either of the following, depending on whether the transcluded content is the entire section or only part of it:
{{transcluded section|source=PAGENAME#SECTION}}
, which renders as:|part=yes
:{{transcluded section|source=PAGENAME#SECTION|part=yes}}
, which renders as:It is recommended to include ahidden comment at the beginning of the transcluded section in thesource page. This comment informs editors that the content is being used elsewhere and serves as a reminder to consider the broader audience when modifying the wording. Additionally, it helps maintain the integrity of the transcluded material on the target page. For example (replace[[PAGENAME#SECTION]] with the name of the target page):
<!-- The content of this section is transcluded to
[[PAGENAME#SECTION]]
. Please be aware that changes made to the original source here will affect the transcluded version on the target page mentioned. -->
No hatnote should be placed on thesource page, in other words no hatnote is needed on the page being transcludedfrom, as readers do not need to know where else the content appears.
Labeled-section selective transclusion uses theparser functions listed inmw:Extension:Labeled Section Transclusion, which are enabled on all Wikimedia wikis, to selectively transclude content. SeeHelp:Labeled section transclusion for how labeled section transclusion works.
Insert the following line into the "source" document (the one from which text is to be transcluded), immediately preceding the first line of each section to be transcluded, substituting SECTIONNAME (twice) with the unique name of the respective section. The section name can be any identifier and must be unique within that document:
<onlyinclude>{{#ifeq:{{{transcludesection|SECTIONNAME}}}|SECTIONNAME|
End each such transcludable section with:
}}</onlyinclude>
To transclude a section marked as above into another page (the "target page"), use the following line on that page, substituting PAGENAME for the "source" document from which text to be transcluded, and SECTIONNAME with the name of the section you want to transclude:
{{PAGENAME|transcludesection=SECTIONNAME}}
Thus each section enclosed within<onlyinclude> …</onlyinclude>
tags will always be rendered when thetranscludesection
parameter is not set (when the document is viewed ordinarily, or when the document is transcluded without setting thetranscludesection
parameter as shown below), and will be rendered by transclusion on any page that does settranscludesection
to the section's name. It willnot be rendered by transclusion that uses thetranscludesection
parameter but sets it to anything other than the name of the section.
Also, when providing PAGENAME, without providing aNamespace, the wiki will assume that the PAGENAME belongs in theTemplate Namespace. To transclude from aMainspace article, use :PAGENAME.
{{:PAGENAME|transcludesection=SECTIONNAME}}
If we want to make the "Principal Criteria" and "Common Name" sections ofWP:TITLE be independently transcludable, we edit the WP:TITLE page and enclose the "Principal Criteria" section as follows:
<onlyinclude>{{#ifeq:{{{transcludesection|principalcriteria}}}|principalcriteria|...''(text of "Principal Criteria" section)''...}}</onlyinclude>
Similarly, we enclose the "Common Name" section with:
<onlyinclude>{{#ifeq:{{{transcludesection|commonname}}}|commonname|...''(text of "Common Name" section)''...}}</onlyinclude>
Then, to transclude the "Principal Criteria" section into another page, we insert into that page:
{{WP:TITLE|transcludesection=principalcriteria}}
To transclude the "Common Name" section into another page, we insert into that page:
{{WP:TITLE|transcludesection=commonname}}
Of course, the same page can transclude two or more sections this way by including multiple such lines.
There is no limit to how many selectable sections for transclusion a document can have. The only requirement is that eachtranscludesection
be given a value that is unique within that page.
PerMOS:LEAD#Format of the first sentence, the first instance of the sub-article title should appear in bold in the first lead sentence of that article; this is often not desirable for a transclusion to a section of the parent article. In addition, the parent article is often wikilinked in the lead of a sub-article; when transcluded to the parent article, this wikilink will appear as bold text. The wikitext markup listed below can be used to address both of these problems.
To ensure that the article title is bolded in the first sentence of the sub-article, but unbolded and wikilinked in the transclusion to the parent article, make the following replacement in the sub-article's first lead sentence:
SUB-ARTICLE_PAGENAME
<noinclude>'''</noinclude>{{No selflink|{{var|SUB-ARTICLE_PAGENAME}}}}<noinclude>'''</noinclude>
If there is a wikilink to the parent article in the lead section of the sub-article, replacing the wikilink to the parent article with a{{no selflink}}
template will ensure that it is wikilinked in the sub-article's lead but not in the transclusion to the parent article. In other words:
[[PARENT_ARTICLE]]
with{{no selflink|PARENT_ARTICLE}}
in the sub-article's lead[[PARENT_ARTICLE|Piped link wikitext]]
with{{No selflink|PARENT_ARTICLE|Piped link wikitext}}
in the sub-article's leadLike many software technologies, transclusion comes with a number of drawbacks. The most obvious one being the cost in terms of increased machine resources needed; to mitigate this to some extent,template limits are imposed by the software to reduce the complexity of pages. Some further drawbacks are listed below.
<noinclude>
,<includeonly>
and<onlyinclude>
markup at the transcluded page to haveselective content; that would require monitoring that the markup is sustained.Some pages onSpecial:Specialpages can be transcluded, such asAllPages,PrefixIndex,NewFiles,NewPages,RecentChanges,WhatLinksHere (seehelp page), andRecentChangesLinked.Samples:
{{Special:AllPages/General}}
– a list of pages starting at "General".{{Special:PrefixIndex/General}}
– a list of pages with prefix "General".{{Special:NewFiles/4}}
– a gallery of the four most recently uploaded files.{{Special:NewPages/5}}
– a list of the five most recently created pages.{{Special:RecentChanges/5}}
– the five most recent changes.{{Special:RecentChangesLinked/General}}
– recent changes to the pages linked from "General".{{Special:Contribs/Larry Sanger|offset=20021108002158|limit=50}}
– user contributions prior to November 2002, limited to 50.Attempting to transclude{{Special:Categories}}
will not result in an actual list of categories, but{{Special:PrefixIndex/Category:}}
can be used for this purpose.
Except forSpecial:RecentChangesLinked
, the slash, and the word or number after the slash, can be omitted, giving a list of pages without a specific starting point, or a list of the default length.
URL parameters can be given like template parameters:
{{Special:RecentChanges|namespace=10|limit=5}}
– the five most recent changes in the "Template" namespace.{{Special:PrefixIndex/Jimbo Wales/|namespace=2|stripprefix=1}}
– the subpages forUser:Jimbo Wales, but without the user page prefix.Note: Transcluding certain special pages (such asSpecial:NewPages) can change thedisplayed title of the page.
Transclusion occurs beforeparsing and can emit syntax fragments, like HTML entities, to preserve them in the final render. The content being transcluded is processed and embedded before the target page is parsed and fully rendered. When transclusion happens at the HTML layer before parsing, it allows certain content – like syntax fragments such ascharacter entity references like&
andmp;
or specific HTML components – to be inserted in their original form and preserved in the final render. However, this approach may cause pages to render incorrectly or violate theprinciple of least surprise for the reader.[i] It should be used sparingly when cleaner alternatives are not available. Emitting fragments of template syntax, such as opening braces ({{}}
), is unlikely to re-parse correctly as template syntax in the target page, and it is unwise to rely on such behavior unless formally documented.
value
on its own will not work, and the unnamed parameters must be called using their 'names', such as|1=value
, if named parameters precede them.