Template:Documentation/testcases
![]() | This is the template test cases page for the sandbox of Template:Documentation. to update the examples. If there are many examples of a complicated template, later ones may break due to limits in MediaWiki; see the HTML comment "NewPP limit report" in the rendered page. You can also use Special:ExpandTemplates to examine the results of template uses. You can test how this page looks in the different skins with these links: |
{{Documentation}} | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
{{Documentation}} {{Documentation}}
This is the {{Documentation}} template. For most of the instructions about how and when to use this template, see w:Wikipedia:Template documentation. 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[edit]Normally this template is used without any parameters, placed at the bottom of the template or page being documented, within <!--Last line of your template code--><noinclude> {{Documentation}} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </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}} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </noinclude> Note that when loading the documentation from a page other than the local /doc page it becomes tricky to handle categories. The content can also be fed directly as text. Like this: <!--Last line of your template code--><noinclude> {{Documentation |content= Some documentation text. }} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </noinclude> When the Parameter <!--Last line of your template code--><noinclude> {{Documentation |1=Template:Any page/doc |content= {{Template:Any page/doc |parameters}} }} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </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[edit]The code should be added at the bottom of the template code, with no space before Categories that apply to the template itself should be added to the bottom of the /doc subpage, inside If the documentation page contains The heading[edit]When in the Template namespace, this template shows this heading: In most other namespaces, such as "Wikisource:", it shows this heading:
But when on File (image) pages it shows this heading:
The heading parameter can be used to set the heading to something else. Like this:
If the heading parameter is empty but defined, no heading is shown and no [edit] [purge] links are shown. Like this:
The heading-style parameter can be fed optional CSS values. Without quotation marks
The link box[edit]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 You can also insert customised text in the link box, by defining the Automatic functions[edit]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}}. Subject namespaces vs. talk namespaces[edit]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
When placed on talk pages, this template usually is placed near the top of the page and without 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. Testing[edit]You can simulate the output for a given page by using the Technical details[edit]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. For more technical details see the talk page. See also[edit]
This is the {{Documentation}} template. For most of the instructions about how and when to use this template, see w:Wikipedia:Template documentation. 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[edit]Normally this template is used without any parameters, placed at the bottom of the template or page being documented, within <!--Last line of your template code--><noinclude> {{Documentation}} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </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}} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </noinclude> Note that when loading the documentation from a page other than the local /doc page it becomes tricky to handle categories. The content can also be fed directly as text. Like this: <!--Last line of your template code--><noinclude> {{Documentation |content= Some documentation text. }} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </noinclude> When the Parameter <!--Last line of your template code--><noinclude> {{Documentation |1=Template:Any page/doc |content= {{Template:Any page/doc |parameters}} }} <!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> </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[edit]The code should be added at the bottom of the template code, with no space before Categories that apply to the template itself should be added to the bottom of the /doc subpage, inside If the documentation page contains The heading[edit]When in the Template namespace, this template shows this heading: In most other namespaces, such as "Wikisource:", it shows this heading:
But when on File (image) pages it shows this heading:
The heading parameter can be used to set the heading to something else. Like this:
If the heading parameter is empty but defined, no heading is shown and no [edit] [purge] links are shown. Like this:
The heading-style parameter can be fed optional CSS values. Without quotation marks
The link box[edit]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 You can also insert customised text in the link box, by defining the Automatic functions[edit]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}}. Subject namespaces vs. talk namespaces[edit]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
When placed on talk pages, this template usually is placed near the top of the page and without 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. Testing[edit]You can simulate the output for a given page by using the Technical details[edit]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. For more technical details see the talk page. See also[edit]
|
{{Documentation}} | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
{{Documentation|Template:Header/doc}} {{Documentation}}
This template can be preloaded via the Gadgets, alternatively, one can preload Template:Documentation/preload. {{header
| title =
| author =
| translator =
| section =
| previous =
| next =
| year =
| notes =
}}
This template is meant to be used at the top of a work[notes 1] in the main namespace and its subsections. Fill in any relevant information, and leave unknown or inapplicable parameters empty. For easy use, see also the header preloading script gadget in your preferences. Documentation[edit]Parameters[edit]Standard[edit]
Optional[edit]
All parameters[edit]{{header
| title =
| author =
| author-display =
| section =
| previous =
| next =
| notes =
<!-- optional from here -->
| year =
| edition =
| translator =
| translator-display =
| related-author =
| portal =
| contributor =
| editor =
| cover =
| shortcut =
<!-- modifying "year" behaviour; use one of -->
| noyear =
| noyearcat =
<!-- modifying sorting behaviour -->
| sortkey =
<!-- provided through wikidata, can be used to override wikidata -->
| wikipedia =
| commons =
| commonscat =
| wikiquote =
| wikinews =
| wiktionary =
| wikibooks =
| wikiversity =
| wikispecies =
| wikivoyage =
| meta =
}}
Relative links[edit]With lengthy, multi-page works, using relative links is highly recommended. This shortens the code and ensures that a work remains linked together even if it is moved or reorganised. The three formats are [[/subpage]] (subpage), [[../]] (parent), and [[../sibling]] (sibling)[1]; see the example usage below. Note that [[../]] will expand to the title of the parent page, which is ideal if the work is renamed at a later time. This depends on a page conforming to the page title standards in the Style guide, with works in the form [[Work title]] and [[Work title/Subpage]].
Chapter titles[edit]In general, include chapter titles in the "section" field, but avoid including them in the "previous" and "next" fields. For example: Example {{header
| title = [[../|The Book of Scottish Song]]
| author =
| editor = Alexander Whitelaw
| translator =
| section = Jock o' Hazeldean
| contributor = Walter Scott
| previous = [[../Sing on, sing on/]]
| next = [[../The Laird o' Cockpen/]]
| year = 1843
| notes =
}}
Usage examples[edit]Normal[edit]Example {{header
| title = [[../]]
| author = Lewis Carroll
| section = Chapter 3: A Caucus-Race and a Long Tale
| previous = [[../Chapter 2/]]
| next = [[../Chapter 4/]]
| notes =
}}
No author link[edit]Example {{header
| title = Peerage Act 1963
| author = the [[Portal:Parliament of the United Kingdom|Parliament of the United Kingdom]] | author-nolink = true
| section =
| previous =
| next =
| year = 1963 | noyear = true
| notes =
}}
Translation[edit]Example {{header
| title = Fables
| author = Jean de La Fontaine
| translator = Elizur Wright
| section =
| previous =
| next =
| notes =
}}
Example {{header
| title = Pantagruel
| author = François Rabelais
| translator1 = Thomas Urquhart
| translator2 = Peter Antony Motteux
| section-translator = unknown
| section = Example
| previous =
| next =
| notes =
}}
Categories[edit]| categories = 1st category / 2nd category Note: that use of this methodology excludes further editing by use of the HotCat tool, so this form should only be used where the categories are unlikely to need to be altered Sister, related author, and portal wiki links[edit]You can link to Wikisource portals and other WMF projects using the optional wiki links parameters where required to override the data provided from Wikidata. These are:
For portal this would generally be added to the root page of a work, rather than added repeatedly for each subpage. Usage on a subpage would be useful where the subpage alone has a relationship with the specified portal, whereas the parent work does not have that relationship. These links are generated using {{plain sister}} Example {{header
| title = Kinematics of Machinery
| author = Franz Reuleaux
| section =
| previous =
| next =
| notes =
| portal1 = Technology
| portal2 = Germany
| wikipedia = Kinematics of Machinery
| related-author = Albert Einstein
}}
Shortcuts[edit]If a work has a shortcut, you can add it using the shortcut field. This should be in accordance with the shortcut guidelines, and shortcuts should not be used for every work. Example {{header
| title = 1911 Encyclopædia Britannica
| author =
| section =
| previous =
| next =
| notes =
| shortcut = [[EB1911]]
}}
Advanced manipulation[edit]Alternative headers[edit]
JavaScript extraction[edit]The header values can be extracted using JavaScript by accessing the text values of their span wrappers:
Microformat[edit]The HTML markup produced by this template includes an hCard microformat, which makes the person's details parsable by computers, either acting automatically to catalogue articles across Wikipedia or via a browser tool operated by a reader, to (for example) add the subject to an address book or database. For more information about the use of microformats on Wikimedia projects, please see Wikipedia's microformat project. Sub-templates[edit]To include a URL, use {{URL}}. Please do not remove instances of these sub-templates. Classes[edit]hCard uses HTML classes including:
Please do not rename or remove these classes; nor collapse nested elements which use them. Technical[edit]This template delegates some logic to Lua modules and uses sub templates to divide up the structural code:
Tracking categories[edit]This template uses categories to track maintenance tasks, errors, and feature usage, which are grouped in Category:Header tracking categories. See also[edit]
Templates called by this template:
This template can be preloaded via the Gadgets, alternatively, one can preload Template:Documentation/preload. {{header
| title =
| author =
| translator =
| section =
| previous =
| next =
| year =
| notes =
}}
This template is meant to be used at the top of a work[notes 1] in the main namespace and its subsections. Fill in any relevant information, and leave unknown or inapplicable parameters empty. For easy use, see also the header preloading script gadget in your preferences. Documentation[edit]Parameters[edit]Standard[edit]
Optional[edit]
All parameters[edit]{{header
| title =
| author =
| author-display =
| section =
| previous =
| next =
| notes =
<!-- optional from here -->
| year =
| edition =
| translator =
| translator-display =
| related-author =
| portal =
| contributor =
| editor =
| cover =
| shortcut =
<!-- modifying "year" behaviour; use one of -->
| noyear =
| noyearcat =
<!-- modifying sorting behaviour -->
| sortkey =
<!-- provided through wikidata, can be used to override wikidata -->
| wikipedia =
| commons =
| commonscat =
| wikiquote =
| wikinews =
| wiktionary =
| wikibooks =
| wikiversity =
| wikispecies =
| wikivoyage =
| meta =
}}
Relative links[edit]With lengthy, multi-page works, using relative links is highly recommended. This shortens the code and ensures that a work remains linked together even if it is moved or reorganised. The three formats are [[/subpage]] (subpage), [[../]] (parent), and [[../sibling]] (sibling)[1]; see the example usage below. Note that [[../]] will expand to the title of the parent page, which is ideal if the work is renamed at a later time. This depends on a page conforming to the page title standards in the Style guide, with works in the form [[Work title]] and [[Work title/Subpage]].
Chapter titles[edit]In general, include chapter titles in the "section" field, but avoid including them in the "previous" and "next" fields. For example: Example {{header
| title = [[../|The Book of Scottish Song]]
| author =
| editor = Alexander Whitelaw
| translator =
| section = Jock o' Hazeldean
| contributor = Walter Scott
| previous = [[../Sing on, sing on/]]
| next = [[../The Laird o' Cockpen/]]
| year = 1843
| notes =
}}
Usage examples[edit]Normal[edit]Example {{header
| title = [[../]]
| author = Lewis Carroll
| section = Chapter 3: A Caucus-Race and a Long Tale
| previous = [[../Chapter 2/]]
| next = [[../Chapter 4/]]
| notes =
}}
No author link[edit]Example {{header
| title = Peerage Act 1963
| author = the [[Portal:Parliament of the United Kingdom|Parliament of the United Kingdom]] | author-nolink = true
| section =
| previous =
| next =
| year = 1963 | noyear = true
| notes =
}}
Translation[edit]Example {{header
| title = Fables
| author = Jean de La Fontaine
| translator = Elizur Wright
| section =
| previous =
| next =
| notes =
}}
Example {{header
| title = Pantagruel
| author = François Rabelais
| translator1 = Thomas Urquhart
| translator2 = Peter Antony Motteux
| section-translator = unknown
| section = Example
| previous =
| next =
| notes =
}}
Categories[edit]| categories = 1st category / 2nd category Note: that use of this methodology excludes further editing by use of the HotCat tool, so this form should only be used where the categories are unlikely to need to be altered Sister, related author, and portal wiki links[edit]You can link to Wikisource portals and other WMF projects using the optional wiki links parameters where required to override the data provided from Wikidata. These are:
For portal this would generally be added to the root page of a work, rather than added repeatedly for each subpage. Usage on a subpage would be useful where the subpage alone has a relationship with the specified portal, whereas the parent work does not have that relationship. These links are generated using {{plain sister}} Example {{header
| title = Kinematics of Machinery
| author = Franz Reuleaux
| section =
| previous =
| next =
| notes =
| portal1 = Technology
| portal2 = Germany
| wikipedia = Kinematics of Machinery
| related-author = Albert Einstein
}}
Shortcuts[edit]If a work has a shortcut, you can add it using the shortcut field. This should be in accordance with the shortcut guidelines, and shortcuts should not be used for every work. Example {{header
| title = 1911 Encyclopædia Britannica
| author =
| section =
| previous =
| next =
| notes =
| shortcut = [[EB1911]]
}}
Advanced manipulation[edit]Alternative headers[edit]
JavaScript extraction[edit]The header values can be extracted using JavaScript by accessing the text values of their span wrappers:
Microformat[edit]The HTML markup produced by this template includes an hCard microformat, which makes the person's details parsable by computers, either acting automatically to catalogue articles across Wikipedia or via a browser tool operated by a reader, to (for example) add the subject to an address book or database. For more information about the use of microformats on Wikimedia projects, please see Wikipedia's microformat project. Sub-templates[edit]To include a URL, use {{URL}}. Please do not remove instances of these sub-templates. Classes[edit]hCard uses HTML classes including:
Please do not rename or remove these classes; nor collapse nested elements which use them. Technical[edit]This template delegates some logic to Lua modules and uses sub templates to divide up the structural code:
Tracking categories[edit]This template uses categories to track maintenance tasks, errors, and feature usage, which are grouped in Category:Header tracking categories. See also[edit]
Templates called by this template:
|
{{Documentation}} |
---|
{{Documentation|content=Some documentation text.}} {{Documentation}} ![]() Some documentation text. ![]() Some documentation text. |
{{Documentation}} | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
{{Documentation |1=Template:Header/doc |content={{Template:Header/doc}} }} {{Documentation}}
This template can be preloaded via the Gadgets, alternatively, one can preload Template:Documentation/preload. {{header
| title =
| author =
| translator =
| section =
| previous =
| next =
| year =
| notes =
}}
This template is meant to be used at the top of a work[notes 1] in the main namespace and its subsections. Fill in any relevant information, and leave unknown or inapplicable parameters empty. For easy use, see also the header preloading script gadget in your preferences. Documentation[edit]Parameters[edit]Standard[edit]
Optional[edit]
All parameters[edit]{{header
| title =
| author =
| author-display =
| section =
| previous =
| next =
| notes =
<!-- optional from here -->
| year =
| edition =
| translator =
| translator-display =
| related-author =
| portal =
| contributor =
| editor =
| cover =
| shortcut =
<!-- modifying "year" behaviour; use one of -->
| noyear =
| noyearcat =
<!-- modifying sorting behaviour -->
| sortkey =
<!-- provided through wikidata, can be used to override wikidata -->
| wikipedia =
| commons =
| commonscat =
| wikiquote =
| wikinews =
| wiktionary =
| wikibooks =
| wikiversity =
| wikispecies =
| wikivoyage =
| meta =
}}
Relative links[edit]With lengthy, multi-page works, using relative links is highly recommended. This shortens the code and ensures that a work remains linked together even if it is moved or reorganised. The three formats are [[/subpage]] (subpage), [[../]] (parent), and [[../sibling]] (sibling)[1]; see the example usage below. Note that [[../]] will expand to the title of the parent page, which is ideal if the work is renamed at a later time. This depends on a page conforming to the page title standards in the Style guide, with works in the form [[Work title]] and [[Work title/Subpage]].
Chapter titles[edit]In general, include chapter titles in the "section" field, but avoid including them in the "previous" and "next" fields. For example: Example {{header
| title = [[../|The Book of Scottish Song]]
| author =
| editor = Alexander Whitelaw
| translator =
| section = Jock o' Hazeldean
| contributor = Walter Scott
| previous = [[../Sing on, sing on/]]
| next = [[../The Laird o' Cockpen/]]
| year = 1843
| notes =
}}
Usage examples[edit]Normal[edit]Example {{header
| title = [[../]]
| author = Lewis Carroll
| section = Chapter 3: A Caucus-Race and a Long Tale
| previous = [[../Chapter 2/]]
| next = [[../Chapter 4/]]
| notes =
}}
No author link[edit]Example {{header
| title = Peerage Act 1963
| author = the [[Portal:Parliament of the United Kingdom|Parliament of the United Kingdom]] | author-nolink = true
| section =
| previous =
| next =
| year = 1963 | noyear = true
| notes =
}}
Translation[edit]Example {{header
| title = Fables
| author = Jean de La Fontaine
| translator = Elizur Wright
| section =
| previous =
| next =
| notes =
}}
Example {{header
| title = Pantagruel
| author = François Rabelais
| translator1 = Thomas Urquhart
| translator2 = Peter Antony Motteux
| section-translator = unknown
| section = Example
| previous =
| next =
| notes =
}}
Categories[edit]| categories = 1st category / 2nd category Note: that use of this methodology excludes further editing by use of the HotCat tool, so this form should only be used where the categories are unlikely to need to be altered Sister, related author, and portal wiki links[edit]You can link to Wikisource portals and other WMF projects using the optional wiki links parameters where required to override the data provided from Wikidata. These are:
For portal this would generally be added to the root page of a work, rather than added repeatedly for each subpage. Usage on a subpage would be useful where the subpage alone has a relationship with the specified portal, whereas the parent work does not have that relationship. These links are generated using {{plain sister}} Example {{header
| title = Kinematics of Machinery
| author = Franz Reuleaux
| section =
| previous =
| next =
| notes =
| portal1 = Technology
| portal2 = Germany
| wikipedia = Kinematics of Machinery
| related-author = Albert Einstein
}}
Shortcuts[edit]If a work has a shortcut, you can add it using the shortcut field. This should be in accordance with the shortcut guidelines, and shortcuts should not be used for every work. Example {{header
| title = 1911 Encyclopædia Britannica
| author =
| section =
| previous =
| next =
| notes =
| shortcut = [[EB1911]]
}}
Advanced manipulation[edit]Alternative headers[edit]
JavaScript extraction[edit]The header values can be extracted using JavaScript by accessing the text values of their span wrappers:
Microformat[edit]The HTML markup produced by this template includes an hCard microformat, which makes the person's details parsable by computers, either acting automatically to catalogue articles across Wikipedia or via a browser tool operated by a reader, to (for example) add the subject to an address book or database. For more information about the use of microformats on Wikimedia projects, please see Wikipedia's microformat project. Sub-templates[edit]To include a URL, use {{URL}}. Please do not remove instances of these sub-templates. Classes[edit]hCard uses HTML classes including:
Please do not rename or remove these classes; nor collapse nested elements which use them. Technical[edit]This template delegates some logic to Lua modules and uses sub templates to divide up the structural code:
Tracking categories[edit]This template uses categories to track maintenance tasks, errors, and feature usage, which are grouped in Category:Header tracking categories. See also[edit]
Templates called by this template:
This template can be preloaded via the Gadgets, alternatively, one can preload Template:Documentation/preload. {{header
| title =
| author =
| translator =
| section =
| previous =
| next =
| year =
| notes =
}}
This template is meant to be used at the top of a work[notes 1] in the main namespace and its subsections. Fill in any relevant information, and leave unknown or inapplicable parameters empty. For easy use, see also the header preloading script gadget in your preferences. Documentation[edit]Parameters[edit]Standard[edit]
Optional[edit]
All parameters[edit]{{header
| title =
| author =
| author-display =
| section =
| previous =
| next =
| notes =
<!-- optional from here -->
| year =
| edition =
| translator =
| translator-display =
| related-author =
| portal =
| contributor =
| editor =
| cover =
| shortcut =
<!-- modifying "year" behaviour; use one of -->
| noyear =
| noyearcat =
<!-- modifying sorting behaviour -->
| sortkey =
<!-- provided through wikidata, can be used to override wikidata -->
| wikipedia =
| commons =
| commonscat =
| wikiquote =
| wikinews =
| wiktionary =
| wikibooks =
| wikiversity =
| wikispecies =
| wikivoyage =
| meta =
}}
Relative links[edit]With lengthy, multi-page works, using relative links is highly recommended. This shortens the code and ensures that a work remains linked together even if it is moved or reorganised. The three formats are [[/subpage]] (subpage), [[../]] (parent), and [[../sibling]] (sibling)[1]; see the example usage below. Note that [[../]] will expand to the title of the parent page, which is ideal if the work is renamed at a later time. This depends on a page conforming to the page title standards in the Style guide, with works in the form [[Work title]] and [[Work title/Subpage]].
Chapter titles[edit]In general, include chapter titles in the "section" field, but avoid including them in the "previous" and "next" fields. For example: Example {{header
| title = [[../|The Book of Scottish Song]]
| author =
| editor = Alexander Whitelaw
| translator =
| section = Jock o' Hazeldean
| contributor = Walter Scott
| previous = [[../Sing on, sing on/]]
| next = [[../The Laird o' Cockpen/]]
| year = 1843
| notes =
}}
Usage examples[edit]Normal[edit]Example {{header
| title = [[../]]
| author = Lewis Carroll
| section = Chapter 3: A Caucus-Race and a Long Tale
| previous = [[../Chapter 2/]]
| next = [[../Chapter 4/]]
| notes =
}}
No author link[edit]Example {{header
| title = Peerage Act 1963
| author = the [[Portal:Parliament of the United Kingdom|Parliament of the United Kingdom]] | author-nolink = true
| section =
| previous =
| next =
| year = 1963 | noyear = true
| notes =
}}
Translation[edit]Example {{header
| title = Fables
| author = Jean de La Fontaine
| translator = Elizur Wright
| section =
| previous =
| next =
| notes =
}}
Example {{header
| title = Pantagruel
| author = François Rabelais
| translator1 = Thomas Urquhart
| translator2 = Peter Antony Motteux
| section-translator = unknown
| section = Example
| previous =
| next =
| notes =
}}
Categories[edit]| categories = 1st category / 2nd category Note: that use of this methodology excludes further editing by use of the HotCat tool, so this form should only be used where the categories are unlikely to need to be altered Sister, related author, and portal wiki links[edit]You can link to Wikisource portals and other WMF projects using the optional wiki links parameters where required to override the data provided from Wikidata. These are:
For portal this would generally be added to the root page of a work, rather than added repeatedly for each subpage. Usage on a subpage would be useful where the subpage alone has a relationship with the specified portal, whereas the parent work does not have that relationship. These links are generated using {{plain sister}} Example {{header
| title = Kinematics of Machinery
| author = Franz Reuleaux
| section =
| previous =
| next =
| notes =
| portal1 = Technology
| portal2 = Germany
| wikipedia = Kinematics of Machinery
| related-author = Albert Einstein
}}
Shortcuts[edit]If a work has a shortcut, you can add it using the shortcut field. This should be in accordance with the shortcut guidelines, and shortcuts should not be used for every work. Example {{header
| title = 1911 Encyclopædia Britannica
| author =
| section =
| previous =
| next =
| notes =
| shortcut = [[EB1911]]
}}
Advanced manipulation[edit]Alternative headers[edit]
JavaScript extraction[edit]The header values can be extracted using JavaScript by accessing the text values of their span wrappers:
Microformat[edit]The HTML markup produced by this template includes an hCard microformat, which makes the person's details parsable by computers, either acting automatically to catalogue articles across Wikipedia or via a browser tool operated by a reader, to (for example) add the subject to an address book or database. For more information about the use of microformats on Wikimedia projects, please see Wikipedia's microformat project. Sub-templates[edit]To include a URL, use {{URL}}. Please do not remove instances of these sub-templates. Classes[edit]hCard uses HTML classes including:
Please do not rename or remove these classes; nor collapse nested elements which use them. Technical[edit]This template delegates some logic to Lua modules and uses sub templates to divide up the structural code:
Tracking categories[edit]This template uses categories to track maintenance tasks, errors, and feature usage, which are grouped in Category:Header tracking categories. See also[edit]
Templates called by this template:
|