Loading AI tools
From Wikipedia, the free encyclopedia
Peninsular Revolutionary War | |||||||||
---|---|---|---|---|---|---|---|---|---|
![]() The Battle of Málaga by Edgar Garcia illustrates the despair of Spanish Imperials in the Iberian Penisula | |||||||||
| |||||||||
Belligerents | |||||||||
Revolutionary Forces: ![]() |
Spanish Coalition: ![]() | ||||||||
Commanders and leaders | |||||||||
![]() |
![]() | ||||||||
Casualties and losses | |||||||||
European Theatre: ~750 000 dead and ~2 900 000 or more wounded or missing[1] French losses
Westphalian / Rhine losses
Hanseatic losses
|
European Theatre: ~750 000 dead and ~2 900 000 or more wounded or missing[1] French losses
Spanish losses
Scandinavian losses
Ottoman losses
|
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 = | caption = | date = | place = | coordinates = | map_type = | map_relief = | latitude = | longitude = | 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).
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.
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 =
}}
{{subst:PAGENAME}}
.[[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.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.
|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.
{{{title}}} | |
---|---|
Part of {{{conflict}}} | |
[[File:{{{image}}}|{{{image_size}}}|alt={{{alt}}}|upright={{{image_upright}}}]] {{{caption}}} | |
Operational scope | {{{scope}}} |
Location | {{{location}}} 0°N 0°E |
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}}} |
{{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 =
}}
Case Blue | |
---|---|
Operational scope | Strategic offensive |
Planned by | Wehrmacht |
Objective | Capture of Caucasus oil fields |
Date | Began 28 June 1942 |
Executed by | Army 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]]
}}
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).
File:Example.jpg
map_type
parameter. If coordinates for several locations are given, consider if hany shall have the title display.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.
The HTML classes of this microformat include:
See a monthly parameter usage report for Template:Necazian in articles based on its TemplateData.
TemplateData for Necazian |
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:
Geo is produced by calling {{coord}}, and uses HTML classes:
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 for Necazian
Parameter | Description | Type | Status | |
---|---|---|---|---|
Conflict | conflict | The name of the conflict being described. | Line | required |
Width | width | Width of the infobox.
| String | optional |
Part of | partof | The larger conflict containing the event described in the article. | Page name | optional |
Image | image | An image for the warbox given in the form Example.jpg. | String | optional |
Image size | image_size | The size of the image | String | optional |
Caption | caption | The text to be placed below the image. | String | optional |
Date | date | 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. | String | optional |
Place | place | The location of the conflict. | String | required |
Coordinates | coordinates | The location of the structure, given as a coordinate pair by using {{coord}} with display=inline,title. | String | optional |
Map Type | map_type | The base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details. | String | optional |
Map Relief | map_relief | "yes" if the location map is a relief map. | String | optional |
Latitude | latitude | Latitude for placing the marker on the location map. | Number | optional |
Longitude | longitude | Longitude for placing the marker on the location map. | Number | optional |
Map Size | map_size | Width of the location map in pixels (px).
| Number | optional |
Map Marker | map_mark | File to use as the location map marker.
| String | optional |
Map Marker Size | map_marksize | Width of the location map marker in pixels (px).
| Number | optional |
Map Caption | map_caption | Caption displayed below the location map.
| String | optional |
Map Label | map_label | The label placed next to the marker on the location map. | Line | optional |
Territory | territory | Any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement. | String | optional |
Result | result | 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. | Line | optional |
Status | status | For ongoing conflicts, the current status of the conflict. | Line | optional |
"Combatants" Header Text | combatants_header | Sets the header text for the combatants section.
| Line | optional |
Combatant 1 | combatant1 | A party participating in the conflict. | String | optional |
Combatant 2 | combatant2 | A party participating in the conflict. | String | optional |
Combatant 3 | combatant3 | A party participating in the conflict. (only if the conflict has three distinct "sides") | String | optional |
Combatant 1a | combatant1a | 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. | String | optional |
Combatant 2a | combatant2a | 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. | String | optional |
Combatant 3a | combatant3a | 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. | String | optional |
Combatant 1b | combatant1b | 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. | String | optional |
Combatant 2b | combatant2b | 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. | String | optional |
Combatant 3b | combatant3b | 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. | String | optional |
Combatant 1c | combatant1c | 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. | String | optional |
Combatant 2c | combatant2c | 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. | String | optional |
Combatant 3c | combatant3c | 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. | String | optional |
Combatant 1d | combatant1d | 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. | String | optional |
Combatant 2d | combatant2d | 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. | String | optional |
Combatant 3d | combatant3d | 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. | String | optional |
Commander of Combatant 1 | commander1 | The commanders of the military forces of Combatant (1) involved. | String | optional |
Commander of Combatant 2 | commander2 | The commanders of the military forces of Combatant 2 involved. | String | optional |
Commander of Combatant 3 | commander3 | The commanders of the military forces of Combatant 3 involved. | String | optional |
Units of Combatant 1 | units1 | 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. | String | optional |
Units of Combatant 2 | units2 | 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. | String | optional |
Units of Combatant 3 | units3 | 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. | String | optional |
Strength of Combatant 1 | strength1 | The numerical strength of Combatant 1. | String | optional |
Strength of Combatant 2 | strength2 | The numerical strength of Combatant 2. | String | optional |
Strength of Combatant 3 | strength3 | 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. | String | optional |
Casualties of Combatant 1 | casualties1 | Casualties suffered by Combatant 1, including dead, wounded, missing, captured, and civilian deaths. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". | String | optional |
Casualties of Combatant 2 | casualties2 | Casualties suffered by Combatant 2, including dead, wounded, missing, captured, and civilian deaths. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". | String | optional |
Casualties of Combatant 3 | casualties3 | If Combatant 3 is set, this field is for the casualties suffered by Combatant 3, including dead, wounded, missing, captured, and civilian deaths. Terms such as "dead" (or "killed"), "wounded", or "captured" should be used in place of abbreviations such as "KIA" or "POW". 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. | String | optional |
Notes | notes | Optional field for further notes; this should only be used in exceptional circumstances. | String | optional |
Campaignbox | campaignbox | 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 {{t|Campaignbox XYZ}}. | String | optional |
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.