Template:Campaignbox
 | This template is used on approximately 24,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
 | This template uses Lua: |
 | This template does not display in the mobile view of Wikipedia; it is desktop only. Read the documentation for an explanation. |
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed on the mobile web site of English Wikipedia. Mobile page views account for approximately 66% of all page views (90-day average as of January 2024[update]).
Usage
Campaignboxes
One common type of navigational template in articles concerning conflicts, wars and related topics is the campaignbox template, intended to provide context and convenient navigation among articles on the battles in a campaign, front, theater or war (or, more rarely, among several campaigns or wars).
If the article includes an infobox, the campaignbox/es are usually placed immediately after it (i.e. just below it). If available, as with infoboxes such as {{Infobox military conflict}}, use the infobox's |campaignbox= parameter:
{{Infobox military conflict
...
}}
{{Campaignbox XXXX}}
{{Infobox military conflict
...
| campaignbox = {{campaignbox XXXX}}
}}
Articles may include multiple campaignboxes; typically, these are stacked under the infobox. The most common scenario occurs when two levels of campaignboxes are present – for example, an article about a battle can include both a campaignbox listing the battle itself and an "enclosing" campaignbox listing the campaign, theater or war during which the battle took place. Similarly, an article about a war can include both a campaignbox listing the war (among a series of wars) and a campaignbox for the war itself, listing the battles that took place during it.
Creating campaignboxes
Existing campaignboxes may be viewed through the Campaignbox template category to which campaignboxes are added automatically. If a new campaignbox becomes necessary, it should be named Template:Campaignbox XXXX (where XXXX is the (shortened) name of the campaign) and should use {{Campaignbox}} thus:
{{Campaignbox
| name =
| title =
| battles =
| notes =
}}
Parameters
- name
- The name by which Wikipedia refers to the template, i.e. "Template:Campaignbox XXXX". This can be produced by using
{{subst:PAGENAME}}. - title
- The name of the campaign or war, which, if an article about the campaign or war exists, should link to it. Dates should not be indicated unless needed for clarity. Note that long links may cause alignment problems; see the troubleshooting guide for more information.
- battles
- A chronological list of battles and operations in the campaign, linked as
[[Battle of YYYY|YYYY]]. A convenient and accessible way to separate the items in the list is to add| listclass = hlistand then use the standard * (asterisk)-based listing format. - notes
- (optional) Any explanatory notes needed to clarify the list. This option should be used sparingly.
- (raw_name)
- (optional; deprecated) This parameter overrides the use of the title in determining the template name and exists for the sake of backward compatibility. When creating a new campaignbox, both title and name should be specified as above and this parameter omitted.
The following optional parameters are passed on to the templates {{Military navigation}} or {{Navbox}} used to create campaignboxes and so can affect their styling. See these two templates' documentation pages for further details.
- state
- To set whether the campaignbox appears fully visible or collapsed (to titlebar only) when it is first presented by a page.
- bodyclass
- CSS styling to affect the whole template.
- listclass
- CSS styling to affect the list of battles, operations, etc. (e.g. to affect
|battles=).
The use of special formatting (such as bolding or changes in font size) in the list of battles – particularly to mark battles as "important" – is generally discouraged; while there are a few cases where such approaches may be both helpful to the reader and sufficiently well-sourced that they do not constitute original research, they are usually both unnecessary and potentially confusing. Similarly, dividing the list of battles into multiple blocks by inserting heading-like separations should be exceptional; if such a division is felt to be needed, a better solution may be to split the one campaignbox into two or more.