TechInfoDepot:Transclusion

Transclusion means the inclusion of the content of one document in another document by reference. In TechInfoDepot, it refers to a function of the MediaWiki software that allows the content of one page to be included in the content of another page, by placing a reference to the source page in the wikitext of the target page. Changes made to a page are automatically reflected on all pages into which that page has been transcluded. A page that is intended to be transcluded into other pages is called a template.

The basic syntax used to produce transclusion in wikitext is  , which will be replaced by the content of the page named Namespace:Name when it is rendered on the user's display. If the referenced page name does not begin with a namespace identifier (Namespace:), it is assumed to be in the Template namespace. To refer to a page in the "Main" (article) namespace, it is necessary to prefix it with a colon (:). Examples:
 *   will transclude from the page Template:Like - specifically:
 *   will transclude from the page Template:Stochastic processes
 *   will transclude from the page Calculus (in the Main namespace)
 *   will transclude from the page TechInfoDepot:Assume good faith

It is also possible to pass parameters to a template, using the expanded syntax described at Help:Template, which can affect what text in the template is rendered. For example, to highlight text like this, the text-to-be-highlighted is passed as a parameter to the highlight template:.

An alternative to transclusion is substitution, whereby the current content of the template is automatically copied into the wikitext of the target page on saving, and will then be an indistinguishable part of the saved page, independent of any later changes made to the template. The syntax for this is

Applications of transclusion
The most common application of transclusion is in the use of templates. However, other pages are also sometimes transcluded, mainly within project space.

Composite pages
The wikitext of a page may (partly or fully) consist of tags for the inclusion of component pages. The component pages are usually not in the template namespace, and are often full pages in their own right. Composite pages are intended to gather the material on them into a central location.

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

This allows the choice between viewing the component pages separately or together. Viewing a composite page is convenient when there are many small, related component pages, in that it allows an overview of all the components without the effort of following numerous links.

In general, each component page and the composite page are treated separately. While the actual changes on the component pages will be transcluded onto the composite page, the edit history, recent changes, page-watch settings, page protection, TOC, "what links here" link, and other features of the composite page do not reflect or affect the histories, watch settings, protection levels, what links here lists of the component pages. The composite page is a page in its own right. The talk page of a composite page is used to talk about the composition and the page in general, not the component pages, though it in turn could be a composite of the talk pages of the component pages.

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.

See also TechInfoDepot talk:Template namespace/Archive 1.

Pages with a common section
When two pages need to discuss the same material in the same way, they can share a section. This involves creating a third page and transcluding that page onto both pages. This third page may be a page in its own right or a subpage of either of the other two, and if the first it may be placed in the same namespace as the other pages or in template namespace. Common sections like this should be marked with an explanatory header, 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.

Examples:

Repetition within a page
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:List of Languages calls Template:Lang def repeatedly with different parameters in order to generate the visible text.

Simple repetition of the same text can be handled with repetition of a parameter in a single template: e.g., 3x, where produces.

For more information on repetition See also m:Help:Recursive conversion of wikitext.

For more information on the current template system, see TechInfoDepot:Template namespace.

Markup
There are three pairs of tags that can be used in wikitext to control how transclusion affects elements of a template or article. They determine whether or not wikitext renders, either in its own article, which we will call "here", or in another article where it is transcluded, which we will call "there". There can be several such section elements. Also, they can be nested. All possible renderings are achievable. For example, to render there one or more sections of the page here use   tags. To append text there, wrap the addition in   tags above, within, or below the section. To omit portions of the section, nest   tags within it.
 *   this content will not be rendered there   . These tags have no effect here.
 *   this content will render only there, and  will not render here   (like invisible ink made visible by means of transclusion).
 *   this content will render here and will render there   but  the rest of the article will be excluded from rendering there.

As a memory aid insert the phrase in transclusion between the two words to get "noInTransclusionInclude", "includeInTransclusionOnly" and "onlyInTransclusionInclude".


 * See, for example, the wikitext of the wiki news thread.

Selective transclusion
Selective transclusion is the process of partially 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  …  tags, and transcluding the whole page. However, to transclude one section from a template or document into one page, and another section from the same template or document into another page, that's selective transclusion, which requires a way to:
 * a) uniquely mark each transcludable section in the source document; and
 * b) in the target document(s) (those to show the transcluded sections), a way to specify which section is to be transcluded.

This section describes how to accomplish this.

Source Document Markup
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:
 *  

Target Document Markup
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:
 *  

Thus each section is enclosed within  … </tt> tags will always be rendered when the transcludesection</tt> parameter is not set (when the document is viewed ordinarily, or when the document is transcluded without setting the transcludesection</tt> parameter as shown below), and will be rendered by transclusion on any page that does set transcludesection</tt> to the section's name. It will not be rendered by transclusion that uses the transcludesection</tt> parameter but sets it to anything other than the name of the section.

Also, when providing PAGENAME, without providing a Namespace, the wiki will assume that the PAGENAME belongs in the Template Namespace. To transclude from a Mainspace article, use :PAGENAME.


 *  </tt>

Example
If we want to make the "Principal Criteria" and "Common Name" sections of WP:TITLE be independently transcludable, we edit the WP:TITLE page and enclose the "Principal Criteria" section as follows:
 *  </tt>

Similarly, we enclose the "Common Name" section with:
 *  </tt>

Then, to transclude the "Principal Criteria" section into another page, we insert into that page:
 *  </tt>

To transclude the "Common Name" section into another page, we insert into that page:
 *  </tt>

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 each transcludesection</tt> be given a value that is unique within that page.

Subpages
One can cut and paste the text to be transcluded into a subpage, then use the name of the subpage in the transclusion template. This approach can only be used with subpages from User, Talk or TechInfoDepot pages; currently, subpages cannot be created from main article pages.

Example: you want to discuss the deletion and redirecting of Pussycat to Cat. First, create the subpage Talk:Pussycat/Let's delete Pussycat!, write your comment into it, then transclude it in Talk:Pussycat and Talk:Cat using the template  . Comments posted in either talk pages will be shown in both. To ease editing of the subpage, it may be helpful to precede the transcluded talk with lat, e.g. . Transcluding in this way will not preserve a fixed record of the discussion at the time of any archiving, so discussions should be closed in conjunction with archiving. An alternative is to centralise discussion in the normal manner on a single talk page and point to it using by substituting Pls templates, per WP:MULTI.

Special pages
Some pages on Special:Specialpages can be transcluded, such as Special:Allpages, Special:Prefixindex, Special:Newfiles, Special:Newpages, Special:Recentchanges and Special:Recentchangeslinked. Samples:
 * – a list of pages starting at "General"
 * – a list of pages with prefix "General"
 * – a gallery of the four most recently uploaded files
 * – a list of the five most recently created pages
 * – the five most recent changes
 * – recent changes to the pages linked from "General"

Except for Special:Recentchangeslinked, the slash and the word/number after the slash can be omitted, giving a list of pages without a specific starting point, or a list of the default length.

Note: Transcluding certain special pages (such as Special:Newpages) can change the displayed title of the page.

Pages related to MediaWiki transclusion

 * m:Help:A simple composite example
 * TechInfoDepot:MediaWiki namespace
 * m:Help:MediaWiki namespace
 * m:Help:Variable
 * TechInfoDepot talk:Template namespace

Templates

 * Help:Template
 * TechInfoDepot:Template namespace
 * TechInfoDepot:Template limits