Wikipedia:WikiProject Military history: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
→‎Participants: Added myself
Line 34: Line 34:
* [[User:Halibutt|Halibu]][[User Talk:Halibutt|tt]] (mostly 20th century battles in Poland and Central Europe)
* [[User:Halibutt|Halibu]][[User Talk:Halibutt|tt]] (mostly 20th century battles in Poland and Central Europe)
* [[User:Brian0918|brian0918]][[User talk:Brian0918|™]] (American Civil War: Battleboxes, Categories, etc.)
* [[User:Brian0918|brian0918]][[User talk:Brian0918|™]] (American Civil War: Battleboxes, Categories, etc.)
* [[User:Kirill Lokshin|Kirill Lokshin]] (15th - 18th century Europe, general organization)


==Article title==
==Article title==

Revision as of 00:49, 5 September 2005

(this page is about a project on historic battles, not about disagreements and edit wars on Wikiprojects)

First, an important note for everyone to remember:

A few Wikipedians have gotten together to make some suggestions about how we might organize data in articles about Battles. These are only suggestions, things to give you focus and to get you going, and you shouldn't feel obligated in the least to follow them. But if you don't know what to write or where to begin, following the below guidelines may be helpful. Mainly, we just want you to write articles!


Title

WikiProject Battles

Scope

This WikiProject aims primarily to provide a standardized format to describe battles.

Parentage

The parents of this WikiProject are the WikiProject History and the WikiProject Military.

Descendant Wikiprojects

Similar Wikiprojects

The similar WikiProjects are WikiProject Wars and WikiProject Timelines.

Participants

Article title

Articles should be called something like Battle of Gettysburg. "Battle" is a neutral term and is preferred to "attack", "slaughter", "massacre", "raid", etc. But other names can be used if they are the most common ways to refer to the battle. So Attack on Pearl Harbor and Doolittle Raid are acceptable.

If disambiguation is needed, add the year in parentheses, for example Battle of Salamis in Cyprus (306 BC). Two battles at the same place in the same year should be called "First", "Second", etc, for example First Battle of Zurich, Second Battle of Zurich. But if the two battles are very close in time they are probably best described in a single article, for example the article Battle of Algeciras describes two battles sometimes called the "First" and "Second" Battles of Algeciras.

Try not to name the article after an operational codename: the codename doesn't give any indication of when or where the battle took place, sometimes doesn't correspond very well to what actually happened, and it represents only one side's planning, so it may lead the article to focus on that side's point of view to the detriment of the other. It is better to give a geographical name, and either redirect from the operation, or write a short article about the operation that links to the main article about the battle. This can be ignored for the most well-known operations, for example Operation Barbarossa, but note that even Operation Overlord redirects to Battle of Normandy.

Structure and format

The opening paragraph should concisely convey:

  1. The name of the battle
  2. Its date
  3. Its location (if not obvious from its name)
  4. Which war it belongs to
  5. Who were the combatants
  6. Something about its outcome or significance

The article should be structured along these lines:

  1. The background. Why did it take place? Which campaign did it belong to? What happened previously?
  2. The prelude. What forces were involved? How did they arrive at the battleground? Was there a plan?
  3. A description of the battle. What tactics were used?
  4. The aftermath. Who won, if anyone? What were the casualties? Was there a pursuit or followup? What happened next? How did the battle affect the course of the war?

Unless the article is long, there is no need to make separate sections. See Battle of the Downs for a short article using this structure and Battle of Zama for a longer one.

For major battles you may also wish to add a "battlebox" presenting information about the battle in table format. See below.

Categories

The sub-categories of Category:Battles should contain all of Wikipedia's articles about battles. The sub-lists of List of battles should contain all major battles in history, whether there is an article in Wikipedia or not.

In the simplest case, an isolated battle belongs to Category:Battles directly. In this case, you'll need to add other relevant categories such as war or history categories to the article about the battle.

Category:Battles    Category:English wars
        |                    |
        `---------+----------'
                  |
             Battle of Hastings

(But Category:English wars didn't exist, then Category:Military history of England would be the best place; and if that didn't exist either, Category:History of England would be best.)

A wars with several battles should have a sub-category for its battles. The category should be named "Battles of X" or "Battles of the X" where X is the name of the war (ideally, X should also be the name of the article describing the war). In this case the sub-category belongs to the history categories. This avoid clutter in the history and battle categories.

Category:Battles    Category:English wars    Category:French wars
       |                       |                          |
       `-----------------------+--------------------------'
                               |
                 Category:Battles of the Hundred Years' War
                               |
                      Battle of Agincourt

Significant wars should have their own category (articles other than battles go directly into the category for the war). In this case the sub-category for the war belongs to the history categories. For example:

Category:Battles    Category:Napoleonic wars
       |                      |     |
       `----------+-----------'     `--------------------.
                  |                                      |
    Category:Battles of the Napoleonic Wars      Napoleon I of France
                  |
            Battle of Waterloo

Sieges and naval battles should be categorized by type, for example:

                   Category:Battles            Category:American Civil War
                     |      |                               |
       .-------------'      `----------------+--------------'
       |                                     |
Category:Sieges           Category:Battles of the American Civil War
       |                                     |
       `------------------+------------------'
                          |
                  Siege of Petersburg

The largest wars should be categorized by theatre or campaign and (for naval battles) by type:

                    Category:Battles          Category:World War II
                        |      |                      |
          .-------------'      `--------+-------------'
          |                             |
Category:Naval battles      Category:World War II operations and battles
          |                         |       |
          `-----------+-------------'       `---------.
                      |                               |
