Manual:Creating pages with preloaded text

Jump to: navigation, search
Language:Project:Language policy English  • français • 日本語

Preloading wikitext presents the user with a partially created page, possibly with inline instructions for content organization, rather than a blank page. This technique is especially useful when the wiki contains one or more categories of articles, with lots of pro-forma text or the information that needs to be collected for such articles is a mix of structured data and free form text.

Creating pages with preloaded text is a three step process:

  1. Design the preload file and its supporting templates
  2. Create pages for the preload files and supporting templates
  3. Set up the trigger to load the preload file

Designing the preload file[edit source]

The preload file is often an article with an embedded template. For example, if you wanted one article for each customer or marketing contact, you might want to preload text that looks something like the example below.

   <!-- Please enter your customer's contact information after the equal sign.
        If you need help uploading the business card images, please see
        [[Help:Uploading business card images]] 
   |Primary phone number=

Naming and documenting the preload file[edit source]

Some extensions (see Extension:Boilerplate) have specific expectations as to where the preloaded text should be stored. Others leave that decision entirely up to the system administrator.

Naming and documenting the preload file takes some care, because preload files don't always show up on "What links here" and so are at risk for accidental deletion (no info/no links—hard to tell from an article that got created and abandoned). For template based preload files, the following naming conventions may help avoid accidental deletion:

  • place template in Template:CategoryName
  • place preload file in Template:CategoryName/Preload

Note: before the fixing of task T7210, preload templates could not contain documentation, categories, interlanguage links etc.—all content would affect the preload output. With bug 5210 fixed, <noinclude> tags now work as expected.

Loading the preload file[edit source]

Preloading can be done with a preload parameter in a URL like which links to the edit box of a new page, preloaded with Template:Foo. There are also a number of extensions available to trigger your preload file, see below.

The wikitext of the source page is preloaded into the editbox if the page or section does not exist yet. If the page or section to be edited already exists then only its wikitext is loaded, the preload command is ignored.


  • In MediaWiki versions before 1.17, both the <noinclude> and </noinclude> tags AND their content are preloaded, which means you can't categorize the source page or include some self-documentation: it'd be dumped into the preloaded text too. As of MediaWiki 1.17, these are now removed; if you need the preloaded text to provide noinclude tags, you can use
    in your source: since the two middle tags will be stripped (see next), the preloaded text will end up with just the desired <noinclude>.
  • The <includeonly> and </includeonly> tags are stripped from the source page. If you need the preloaded text to provide includeonly tags, you can use
    in your source: since the two middle tags will be stripped, the preloaded text will end up with just the desired <includeonly>.

Thus there is neither a complete inclusion nor a regular transclusion. See also task T7210 (since 2006-03-09).

If it is creating a new section, the initial content of the "Subject/headline" box can be provided with the parameter "preloadtitle"

If it is not creating a new section, the summary can be set with the summary parameter (task T19002).

The minor edit checkbox can be set by adding minor parameter

Using parameters[edit source]

MediaWiki version: 1.23

You can also specify parameters to the preload text with the preloadparams[] url parameter (When linking on wiki, you may want to escape the [] to be %5b%5d.) Each parameter specified replaces a $1, $2, ... variable.

Note: $1, $2, ... variables are distinct from {{{1}}}, {{{2}}}, ... variables. In order to use preloadparams[], it appears to be necessary for the template to use $1, $2, ... variables instead of {{{1}}}, {{{2}}}, ... variables. This documentation should be improved by explaining why these two distinct template parameter notations exist, and when it is possible or necessary to use each of the two notations.

For example:

Extensions[edit source]

Extensions that trigger a preload file include:

A few extensions also handle all three steps for you:

All extensions related to page creation are in the Page creation extensions category.

See also[edit source]