Template:Split portions/doc
| This is a documentation subpage for Template:Split portions. It may contain usage information, categories and other content that is not part of the original template page. |
__EXPECTED_UNCONNECTED_PAGE__
{{Wikipedia:Article alerts/Bot use warning}} This template is for splitting out content that may be integrated throughout an article (or other page), or a section thereof, but which would be more relevant as a separate page (or multiple pages), and should be relocated there, leaving the relevant content in the original page.
This template is useful especially when at least one of the proposed split-to titles does not yet exist as an page. It is also only used when the content is diffuse or partial and does not form entire identifiable sections. The exact nature of the split is usually detailed in a proposal on the talk page of the page proposed for splitting.
Usage
To propose splitting content from one page out to another page or pages:
- At the top of the page to split the content from, put
{{Split portions|date=October 2026 |Title to which to relocate the content}}. - If there is more than one suggested title to which to relocate the content, include each:
{{Split portions|date=October 2026 |First target title |Second target title}}. Up to 20 articles (already existing or not) can be specified. - This template is mostly used to suggest splits to new pages. If any of the suggested target pages already exists, then at the top of it put
{{Merge portions from|date=October 2026 |Title of article to split the content from}}.
- See also the
|portion=and|discuss=parameters.
You are encouraged to be specific: The |portion= (or |portions=) parameter allows you to replace the word "portions" with something more specific. Examples:
{{Split portions|portion=the material about book/comic and film/TV characters |date=October 2026 |List of fictional hedgehogs}}.{{Split portions|portions=the details about specific Gothic peoples |date=October 2026 |Art of the Visigoths |Art of the Ostrogoths}}
The parameter |small=y will reduce the size of the template to a left-hand box instead of a banner.
This template will add articles (but not other pages) to Category:All articles proposed for splitting and the proper dated subcategory of Category:Articles proposed for splitting.
For sections only
If portions of one section need to be split out, use {{Split portions}} at the top of that section, and use the |section=y parameter: {{Split portions|section=y |date=October 2026 |Title to which to relocate the content}}. This will change the wording to "portions of this section". This can be done at two or more places in the article to suggest multiple specific splits, instead of a more vague multi-split template at the top of the article.
It has been suggested that portions of this section be split out into another page titled Title to which to relocate the content. (Discuss) (November 2015) |
If portions of several subsections of a single section need to relocate, leaving the rest of the section in place, you can put the template at the top of that section, and use the |subsections=y parameter (or |section=y|sections=y, which has the same effect): {{Split portions|subsections=y |date=October 2026 |Title to which to relocate the content}}. This will change the wording to "subsections of this section". However, if will probably be more helpful to use |section=, and use a separate template in each of the subsections proposed for splitting.
It has been suggested that subsections of this section be split out into another page titled Title to which to relocate the content. (Discuss) (November 2015) |
If a whole section needs to be split, to only one new page, you can use {{Split section}} instead, at the top of the section: {{Split section|date=October 2026 |Title to which to relocate the content}}. This template only supports one target title parameter.
It has been suggested that this section be split out into another page titled Title to which to relocate the content. (Discuss) (November 2015) |
If a proposed section split (whole or partial) is to more than one page, use: {{Split portions|portion=this section |date=October 2026 |First title to which to relocate the content |Second title to which to relocate the content}}
It has been suggested that this section be split out into pages titled First title to which to relocate the content and Second title to which to relocate the content. (Discuss) (November 2015) |
If multiple sections or portions thereof need to be split out, you can put the template at the top of the page, and use the |sections=y parameter: {{Split portions|sections=y |date=October 2026 |Title to which to relocate the content}}. This will change the wording to "sections of this article" (or "sections of this page", in other namespaces).
It has been suggested that sections of this page be split out into another page titled Title to which to relocate the content. (Discuss) (November 2015) |
This is usually the least desirable option because of its vagueness, and it will probably be more helpful to tag each of the subsections proposed for splitting, with either {{Split portions|section (partial) or
|...}}{{Split section|...}} (whole section).
The |sections= and |subsections= options will, when used in mainspace, also categorize the split-from article into the proper dated subcategory of Category:Article sections proposed for splitting.
Merging into existing pages
To propose splitting/merging an entire section from one page into another, one would normally use {{Merge from|section=y}} and {{Merge to|section=y}}. To propose merging an entire page into another, use {{Merge to}} and {{Merge from}}.
If several sections in the current article need to move to one or more other articles, at least one of which already exists, then using separate {{Merge to}} tags would often be visually disruptive to the article. Instead, the |existing= parameter of this template can be used, with |sections=:
{{Split portions|existing=y|portions=sections "Foo", "Bar", and "Baz"|Article Foo|Article Bar|Article Baz}}
It has been suggested that sections "Foo", "Bar", and "Baz" be split out and merged as needed into pages titled Article Foo, Article Bar and Article Baz, one or more of which already exist. (Discuss) |
{{Split portions|existing=y|portions=sections about Foo|Article Foo}}
It has been suggested that sections about Foo be split out and merged into the page titled Article Foo, which already exists. (Discuss) |
On the target article, you can also tag it with {{Merge portions from}}:
{{Merge portions from|Article Bar|section "Foo"}}
| It has been suggested that portions of Article Bar (section "Foo") be split out from it and merged into this page. (Discuss) |
TemplateData
TemplateData for Split portions
Use this template to suggest that portions of this article be split out into another article.
| Parameter | Description | Type | Status | |
|---|---|---|---|---|
| Month and year | date | The month and year that the template was placed (in full). "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" inserts the current month and year automatically.
| Line | suggested |
| First new page title | 1 | no description | String | required |
| Second new page title | 2 | no description | String | suggested |
| Third new page title | 3 | no description | String | optional |
| Fourth new page title | 4 | no description | String | optional |
| Fifth new page title | 5 | no description | String | optional |
| Sixth new page title | 6 | no description | String | optional |
| Seventh new page title | 7 | no description | String | optional |
| Eighth new page title | 8 | no description | String | optional |
| Ninth new page title | 9 | no description | String | optional |
| Tenth new page title | 10 | no description | String | optional |
| Eleventh new page title | 11 | no description | String | optional |
| Twelfth new page title | 12 | no description | String | optional |
| Thirteenth new page title | 13 | no description | String | optional |
| Fourteenth new page title | 14 | no description | String | optional |
| Fifteenth new page title | 15 | no description | String | optional |
| Sixteenth new page title | 16 | no description | String | optional |
| Seventeenth new page title | 17 | no description | String | optional |
| Eighteenth new page title | 18 | no description | String | optional |
| Nineteenth new page title | 19 | no description | String | optional |
| Twentieth new page title | 20 | no description | String | optional |
| Talk page discussion | discuss | Talk page and section where the split discussion is taking place
| Page name | suggested |
| Sections, not portions? | sections | Enter any text here to replace the word "portions" with "sections". If "Section, not article?" is also enabled, this will become "subsections".
| Line | optional |
| Section, not article? | section | Enter any text here to replace the word "article" with "section". If "Sections, not portions?" is also enabled, "sections" will become "subsections".
| Line | optional |
| Subsections of a section? | subsections | Enter any text here to replace "portions of this article" with "subsections of this section".
| Line | optional |
| Text to replace "portions" | portions portion | Custom text to replace "portions" in the template
| String | optional |
| Page already exists? | existing | Enter any text here to indicate that one or more of the proposed articles already exists.
| Line | optional |
| Make template small | small | Enter any text here to make the template box small and aligned to the left.
| Line | optional |
{{Wikipedia:Template messages/Splitting/List|noheading=yes}}{{Wikipedia:Template messages/Merging/List|noheading=yes}}
Article splitting templates |
|---|
- Template:Split portions invokes Module:Navbox using Lua.
Usage
This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.
The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.
Syntax
{{navbox
|state = uncollapsed, collapsed, plain, autocollapse (default)
|name = mandatory - name of the template
|style = optional - style for the whole table
|title = mandatory - navbox header
|gtitleN = optional - title of N-th group of items
|styleN = optional - style for groupN; i.e. text-align
|groupN = mandatory - list of groups of items
|fstyle = optional - style for footer ; i.e. text-align
|footer = optional - navbox footer
}}
- Groups: Currently there is no technical limit to the maximum number of groups.
- Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
- Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
- Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
- Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
- Line breaks: Line-breaks (
<br />) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN. - Bullets: Create unordered lists with lines beginning with *.
- Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! (
{{!}}).
States
- Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
- Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
- Uncollapsed: Forces the navbox to be displayed.
- All of the navboxes in this documentation are in the uncollapsed state.
- Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
- Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
- Plain: Removes the "show/hide" link.
Sub-groups
- For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
- To create sub-groups within
{{navbox}}, certain parameters are to be included:- The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
- The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.
{{navbox
|name =
|title =
|gtitle1 =
|group1 =
|gtitle2 =
|gtype2 = Subgroup (mandatory)
|group2 =
{{navbox
|subgroup = yes (mandatory)
|gtitle1 =
|group1 =
|gtitle2 =
|group2 =
}}
}}
Collapsible sub-groups
- For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
- To create collapsible sub-groups within
{{navbox}}, these parameters need to be included:- The parent navbox is almost always uncollapsed (state=uncollapsed).
- The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
- The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
- The nested collapsible navbox is forcefully collapsed (state=collapsed).
{{navbox
|state = uncollapsed
|name =
|gtype1 = Subgroup
|group1 =
{{navbox
|collapsible = yes
|state = collapsed
|title =
|gtitle1 =
|group1 =
|gtitle2 =
|group2 =
}}
}}
Use of images
- The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
- Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.
Link and file share the same name
{{plink|Item}}
File name differs from the link
{{plink|Item|File}}
Link and file share the same name, but different text is desired to display
{{plink|Item|alt=Text}}
File name differs from the link and different text is desired to display
{{plink|Item|File|alt=Text}}
Categorising
Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.
There are 2 methods of categorising pages with navboxes:
The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.
Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.
Examples
To see the following navboxes in action, see Template:Navbox.
Single line navbox with centered list
{{navbox
|name =
|title =
|style1 = text-align:center
|group1 =
}}
Navbox with standard footer
{{navbox
|name =
|title =
|gtitle1 =
|group1 =
|footer = Centered footer
}}
Navbox with styled footer
{{navbox
|name =
|title =
|gtitle1 =
|group1 =
|fstyle = text-align:right
|footer = Right-aligned footer
}}
Multiple line navbox
{{navbox
|name =
|title =
|gtitle1 = Group title 1
|group1 =
|gtitle2 = Group title 2
|group2 =
|gtitle3 = Group title 3
|group3 =
}}
Collapsed navbox
{{navbox
|state = collapsed
|name =
|title =
|style1 = text-align:center
|group1 =
}}
Plain navbox with Tnavbar
{{navbox
|state = plain
|name =
|title =
|style1 = text-align:center
|group1 =
}}
Plain navbox without Tnavbar
{{navbox
|state = plain
|title =
|style1 = text-align:center
|group1 =
}}
Complicated navbox
{{navbox
|state = uncollapsed
|name =
|title =
|gtitle1 = Level 1 Title 1
|group1 =
|gtitle2 = Level 1 Title 2
|group2 =
|gtitle3 = Level 1 Title 3
|group3 =
|gtitle4 = Level 1 Title 4
|group4 =
|gtitle5 = Level 1 Title 5
|gtype5 = Subgroup
|group5 =
{{navbox
|subgroup = Yes
|gtitle1 = Level 2 Title 1
|group1 =
|gtitle2 = Level 2 Title 2
|group2 =
|gtitle3 = Level 2 Title 3
|gtype3 = Subgroup
|group3 =
{{navbox
|subgroup = Yes
|gtitle1 = Level 3 Title 1
|group1 =
|gtitle2 = Level 3 Title 2
|group2 =
}}
|gtitle4 = Level 2 Title 4
|group4 =
}}
|gtitle6 = Level 1 Title 6
|group6 =
|gtitle7 = Level 1 Title 7
|group7 =
|fstyle =
|footer =
}}
Preventing unwanted documentation
The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).
Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.