Category:Naval battles of World War II    Category:World War II operations and battles of the Pacific Campaign
                      |                                  |
                      `------------------+---------------'
                                         |
                                  Battle of Midway

(Note that some of the World War II categories have names that don't fit the scheme.)

See Wikipedia:WikiProject Wars and Wikipedia:WikiProject History for further advice about categorization.

Discussion forums

Templates

Battle articles can use a Wikipedia:Infobox (known as a battlebox in this WikiProject) to summarise pertinent information about the battle. A battlebox is not compulsory. The preferred battlebox template is Template:Battlebox (described below).

Battle infobox

Usage

Battle of Lützen
Part of the Thirty Years' War
Battle of Lutzen by Carl Whalbom depicting King Gustavus Aolphus falling from a horse mortally wounded in a melee
The Battle of Lützen by Carl Wahlbom shows the death of King Gustavus Adolphus on 16 November 1632.
Date6 November (O.S.) or 16 November (N.S.), 1632
Location
Near Lützen, southwest of Leipzig
(present-day Germany)
51°15′N 12°08′E / 51.250°N 12.133°E / 51.250; 12.133
Result Protestant victory
(see Aftermath section)
Belligerents
Sweden Sweden
Protestant Union
 Holy Roman Empire
Catholic League
Commanders and leaders
Sweden Gustavus Adolphus 
Sweden Dodo von Knyphausen
Electorate of Saxony Bernhard of Saxe-Weimar
Sweden Robert Munro, 18th Baron of Foulis
Holy Roman Empire Albrecht von Wallenstein
Holy Roman Empire Heinrich Holk
Holy Roman Empire Count Gottfried zu Pappenheim (DOW)
Strength
12,800 infantry
6,200 cavalry
60 guns
10,000 infantry
7,000 cavalry, plus 3,000 infantry and 2,000 cavalry on arrival
24 guns
Casualties and losses
3,400 dead and 1,600 wounded or missing Probably about the same as Swedish casualties[1]

A military conflict infobox (sometimes referred to as a warbox) may be used to summarize information about a particular military conflict (a battle, campaign, war, or group of related wars) in a standard manner.

Information summarized in an infobox should follow the general guidance for writing a lead section. It should not "make claims" or present material not covered by the article. As with a lead section, there is some discretion in citing information in an infobox. The same guidance should be applied to an infobox as given for citations in a lead section. Information in an infobox must conform with verifiability, point-of-view and other policies.

Information in the infobox should not be "controversial". Refer the reader to an appropriate section in the article or leave the parameter blank rather than make an unsubstantiated or doubtful claim.

The infobox should be added using the {{infobox military conflict}} template, as shown below:

{{Infobox military conflict
| conflict    = 
| width       = 
| partof      = 
| image       = 
| image_size  =
| alt         =
| caption     = 
| date        = 
| place       = 
| coordinates = <!--Use the {{coord}} template -->
| map_type    = 
| map_relief  = 
| map_size    = 
| map_marksize = 
| map_caption = 
| map_label   = 
| territory   = 
| result      = 
| status      = 
| combatants_header = 
| combatant1  = 
| combatant2  = 
| combatant3  = 
| commander1  = 
| commander2  = 
| commander3  = 
| units1      = 
| units2      = 
| units3      = 
| strength1   = 
| strength2   = 
| strength3   = 
| casualties1 = 
| casualties2 = 
| casualties3 = 
| notes       = 
| campaignbox = 
}}

Note: When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". All subjective or qualitative judgements and numerical quantities or statistics must be cited to a reliable source (see WP:MILMOS#CITE).

Parameters

  • conflict – the name of the conflict being described (e.g. "Battle of Lützen" or "World War I").
  • widthoptional – the width of the infobox, e.g. "400px"; defaults to: "315px".
  • partofoptional – the larger conflict containing the event described in the article. For battles or campaigns, this should be the war during which the event takes place; for particularly large wars, this may include a theatre (e.g. "the Eastern Front of World War II"). For wars, the parameter may be used to link to a larger group of wars (e.g. the Italian War of 1521–26 to the Italian Wars). It may be necessary to insert "the" before the name of the war for proper grammar.
  • imageoptional – an image for the warbox. Given in the form Example.jpg
  • image_sizeoptional – a size for the image
  • altoptionalAlternative text for image that is accessible to screen readers to help the visually impaired
  • captionoptional – the text to be placed below the image.
  • dateoptional – the date of the conflict described. Convention is to give the actual date for battles and the years for wars, but this does not always apply.
  • place – the location of the conflict. For conflicts covering a wide area, a general description (e.g. "France", or "Europe", or "Worldwide") may be used.
  • coordinatesoptional – the location of the structure, given as a coordinate pair by using {{coord}} with display=inline,title. Used to display the geographic location of the conflict and the location on a map added with the map_type parameter.
  • map_typeoptional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
  • map_reliefoptional – "yes" if the location map is a relief map; see {{location map}} for more details.
  • map_sizeoptional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
  • map_markoptional – the name of a file to use as the location map marker, e.g. Green_pog.svg; defaults to: "Red_pog.svg".
  • map_marksizeoptional – width of the location map marker in pixels (px), e.g. "10"; defaults to: "8".
  • map_captionoptional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
  • map_labeloptional – the label placed next to the marker on the location map.
  • territoryoptional – any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement.
  • actionoptional – In case of Coup d'État, short description of modus operandi, e.g. "...marched over the city...", "...dissolving the Congress of the Republic...", "...take the government hostage ...", "...put the country under military control ...", etc.
  • resultoptional – this parameter may use one of two standard terms: "X victory" or "Inconclusive". The term used is for the "immediate" outcome of the "subject" conflict and should reflect what the sources say. In cases where the standard terms do not accurately describe the outcome, a link or note should be made to the section of the article where the result is discussed in detail (such as "See the Aftermath section"). Such a note can also be used in conjunction with the standard terms but should not be used to conceal an ambiguity in the "immediate" result. Do not introduce non-standard terms like "decisive", "marginal" or "tactical", or contradictory statements like "decisive tactical victory but strategic defeat". Omit this parameter altogether rather than engage in speculation about which side won or by how much.
  • statusoptional – for ongoing conflicts, the current status of the conflict. This should not be used if a final result (above) is provided.
  • combatants_headeroptional – sets the header text for the combatants section. Default is "Belligerents". In case of Coup d'État, use "Government-Insurgents   "
  • combatant1/combatant2/combatant3optional – the parties participating in the conflict. This is most commonly the countries whose forces took part in the conflict; however, larger groups (such as alliances or international organizations) or smaller ones (such as particular units, formations, or groups) may be indicated if doing so improves reader understanding. When there is a large number of participants, it may be better to list only the three or four major groups on each side of the conflict, and to describe the rest in the body of the article. The combatant3 field may be used if a conflict has three distinct "sides", and should be left blank on other articles. Combatants should be listed in order of importance to the conflict, be it in terms of military contribution, political clout, or a recognized chain of command. If differing metrics can support alternative lists, then ordering is left to the editors of the particular article. The practice of writing in a "Supported by" subheading is deprecated (see discussion).
    • combatant1a/combatant2a/combatant3aoptional – in cases where the parties significantly changed over the course of the conflict, these subsidiary fields may be used to provide additional rows for the combatantN fields (above).
    • combatant1b/combatant2b/combatant3boptional – additional row, as above.
    • combatant1c/combatant2c/combatant3coptional – additional row, as above.
    • combatant1d/combatant2d/combatant3doptional – additional row, as above.
    • combatant1e/combatant2e/combatant3eoptional – additional row, as above.
  • commander1/commander2/commander3optional – the commanders of the military forces involved. For battles, this should include military commanders (and other officers as necessary). For wars, only prominent or notable leaders should be listed, with an upper limit of about seven per combatant column recommended. Ranks and position titles should be omitted. The {{KIA}} and {{POW}} templates may be included immediately after the names of commanders who were killed in action or surrendered and were taken prisoner, respectively. The commander3 field can only be used if the combatant3 field is set.
    • commander1a/commander2a/commander3aoptional – in cases where the commanders significantly changed over the course of the conflict, these subsidiary fields may be used to provide additional rows for the commanderN fields (above).
    • commander1b/commander2b/commander3boptional – additional row, as above.
    • commander1c/commander2c/commander3coptional – additional row, as above.
    • commander1d/commander2d/commander3doptional – additional row, as above.
    • commander1e/commander2e/commander3eoptional – additional row, as above.
  • units1/units2/units3optional – the units or formations involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field. The units3 field can only be used if the combatant3 field is set.
  • strength1/strength2optional – the numerical strength of the units involved.
  • polstrength1/polstrength2optional – In case of Coup d'Etat, political organizations that supported the government (1) respective the insurgents (2).
  • milstrength1/milstrength2optional – In case of Coup d'Etat, military units that supported the government (1) respective the insurgents (2).
  • strength3optional – if combatant3 is set, this is a third strength field identical to the two above; if it is not set, this is an alternate combined field for use where only the total participation in a conflict is known.
  • casualties1/casualties2optionalcasualties suffered (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Note that this section of the infobox is headed "Casualties and losses". Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc.
  • casualties3optional – if combatant3 is set, this is a third casualty field identical to the two above; if it is not set, this is an alternate combined field for use where only the total casualties of a conflict are known, or where civilian casualties cannot be directly attributed to either side.
  • notesoptional – optional field for further notes; this should only be used in exceptional circumstances.
  • campaignboxoptional – optional field for appending a campaignbox template to the bottom of the infobox, which allows both boxes to float as a single element (useful if there are subsequent left floating images, which would otherwise not be able to float above the campaign box); the template must be specified in the format {{Campaignbox XYZ}}.

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}}
or
{{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 = hlist and 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.

This infobox may be used to describe a particular planned or executed military operation or attack. For operations that resulted in combat, it can be used as an auxiliary template to the {{infobox military conflict}}, if necessary; for other types of operations, including those that were planned but never executed, it may be used alone. In the case of conflicts that consisted of multiple independent operations, multiple copies of the box may be used on a single article.


Usage

{{{title}}}
Part of {{{conflict}}}
[[File:{{{image}}}|{{{image_size}}}|alt={{{alt}}}|upright={{{image_upright}}}]]
{{{caption}}}
Operational scope{{{scope}}}
Location
{{{location}}}

0°N 0°E / 0°N 0°E / 0; 0
Planned{{{planned}}}
Planned by{{{planned_by}}}
Commanded by{{{commanded_by}}}
Target{{{target}}}
Date{{{date}}}
{{{time}}}
{{{time-begin}}} – {{{time-end}}} ({{{timezone}}})
Executed by{{{executed_by}}}
Outcome{{{outcome}}}
Casualties{{{casualties}}}
{{{map_label}}} is located in Earth
{{{map_label}}}
{{{map_label}}}
{{{map_caption}}}
{{Infobox military operation
 |name          = 
 |partof        = 
 |subtitle      = 
 |image         = 
 |image_upright = 
 |alt           = 
 |caption       = 
 |scope         = 
 |type          = 
 |location      = 
 |location2     = <!-- 2 through 10 for more locations -->
 |coordinates   = 
 |coordinates2  = <!-- 2 through 10 for more locations -->
 |map_type      = 
 |map_size      = 
 |map_caption   = 
 |map_label     = 
 |map_label2    = <!-- 2 through 10 for more locations -->
 |planned       = 
 |planned_by    = 
 |commanded_by  = 
 |objective     = 
 |target        = 
 |date          = <!-- {{start date|YYYY|MM|DD|df=y}} --> 
 |time          = 
 |time-begin    = 
 |time-end      = 
 |timezone      = 
 |executed_by   = 
 |outcome       = 
 |casualties    = 
 |fatalities    = 
 |injuries      = 
}}

Example

Case Blue
Operational scopeStrategic offensive
Planned byWehrmacht
ObjectiveCapture of Caucasus oil fields
DateBegan 28 June 1942 (1942-06-28)
Executed byArmy Group South
{{Infobox military operation
 |name        = Case Blue
 |scope       = Strategic offensive
 |planned_by  = ''[[Wehrmacht]]''
 |objective   = Capture of [[Caucasus]] oil fields
 |executed    = Began {{start date|1942|06|28|df=y}}
 |executed_by = [[Army Group South]]
}}

Parameters

Note: When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". All subjective or qualitative judgements and numerical quantities or statistics must be cited to a reliable source (see WP:MILMOS#CITE).

  • name – the name of the operational plan; names in multiple languages may be provided.
  • subtitle – alternative name of the conflict being described.
  • partofoptional – the larger conflict containing the event described in the article.
  • imageoptional – an image for the warbox. Given in the form File:Example.jpg
  • image_uprightoptional – image upright scaling factor.
  • altoptionalAlternative text for image that is accessible to screen readers to help the visually impaired
  • captionoptional – the text to be placed below the image.
  • locationoptional – the location of the operation.
  • coordinatesoptional – the coordinates for the location above, given as {{coord}} with |display=inline,title. Used to display the geographic location of the conflict and the location on a map added with the map_type parameter. If coordinates for several locations are given, consider if hany shall have the title display.
  • map_typeoptional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
  • map_sizeoptional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
  • map_captionoptional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
  • map_labeloptional – the label placed next to the marker on the location map.
  • scopeoptional – the scope of the operation, such as "Strategic", "Operational", or "Tactical".
  • typeoptional – as an alternative to the scope field above, the type of operation, such as "Suicide attack" or "Ambush".
  • plannedoptional – the date(s) on which the plan was developed.
  • planned_byoptional – the person or group responsible for developing the plan.
  • commanded_byoptional – the person commanding the operation.
  • objectiveoptional – the objective(s) of the operation.
  • targetoptional – as an alternative to the objective field above, the target(s) of the operation.
  • dateoptional – the date(s), if any, on which the operation was executed. use {{Start date}} (and {{End date}} if required)
  • timeoptional – the time, if any, at which the operation was executed.
  • time-begin and time-endoptional – as an alternative to the time field above, the start and end times, respectively.
  • timezoneoptional – the timezone of the location of the operation; UTC+X, UTC-X, or UTC (i.e. offset from UTC) is preferred.
  • executed_byoptional – the people, groups, units, or formations responsible for executing the operation.
  • outcomeoptional – the outcome of the operation from the perspective of the planners with a very brief summary of defence if appropriate.
  • casualtiesoptional – any casualties occurring during the execution of the operation.
  • fatalitiesoptional – as an alternative to the casualties field above, the number of fatalities occurring during the execution of the operation.
  • injuriesoptional – as an alternative to the casualties field above, the number of injuries occurring during the execution of the operation.

Microformat

The HTML mark-up produced by this template includes an hCalendar microformat that makes event details readily parsable by computer programs. This aids tasks such as the cataloguing of articles and maintenance of databases. For more information about the use of microformats on Wikipedia, please visit the Microformat WikiProject.

Classes used

The HTML classes of this microformat include:

  • attendee
  • contact
  • description
  • dtend
  • dtstart
  • location
  • organiser
  • summary
  • url
  • vevent
Please do not rename or remove these classes
nor collapse nested elements which use them.

TemplateData

TemplateData for this template used by TemplateWizard, VisualEditor and other tools
See a monthly parameter usage report for Template:WikiProject Military history in articles based on its TemplateData.

TemplateData for WikiProject Military history

This infobox may be used to describe a particular planned or executed military operation or attack.

Template parameters

This template has custom formatting.

ParameterDescriptionTypeStatus
Namename

The name of the military operation

Stringsuggested

See also


Microformat

The HTML markup produced by this template includes an hCalendar microformat, which makes the event details parsable by computers, either acting automatically to catalogue article across Wikipedia, or via a browser tool operated by a person, to (for example) add the subject to a calendar or diary application. Within the hCalendar is a Geo microformat, which additionally makes the coordinates (latitude & longitude) parsable, so that they can be, say, looked up on a map, or downloaded to a GPS unit. For more information about the use of microformats on Wikipedia, please see the microformat project.

Dates will only be included if you use {{Start date}} or {{End date}} (use the former for single dates, but do not use any of these if the date is before 1583 CE). {{End date}} requires that a time be specified, but display of this time may be suppressed by adding |nodate=yes to the end.

To include a URL, use {{URL}}.

hCalendar uses HTML classes including:

  • attendee
  • dtend
  • dtstart
  • location
  • summary
  • url
  • vevent

Geo is produced by calling {{coord}}, and uses HTML classes:

  • geo
  • latitude
  • longitude

Please do not rename or remove these classes nor collapse nested elements which use them.
Also, when giving coordinates, please don't be overly precise.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. See a monthly parameter usage report for Template:WikiProject Military history in articles based on its TemplateData.

TemplateData for WikiProject Military history

TemplateData

Summarize information about a particular military conflict (a battle, campaign, war, or group of related wars).

Template parameters

This template has custom formatting.

ParameterDescriptionTypeStatus
Conflictconflict

The name of the conflict being described.

Linerequired
Widthwidth

Width of the infobox.

Default
315px
Stringoptional
Part ofpartof

The larger conflict containing the event described in the article.

Page nameoptional
Imageimage

An image for the warbox given in the form Example.jpg.

Fileoptional
Image sizeimage_size

The size of the image

Stringoptional
Altalt

Alternative textual description of the image

Stringoptional
Captioncaption

The text to be placed below the image.

Stringoptional
Datedate

The date of the conflict described. Convention is to give the actual date for battles and the years for wars, but this does not always apply.

Stringoptional
Placeplace

The location of the conflict.

Stringrequired
Coordinatescoordinates

The location of the structure, given as a coordinate pair by using {{coord}} with display=inline,title.

Stringoptional
Map Typemap_type

The base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.

Stringoptional
Map Reliefmap_relief

"yes" if the location map is a relief map.

Stringoptional
Map Sizemap_size

Width of the location map in pixels (px).

Default
220
Numberoptional
Map Markermap_mark

File to use as the location map marker.

Default
red_pog.svg
Stringoptional
Map Marker Sizemap_marksize

Width of the location map marker in pixels (px).

Default
8
Numberoptional
Map Captionmap_caption

Caption displayed below the location map.

Default
Location within {{{map_type}}}
Stringoptional
Map Labelmap_label

The label placed next to the marker on the location map.

Lineoptional
Territoryterritory

Any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement.

Stringoptional
Resultresult

This parameter may use one of two standard terms: "X victory" or "Inconclusive". The term used is for the "immediate" outcome of the "subject" conflict and should reflect what the sources say. In cases where the standard terms do not accurately describe the outcome, a link or note should be made to the section of the article where the result is discussed in detail (such as "See the Aftermath section"). Such a note can also be used in conjunction with the standard terms but should not be used to conceal an ambiguity in the "immediate" result. Do not introduce non-standard terms like "decisive", "marginal" or "tactical", or contradictory statements like "decisive tactical victory but strategic defeat". Omit this parameter altogether rather than engage in speculation about which side won or by how much.

Stringoptional
Statusstatus

For ongoing conflicts, the current status of the conflict.

Lineoptional
"Combatants" Header Textcombatants_header

Sets the header text for the combatants section.

Default
Belligerents
Lineoptional
Combatant 1combatant1

A party participating in the conflict.

Stringoptional
Combatant 2combatant2

A party participating in the conflict.

Stringoptional
Combatant 3combatant3

A party participating in the conflict. (only if the conflict has three distinct "sides")

Stringoptional
Combatant 1acombatant1a

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2acombatant2a

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3acombatant3a

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Combatant 1bcombatant1b

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2bcombatant2b

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3bcombatant3b

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Combatant 1ccombatant1c

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2ccombatant2c

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3ccombatant3c

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Combatant 1dcombatant1d

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2dcombatant2d

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3dcombatant3d

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Commander of Combatant 1commander1

The commanders of the military forces of Combatant (1) involved.

Stringoptional
Commander of Combatant 2commander2

The commanders of the military forces of Combatant 2 involved.

Stringoptional
Commander of Combatant 3commander3

The commanders of the military forces of Combatant 3 involved.

Stringoptional
Units of Combatant 1units1

The units or formations of Combatant 1 involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field.

Stringoptional
Units of Combatant 2units2

The units or formations of Combatant 2 involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field.

Stringoptional
Units of Combatant 3units3

The units or formations of Combatant 3 involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field.

Stringoptional
Strength of Combatant 1strength1

The numerical strength of Combatant 1.

Stringoptional
Strength of Combatant 2strength2

The numerical strength of Combatant 2.

Stringoptional
Strength of Combatant 3strength3

If Combatant 3 is set, this field is for the numerical strength of Combatant 3. If Combatant 3 is not set, this is an alternate combined field for use where only the total participation in a conflict is known.

Stringoptional
Casualties of Combatant 1casualties1

Casualties suffered by Combatant 1 (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc.

Stringoptional
Casualties of Combatant 2casualties2

Casualties suffered by Combatant 2 (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc.

Stringoptional
Casualties of Combatant 3casualties3

If Combatant 3 is set, this field is for the casualties suffered by Combatant 3, (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc. If combatant3 is not set, this is an alternate combined field for use where only the total casualties of a conflict are known, or where civilian casualties cannot be directly attributed to either side.

Stringoptional
Notesnotes

Optional field for further notes; this should only be used in exceptional circumstances.

Stringoptional
Campaignboxcampaignbox

Optional field for appending a campaignbox template to the bottom of the infobox, which allows both boxes to float as a single element (useful if there are subsequent left floating images, which would otherwise not be able to float above the campaign box); the template must be specified in the format {{Campaignbox XYZ}}.

Stringoptional

See also


Usage

Battle of Lützen
Part of the Thirty Years' War
Battle of Lutzen by Carl Whalbom depicting King Gustavus Aolphus falling from a horse mortally wounded in a melee
The Battle of Lützen by Carl Wahlbom shows the death of King Gustavus Adolphus on 16 November 1632.
Date6 November (O.S.) or 16 November (N.S.), 1632
Location
Near Lützen, southwest of Leipzig
(present-day Germany)
51°15′N 12°08′E / 51.250°N 12.133°E / 51.250; 12.133
Result Protestant victory
(see Aftermath section)
Belligerents
Sweden Sweden
Protestant Union
 Holy Roman Empire
Catholic League
Commanders and leaders
Sweden Gustavus Adolphus 
Sweden Dodo von Knyphausen
Electorate of Saxony Bernhard of Saxe-Weimar
Sweden Robert Munro, 18th Baron of Foulis
Holy Roman Empire Albrecht von Wallenstein
Holy Roman Empire Heinrich Holk
Holy Roman Empire Count Gottfried zu Pappenheim (DOW)
Strength
12,800 infantry
6,200 cavalry
60 guns
10,000 infantry
7,000 cavalry, plus 3,000 infantry and 2,000 cavalry on arrival
24 guns
Casualties and losses
3,400 dead and 1,600 wounded or missing Probably about the same as Swedish casualties[1]

A military conflict infobox (sometimes referred to as a warbox) may be used to summarize information about a particular military conflict (a battle, campaign, war, or group of related wars) in a standard manner.

Information summarized in an infobox should follow the general guidance for writing a lead section. It should not "make claims" or present material not covered by the article. As with a lead section, there is some discretion in citing information in an infobox. The same guidance should be applied to an infobox as given for citations in a lead section. Information in an infobox must conform with verifiability, point-of-view and other policies.

Information in the infobox should not be "controversial". Refer the reader to an appropriate section in the article or leave the parameter blank rather than make an unsubstantiated or doubtful claim.

The infobox should be added using the {{infobox military conflict}} template, as shown below:

{{Infobox military conflict
| conflict    = 
| width       = 
| partof      = 
| image       = 
| image_size  =
| alt         =
| caption     = 
| date        = 
| place       = 
| coordinates = <!--Use the {{coord}} template -->
| map_type    = 
| map_relief  = 
| map_size    = 
| map_marksize = 
| map_caption = 
| map_label   = 
| territory   = 
| result      = 
| status      = 
| combatants_header = 
| combatant1  = 
| combatant2  = 
| combatant3  = 
| commander1  = 
| commander2  = 
| commander3  = 
| units1      = 
| units2      = 
| units3      = 
| strength1   = 
| strength2   = 
| strength3   = 
| casualties1 = 
| casualties2 = 
| casualties3 = 
| notes       = 
| campaignbox = 
}}

Note: When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". All subjective or qualitative judgements and numerical quantities or statistics must be cited to a reliable source (see WP:MILMOS#CITE).

Parameters

  • conflict – the name of the conflict being described (e.g. "Battle of Lützen" or "World War I").
  • widthoptional – the width of the infobox, e.g. "400px"; defaults to: "315px".
  • partofoptional – the larger conflict containing the event described in the article. For battles or campaigns, this should be the war during which the event takes place; for particularly large wars, this may include a theatre (e.g. "the Eastern Front of World War II"). For wars, the parameter may be used to link to a larger group of wars (e.g. the Italian War of 1521–26 to the Italian Wars). It may be necessary to insert "the" before the name of the war for proper grammar.
  • imageoptional – an image for the warbox. Given in the form Example.jpg
  • image_sizeoptional – a size for the image
  • altoptionalAlternative text for image that is accessible to screen readers to help the visually impaired
  • captionoptional – the text to be placed below the image.
  • dateoptional – the date of the conflict described. Convention is to give the actual date for battles and the years for wars, but this does not always apply.
  • place – the location of the conflict. For conflicts covering a wide area, a general description (e.g. "France", or "Europe", or "Worldwide") may be used.
  • coordinatesoptional – the location of the structure, given as a coordinate pair by using {{coord}} with display=inline,title. Used to display the geographic location of the conflict and the location on a map added with the map_type parameter.
  • map_typeoptional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
  • map_reliefoptional – "yes" if the location map is a relief map; see {{location map}} for more details.
  • map_sizeoptional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
  • map_markoptional – the name of a file to use as the location map marker, e.g. Green_pog.svg; defaults to: "Red_pog.svg".
  • map_marksizeoptional – width of the location map marker in pixels (px), e.g. "10"; defaults to: "8".
  • map_captionoptional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
  • map_labeloptional – the label placed next to the marker on the location map.
  • territoryoptional – any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement.
  • actionoptional – In case of Coup d'État, short description of modus operandi, e.g. "...marched over the city...", "...dissolving the Congress of the Republic...", "...take the government hostage ...", "...put the country under military control ...", etc.
  • resultoptional – this parameter may use one of two standard terms: "X victory" or "Inconclusive". The term used is for the "immediate" outcome of the "subject" conflict and should reflect what the sources say. In cases where the standard terms do not accurately describe the outcome, a link or note should be made to the section of the article where the result is discussed in detail (such as "See the Aftermath section"). Such a note can also be used in conjunction with the standard terms but should not be used to conceal an ambiguity in the "immediate" result. Do not introduce non-standard terms like "decisive", "marginal" or "tactical", or contradictory statements like "decisive tactical victory but strategic defeat". Omit this parameter altogether rather than engage in speculation about which side won or by how much.
  • statusoptional – for ongoing conflicts, the current status of the conflict. This should not be used if a final result (above) is provided.
  • combatants_headeroptional – sets the header text for the combatants section. Default is "Belligerents". In case of Coup d'État, use "Government-Insurgents   "
  • combatant1/combatant2/combatant3optional – the parties participating in the conflict. This is most commonly the countries whose forces took part in the conflict; however, larger groups (such as alliances or international organizations) or smaller ones (such as particular units, formations, or groups) may be indicated if doing so improves reader understanding. When there is a large number of participants, it may be better to list only the three or four major groups on each side of the conflict, and to describe the rest in the body of the article. The combatant3 field may be used if a conflict has three distinct "sides", and should be left blank on other articles. Combatants should be listed in order of importance to the conflict, be it in terms of military contribution, political clout, or a recognized chain of command. If differing metrics can support alternative lists, then ordering is left to the editors of the particular article. The practice of writing in a "Supported by" subheading is deprecated (see discussion).
    • combatant1a/combatant2a/combatant3aoptional – in cases where the parties significantly changed over the course of the conflict, these subsidiary fields may be used to provide additional rows for the combatantN fields (above).
    • combatant1b/combatant2b/combatant3boptional – additional row, as above.
    • combatant1c/combatant2c/combatant3coptional – additional row, as above.
    • combatant1d/combatant2d/combatant3doptional – additional row, as above.
    • combatant1e/combatant2e/combatant3eoptional – additional row, as above.
  • commander1/commander2/commander3optional – the commanders of the military forces involved. For battles, this should include military commanders (and other officers as necessary). For wars, only prominent or notable leaders should be listed, with an upper limit of about seven per combatant column recommended. Ranks and position titles should be omitted. The {{KIA}} and {{POW}} templates may be included immediately after the names of commanders who were killed in action or surrendered and were taken prisoner, respectively. The commander3 field can only be used if the combatant3 field is set.
    • commander1a/commander2a/commander3aoptional – in cases where the commanders significantly changed over the course of the conflict, these subsidiary fields may be used to provide additional rows for the commanderN fields (above).
    • commander1b/commander2b/commander3boptional – additional row, as above.
    • commander1c/commander2c/commander3coptional – additional row, as above.
    • commander1d/commander2d/commander3doptional – additional row, as above.
    • commander1e/commander2e/commander3eoptional – additional row, as above.
  • units1/units2/units3optional – the units or formations involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field. The units3 field can only be used if the combatant3 field is set.
  • strength1/strength2optional – the numerical strength of the units involved.
  • polstrength1/polstrength2optional – In case of Coup d'Etat, political organizations that supported the government (1) respective the insurgents (2).
  • milstrength1/milstrength2optional – In case of Coup d'Etat, military units that supported the government (1) respective the insurgents (2).
  • strength3optional – if combatant3 is set, this is a third strength field identical to the two above; if it is not set, this is an alternate combined field for use where only the total participation in a conflict is known.
  • casualties1/casualties2optionalcasualties suffered (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Note that this section of the infobox is headed "Casualties and losses". Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc.
  • casualties3optional – if combatant3 is set, this is a third casualty field identical to the two above; if it is not set, this is an alternate combined field for use where only the total casualties of a conflict are known, or where civilian casualties cannot be directly attributed to either side.
  • notesoptional – optional field for further notes; this should only be used in exceptional circumstances.
  • campaignboxoptional – optional field for appending a campaignbox template to the bottom of the infobox, which allows both boxes to float as a single element (useful if there are subsequent left floating images, which would otherwise not be able to float above the campaign box); the template must be specified in the format {{Campaignbox XYZ}}.

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}}
or
{{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 = hlist and 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.

This infobox may be used to describe a particular planned or executed military operation or attack. For operations that resulted in combat, it can be used as an auxiliary template to the {{infobox military conflict}}, if necessary; for other types of operations, including those that were planned but never executed, it may be used alone. In the case of conflicts that consisted of multiple independent operations, multiple copies of the box may be used on a single article.


Usage

{{{title}}}
Part of {{{conflict}}}
[[File:{{{image}}}|{{{image_size}}}|alt={{{alt}}}|upright={{{image_upright}}}]]
{{{caption}}}
Operational scope{{{scope}}}
Location
{{{location}}}

0°N 0°E / 0°N 0°E / 0; 0
Planned{{{planned}}}
Planned by{{{planned_by}}}
Commanded by{{{commanded_by}}}
Target{{{target}}}
Date{{{date}}}
{{{time}}}
{{{time-begin}}} – {{{time-end}}} ({{{timezone}}})
Executed by{{{executed_by}}}
Outcome{{{outcome}}}
Casualties{{{casualties}}}
{{{map_label}}} is located in Earth
{{{map_label}}}
{{{map_label}}}
{{{map_caption}}}
{{Infobox military operation
 |name          = 
 |partof        = 
 |subtitle      = 
 |image         = 
 |image_upright = 
 |alt           = 
 |caption       = 
 |scope         = 
 |type          = 
 |location      = 
 |location2     = <!-- 2 through 10 for more locations -->
 |coordinates   = 
 |coordinates2  = <!-- 2 through 10 for more locations -->
 |map_type      = 
 |map_size      = 
 |map_caption   = 
 |map_label     = 
 |map_label2    = <!-- 2 through 10 for more locations -->
 |planned       = 
 |planned_by    = 
 |commanded_by  = 
 |objective     = 
 |target        = 
 |date          = <!-- {{start date|YYYY|MM|DD|df=y}} --> 
 |time          = 
 |time-begin    = 
 |time-end      = 
 |timezone      = 
 |executed_by   = 
 |outcome       = 
 |casualties    = 
 |fatalities    = 
 |injuries      = 
}}

Example

Case Blue
Operational scopeStrategic offensive
Planned byWehrmacht
ObjectiveCapture of Caucasus oil fields
DateBegan 28 June 1942 (1942-06-28)
Executed byArmy Group South
{{Infobox military operation
 |name        = Case Blue
 |scope       = Strategic offensive
 |planned_by  = ''[[Wehrmacht]]''
 |objective   = Capture of [[Caucasus]] oil fields
 |executed    = Began {{start date|1942|06|28|df=y}}
 |executed_by = [[Army Group South]]
}}

Parameters

Note: When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". All subjective or qualitative judgements and numerical quantities or statistics must be cited to a reliable source (see WP:MILMOS#CITE).

  • name – the name of the operational plan; names in multiple languages may be provided.
  • subtitle – alternative name of the conflict being described.
  • partofoptional – the larger conflict containing the event described in the article.
  • imageoptional – an image for the warbox. Given in the form File:Example.jpg
  • image_uprightoptional – image upright scaling factor.
  • altoptionalAlternative text for image that is accessible to screen readers to help the visually impaired
  • captionoptional – the text to be placed below the image.
  • locationoptional – the location of the operation.
  • coordinatesoptional – the coordinates for the location above, given as {{coord}} with |display=inline,title. Used to display the geographic location of the conflict and the location on a map added with the map_type parameter. If coordinates for several locations are given, consider if hany shall have the title display.
  • map_typeoptional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
  • map_sizeoptional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
  • map_captionoptional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
  • map_labeloptional – the label placed next to the marker on the location map.
  • scopeoptional – the scope of the operation, such as "Strategic", "Operational", or "Tactical".
  • typeoptional – as an alternative to the scope field above, the type of operation, such as "Suicide attack" or "Ambush".
  • plannedoptional – the date(s) on which the plan was developed.
  • planned_byoptional – the person or group responsible for developing the plan.
  • commanded_byoptional – the person commanding the operation.
  • objectiveoptional – the objective(s) of the operation.
  • targetoptional – as an alternative to the objective field above, the target(s) of the operation.
  • dateoptional – the date(s), if any, on which the operation was executed. use {{Start date}} (and {{End date}} if required)
  • timeoptional – the time, if any, at which the operation was executed.
  • time-begin and time-endoptional – as an alternative to the time field above, the start and end times, respectively.
  • timezoneoptional – the timezone of the location of the operation; UTC+X, UTC-X, or UTC (i.e. offset from UTC) is preferred.
  • executed_byoptional – the people, groups, units, or formations responsible for executing the operation.
  • outcomeoptional – the outcome of the operation from the perspective of the planners with a very brief summary of defence if appropriate.
  • casualtiesoptional – any casualties occurring during the execution of the operation.
  • fatalitiesoptional – as an alternative to the casualties field above, the number of fatalities occurring during the execution of the operation.
  • injuriesoptional – as an alternative to the casualties field above, the number of injuries occurring during the execution of the operation.

Microformat

The HTML mark-up produced by this template includes an hCalendar microformat that makes event details readily parsable by computer programs. This aids tasks such as the cataloguing of articles and maintenance of databases. For more information about the use of microformats on Wikipedia, please visit the Microformat WikiProject.

Classes used

The HTML classes of this microformat include:

  • attendee
  • contact
  • description
  • dtend
  • dtstart
  • location
  • organiser
  • summary
  • url
  • vevent
Please do not rename or remove these classes
nor collapse nested elements which use them.

TemplateData

TemplateData for this template used by TemplateWizard, VisualEditor and other tools
See a monthly parameter usage report for Template:WikiProject Military history in articles based on its TemplateData.

TemplateData for WikiProject Military history

This infobox may be used to describe a particular planned or executed military operation or attack.

Template parameters

This template has custom formatting.

ParameterDescriptionTypeStatus
Namename

The name of the military operation

Stringsuggested

See also


Microformat

The HTML markup produced by this template includes an hCalendar microformat, which makes the event details parsable by computers, either acting automatically to catalogue article across Wikipedia, or via a browser tool operated by a person, to (for example) add the subject to a calendar or diary application. Within the hCalendar is a Geo microformat, which additionally makes the coordinates (latitude & longitude) parsable, so that they can be, say, looked up on a map, or downloaded to a GPS unit. For more information about the use of microformats on Wikipedia, please see the microformat project.

Dates will only be included if you use {{Start date}} or {{End date}} (use the former for single dates, but do not use any of these if the date is before 1583 CE). {{End date}} requires that a time be specified, but display of this time may be suppressed by adding |nodate=yes to the end.

To include a URL, use {{URL}}.

hCalendar uses HTML classes including:

  • attendee
  • dtend
  • dtstart
  • location
  • summary
  • url
  • vevent

Geo is produced by calling {{coord}}, and uses HTML classes:

  • geo
  • latitude
  • longitude

Please do not rename or remove these classes nor collapse nested elements which use them.
Also, when giving coordinates, please don't be overly precise.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. See a monthly parameter usage report for Template:WikiProject Military history in articles based on its TemplateData.

TemplateData for WikiProject Military history

TemplateData

Summarize information about a particular military conflict (a battle, campaign, war, or group of related wars).

Template parameters

This template has custom formatting.

ParameterDescriptionTypeStatus
Conflictconflict

The name of the conflict being described.

Linerequired
Widthwidth

Width of the infobox.

Default
315px
Stringoptional
Part ofpartof

The larger conflict containing the event described in the article.

Page nameoptional
Imageimage

An image for the warbox given in the form Example.jpg.

Fileoptional
Image sizeimage_size

The size of the image

Stringoptional
Altalt

Alternative textual description of the image

Stringoptional
Captioncaption

The text to be placed below the image.

Stringoptional
Datedate

The date of the conflict described. Convention is to give the actual date for battles and the years for wars, but this does not always apply.

Stringoptional
Placeplace

The location of the conflict.

Stringrequired
Coordinatescoordinates

The location of the structure, given as a coordinate pair by using {{coord}} with display=inline,title.

Stringoptional
Map Typemap_type

The base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.

Stringoptional
Map Reliefmap_relief

"yes" if the location map is a relief map.

Stringoptional
Map Sizemap_size

Width of the location map in pixels (px).

Default
220
Numberoptional
Map Markermap_mark

File to use as the location map marker.

Default
red_pog.svg
Stringoptional
Map Marker Sizemap_marksize

Width of the location map marker in pixels (px).

Default
8
Numberoptional
Map Captionmap_caption

Caption displayed below the location map.

Default
Location within {{{map_type}}}
Stringoptional
Map Labelmap_label

The label placed next to the marker on the location map.

Lineoptional
Territoryterritory

Any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement.

Stringoptional
Resultresult

This parameter may use one of two standard terms: "X victory" or "Inconclusive". The term used is for the "immediate" outcome of the "subject" conflict and should reflect what the sources say. In cases where the standard terms do not accurately describe the outcome, a link or note should be made to the section of the article where the result is discussed in detail (such as "See the Aftermath section"). Such a note can also be used in conjunction with the standard terms but should not be used to conceal an ambiguity in the "immediate" result. Do not introduce non-standard terms like "decisive", "marginal" or "tactical", or contradictory statements like "decisive tactical victory but strategic defeat". Omit this parameter altogether rather than engage in speculation about which side won or by how much.

Stringoptional
Statusstatus

For ongoing conflicts, the current status of the conflict.

Lineoptional
"Combatants" Header Textcombatants_header

Sets the header text for the combatants section.

Default
Belligerents
Lineoptional
Combatant 1combatant1

A party participating in the conflict.

Stringoptional
Combatant 2combatant2

A party participating in the conflict.

Stringoptional
Combatant 3combatant3

A party participating in the conflict. (only if the conflict has three distinct "sides")

Stringoptional
Combatant 1acombatant1a

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2acombatant2a

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3acombatant3a

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Combatant 1bcombatant1b

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2bcombatant2b

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3bcombatant3b

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Combatant 1ccombatant1c

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2ccombatant2c

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3ccombatant3c

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Combatant 1dcombatant1d

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 1 field.

Stringoptional
Combatant 2dcombatant2d

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 2 field.

Stringoptional
Combatant 3dcombatant3d

In cases where the parties significantly changed over the course of the conflict, this field may be used to provide additional rows for the Combatant 3 field.

Stringoptional
Commander of Combatant 1commander1

The commanders of the military forces of Combatant (1) involved.

Stringoptional
Commander of Combatant 2commander2

The commanders of the military forces of Combatant 2 involved.

Stringoptional
Commander of Combatant 3commander3

The commanders of the military forces of Combatant 3 involved.

Stringoptional
Units of Combatant 1units1

The units or formations of Combatant 1 involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field.

Stringoptional
Units of Combatant 2units2

The units or formations of Combatant 2 involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field.

Stringoptional
Units of Combatant 3units3

The units or formations of Combatant 3 involved. If a large number of distinct formations is present, it may be better to reference an order of battle in the body of the article than to include the entire list in this field.

Stringoptional
Strength of Combatant 1strength1

The numerical strength of Combatant 1.

Stringoptional
Strength of Combatant 2strength2

The numerical strength of Combatant 2.

Stringoptional
Strength of Combatant 3strength3

If Combatant 3 is set, this field is for the numerical strength of Combatant 3. If Combatant 3 is not set, this is an alternate combined field for use where only the total participation in a conflict is known.

Stringoptional
Casualties of Combatant 1casualties1

Casualties suffered by Combatant 1 (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc.

Stringoptional
Casualties of Combatant 2casualties2

Casualties suffered by Combatant 2 (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc.

Stringoptional
Casualties of Combatant 3casualties3

If Combatant 3 is set, this field is for the casualties suffered by Combatant 3, (including: dead, wounded, missing, captured and civilian deaths) and equipment losses. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". Where equipment losses are reported, this should be confined to major or significant types of equipment broadly categorized such as: tanks, guns (artillery pieces), aircraft, destroyers etc. If combatant3 is not set, this is an alternate combined field for use where only the total casualties of a conflict are known, or where civilian casualties cannot be directly attributed to either side.

Stringoptional
Notesnotes

Optional field for further notes; this should only be used in exceptional circumstances.

Stringoptional
Campaignboxcampaignbox

Optional field for appending a campaignbox template to the bottom of the infobox, which allows both boxes to float as a single element (useful if there are subsequent left floating images, which would otherwise not be able to float above the campaign box); the template must be specified in the format {{Campaignbox XYZ}}.

Stringoptional

See also

Color scheme

For the "colour_scheme" parameter in {{Battlebox}}, use the value from the appropriate "Colour" cell in the following table.

Colour scheme for battleboxes
Land Battles (black text)
Colour Locality Example
background:#ffcccc North America Battle of New Orleans
background:#ccffcc South America Battle of Goose Green
background:#ffff99 Asia¹ Battle of Ager Sanguinis
background:#cccccc Europe¹ Battle of Lützen (1632)
background:#eeddbb Africa Battle of Romani
background:#ffccaa Oceania² Battle of Iwo Jima
background:#ffccff Fictitious³ Nirnaeth Arnoediad
empty Other/Unknown none

Naval Battles (blue text)
Colour Locality Example
background:#ffcccc;color:#2222cc North America Battle of Lake Erie
background:#ccffcc;color:#2222cc South America Battle of the River Plate
background:#ffff99;color:#2222cc Asia¹ Battle of Syllaeum
background:#cccccc;color:#2222cc Europe¹ Battle of Naupactus (429 BC)
background:#eeddbb;color:#2222cc Africa Battle of the Nile
background:#ffccaa;color:#2222cc Oceania² Battle of Midway
background:#ffccff;color:#2222cc Fictitious³ the Sacrifice of Thunder Child
background:#ccccff;color:#2222cc Open ocean⁴ The Glorious First of June
Notes:
  1. The official border between the Asian and European continents is the Ural Mountains, Black Sea, Bosphorus, Sea of Marmara and Dardanelles.
  2. Oceania covers Australia, New Zealand, Pacific Islands, Papua New Guinea, the Philippines and Antarctica.
  3. "Fictitious" includes mythological, literary, movie, science fiction, fantasy battles. A fictitious battle in Europe remains fictitious.
  4. "Open ocean" can mean outside of the 12 nautical mile territorial limit of any nation on a continent, or the 200 nautical mile exclusive economic zone of continental nations.


Progress

See also: Wikipedia:New articles (Battles)

Most wanted

Of the 50 largest battles of the 20th century, we still have articles on fewer than half. In rough order of size, the most wanted articles are these:

Eastern Front (WWII)

World War I

Other C20