Template:Documentation

Documentation icon Template documentation[view] [edit] [history] [purge]

This is the {{Documentation}} template.

This template displays a green doc box like you are seeing now, and automatically loads the content from a /doc subpage. It can also load the content from other places if instructed to.

This template is intended for documenting templates and other pages which are transcluded onto other pages. It can be used in template space and most other namespaces.

Use of this template allows templates to be protected where necessary, while allowing anyone to edit the documentation and categories.

Usage

Normally this template is used without any parameters, placed at the bottom of the template or page being documented, within <noinclude>:

<!--Last line of your template code--><noinclude>
{{Documentation}}
<!-- Add categories to the /doc subpage and interwikis in Wikidata, not here! -->
</noinclude>

Then this template automatically loads the content from the /doc subpage of the template it is used on.

This template can also load the content from any other page. Like this:

<!--Last line of your template code--><noinclude>
{{Documentation |Template:Other page/doc}}
</noinclude>

Note that when loading the documentation from another page than the local /doc page it becomes tricky to handle the categories and interwiki links.

The content can also be fed directly as text. Like this:

<!--Last line of your template code--><noinclude>
{{Documentation |content=
Some documentation text.
}}
</noinclude>

When the |content= parameter is used, the doc box normally does not show the [edit] [purge] links in the top right corner. Note that if the /doc page exists a link to it is still shown in the link box below the doc box.

Parameter |1= and the |content= parameter can also be combined, like this:

<!--Last line of your template code--><noinclude>
{{Documentation
|1=Template:Any page/doc
|content=
{{Template:Any page/doc |parameters}}
}}
</noinclude>

Then the pagename fed as parameter 1 is used for the [edit] [purge] links and for the /doc link in the link box below the doc box. But the content parameter is used for the content shown in the doc box. The above code means that the content is transcluded as {{Template:Any page/doc|parameters}}. In this example a parameter is also fed to the /doc page being loaded.

Best practice

The code should be added at the bottom of the template code, with no space before <noinclude> (which would cause extra space on pages where the template is used).

Categories and interwiki links that apply to the template itself should be added to the bottom of the /doc subpage, inside <includeonly>...</includeonly> tags.

If the documentation page contains <includeonly> or <noinclude> tags as part of the visible documentation text, replace the "<" with "&lt;".

The heading

When in the Template namespace, this template shows this heading:

Template-info.png Template documentation

In most other namespaces, such as "Festipedia:", it shows this heading:

Documentation

But when on File (image) pages it shows this heading:

Summary

The heading parameter can be used to set the heading to something else. Like this:

{{Documentation |heading=Infobox documentation}}

If the heading parameter is empty but defined, no heading is shown and no [edit] [purge] links are shown. Like this:

{{Documentation |heading=}}

The heading-style parameter can be fed optional CSS values. Without quotation marks " " but with the ending semicolons ;. For example:

heading-style = color: red; font-size: 150%;

The link box

Below the big doc box is a small link box that shows some meta-data about the documentation. The link box shows different things depending on what parameters are fed to this template, and in which namespace it is used. In some cases the link box is not shown at all.

To hide the link box, add the parameter |link box=off.

You can also insert customised text in the link box, by defining the |link box= parameter. For example: |link box=This documentation is automatically generated by [[Template:Country showdata]]

Automatic functions

If the documentation page does not exist, the [create] link includes a preload page so that clicking it will pre-fill the edit form with the basic documentation page format. Preload text is also used for the /sandbox and /testcases (create) links.

When this template is on a protected template page it now automatically adds {{pp-template}} which shows the grey or red padlock in the top right corner. So no need to manually add {{pp-template}} to templates that use {{Documentation}}.

When this template is on a /sandbox subpage it automatically adds the {{Template sandbox notice}}. If that sandbox is not a subpage of the live template, then the |livepage= parameter can be used to correctly link back to that template.

Subject namespaces vs. talk namespaces

Terminology: Subject namespaces are the opposite of talk namespaces. For instance "Template:" is the subject space of "Template talk:".

This template is usually placed in a subject namespace, within <noinclude> tags. But in some cases this template needs to be on the talk page:

  • In the Mediawiki namespace, since <noinclude> often does not work in system messages, and since the Mediawiki namespace needs to be kept clean for performance reasons.

When placed on talk pages, this template usually is placed near the top of the page and without <noinclude>...</noinclude> tags.

The /doc, /sandbox and /testcases pages should normally be in the subject namespace, except in the namespaces that do not have the MediaWiki subpage feature enabled: Main, File, Mediawiki and Category. (But currently we only show the /sandbox and /testcases links from User, User talk, Template and Template talk namespaces.) There are also a whole bunch of other technical reasons why the /doc page must be stored under the talk page for those (but only those) namespaces.

This template automatically points its [create] links for the /doc, /sandbox and /testcases to the right namespace.

Technical details

This template calls {{Documentation/start box2}} and {{Documentation/end box2}} which in turn call {{Documentation/start box}} and {{documentation/end box}}. The /start box (and /end box) hold most of the code, while this template and /start box2 (and /end box2) do parameter preprocessing.

The preload page for the /doc [create] link is Template:Documentation/preload. The preload pages for the /sandbox and /testcases [create] links are Template:Documentation/preload-sandbox and Template:Documentation/preload-testcases.

See also

  • {{Documentation}} – Placed on templates and other pages to document them.
  • {{Documentation subpage}} – Used at the top of /doc subpages to explain what they are and to link back to the page they document.


SVR Wiki

Main Page

From SVR Wiki
Jump to: navigation, search

Welcome to the Severn Valley Railway Wiki

From this week's featured article
E1682 is a BRBritish Rail or British Railways Mk 1 Buffet Restaurant carriage. It was acquired by the SVRSevern Valley Railway (BRBritish Rail or British Railways) Buffet Car Fund in 1981 and used for many years on the Severn Valley Venturer dining service. (Full article...)
Schematic Map of the SVRSevern Valley Railway
BridgnorthEardingtonHampton LoadeCountry Park HaltHighleyThe Engine HouseArleyVictoria BridgeNorthwood HaltWyre Forest LineBewdleyStourport BranchBewdley TunnelConnection to Network RailKidderminsterMaps#Schematic maps of the pre-closure SVRMapandlinks3.png
Click on the map for a
larger interactive version

For 101 years between 1862 and 1963, the Severn Valley Railway formed part of the national railway network, running for 40 miles between Hartlebury and Shrewsbury. Established as a separate company, it was mainly operated by the Great Western Railway (GWRGreat Western Railway) and later by British Railways (BRBritish Rail or British Railways).

The present day Severn Valley Railway (SVRSevern Valley Railway) was established in 1965 to preserve part of the line as a heritage railway. Today it has six stations and two halts and runs for 16 miles along the Severn Valley between Bridgnorth in Shropshire and Kidderminster in Worcestershire, following the course of the River Severn for much of its route. Operations involve a mixture of steam and heritage diesel-hauled services.

This unofficial website is a project aimed to collect information and record events relating to the SVRSevern Valley Railway, both past and present.

For timetables, fare information, and news about special events, please visit the SVR Official Website. Other news and information of interest to members, shareholders and enthusiasts can be found on SVRLive.

In April 2023 the SVRSevern Valley Railway announced the launch of a Survival Fund to enable it to overcome the current financial crisis and implement longer-term plans for its future. Information and details of how to donate may be found on the SVRSevern Valley Railway's Survival Fund page.

Categories of article

History of the Severn Valley Railway

Current events on the SVRSevern Valley Railway

Information about the SVRSevern Valley Railway

Miscellaneous


Query Corner

Unsurprisingly, there are a large number of questions about the SVRSevern Valley Railway, both in pre-preservation days and for a number of historical items since then. Take a visit down to Query Corner to see if you have a recollection relating to some long forgotten event, or know of a reliable source (maybe an early edition of the SVR News?) that might have the information we need!

In addition are a number of stub articles requiring further input.

Adding to this Wiki

This site, or "wiki", is a collaborative effort, and anyone who has any knowledge relating to the SVRSevern Valley Railway should feel free to contribute. Once you have created a user account and logged in, you can modify any page by clicking the "Edit" button in the top right hand corner. For some tips on how to format pages, and some guidelines on how to make this wiki accessible can be found on Tips for contributing to the SVR Wiki.

Alternatively, if you don't feel confident editing this Wiki (although there is no reason you shouldn't!!), each article also has a "Discussion" page, which can be accessed by clicking the relevant button in the top left hand corner. This allows you to make additions, suggestions, or corrections to a page without making any change to the article itself.


Navigation menu