Wikipedia:WikiProject Military history
Military history is the recording (in writing or otherwise) of the events in the history of humanity that fall within the category of conflict. This may range from a melee between two tribes to conflicts between proper militaries to a world war affecting the majority of the human population.
This WikiProject has three main goals:
- To provide a standardized format for articles which describe aspects of military history (especially wars, battles, and related subjects).
- To improve Wikipedia's coverage of military history by creating, expanding, and maintaining such articles.
- To serve as a central point of discussion for issues related to these articles.
Announcements and open tasks
Guidelines
Naming
Articles should be called something like Battle of Gettysburg or Siege of Nuremberg. "Battle" and "Siege" are neutral terms and are 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.
Article structure
The guidelines presented in this section are intended to serve as a starting point for writing a good article; they are not meant to enforce a single structure on all articles, nor to limit the topics an article will discuss.
Battles
The opening paragraph (or lead section in a longer article) should concisely convey:
- The name of the battle (including alternate names).
- When did it happen?
- Where did it happen?
- Which war or campaign does it belong to?
- Who were the combatants?
- What was its outcome or significance?
The article can be structured along these lines:
- The background. Why did it take place? Which campaign did it belong to? What happened previously?
- The prelude. What forces were involved? How did they arrive at the battleground? Was there a plan?
- A description of the battle. What tactics were used?
- 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 Normandy for a longer one.
Wars
The opening paragraph (or lead section) should concisely convey:
- The name of the war (including alternate names).
- When did it happen?
- Who fought in it?
- Why did it happen? (but if it is impossible to simplify complex causes into a one-sentence explanation, leave this for a later section)
- What was the outcome?
- What was its significance, if any?
The article can be structured along these lines:
- The historical background to the conflict, including preceding conflicts, the political situation, military preparedness, and technology.
- The causes of the conflict.
- The trigger, if notable. For example, the murder of Archduke Franz Ferdinand of Austria triggered a sequence of events that led to World War I. Take care to distinguish a trigger or pretext from the underlying causes that allowed the event to trigger a war.
- How the partipants became involved, and the first military moves.
- A summary of the conflict. When a war is large, it can often be divided into phases, geographic regions ("theaters"), or naval and land campaigns. Military actions then be described by phase, theater, or campaign. Don't describe individual battles in detail; refer to a separate article on the battle and just explain the result of the battle and its consequences for the war.
- If the war is very large there should be separate articles for each phase/theater/campaign of the war, and for important tactical, strategic and technological aspects of the war. Give brief summaries of those aspects of the war in the main article, and refer the reader to the detailed article.
- How the war came to an end. If there was an important peace treaty, make a separate article for the peace treaty and refer to it.
- What were the consequences of the war? Who did it affect? What happened next? Did the war lead to peace or to further wars? Were countries conquered or liberated? Were there significant advances in tactics or technology?
- Auxiliary lists and tables: list of battles, list of countries and alliances involved, table casualties by country.
If the article is long, it can be divided into sections along the lines indicated above (if it is short, there is no need). See First Anglo-Dutch War for a short article with this structure, and World War I for a long article.
Infobox templates
 | This template is used on approximately 16,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
 | This template uses Lua: |
Usage
| Battle of Lützen | |||||||
|---|---|---|---|---|---|---|---|
| Part of the Thirty Years' War | |||||||
 The Battle of Lützen by Carl Wahlbom shows the death of King Gustavus Adolphus on 16 November 1632. | |||||||
| |||||||
| Belligerents | |||||||
 SwedenProtestant Union |
 Holy Roman Empire Catholic League | ||||||
| Commanders and leaders | |||||||
Gustavus Adolphus † Dodo von Knyphausen Bernhard of Saxe-Weimar Robert Munro, 18th Baron of Foulis |
Albrecht von Wallenstein Heinrich Holk 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").
- width – optional – the width of the infobox, e.g. "400px"; defaults to: "315px".
- partof – optional – 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.
- image – optional – an image for the warbox. Given in the form
Example.jpg - image_size – optional – a size for the image
- alt – optional – Alternative text for image that is accessible to screen readers to help the visually impaired
- caption – optional – the text to be placed below the image.
- date – optional – 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.
- coordinates – optional – 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_typeparameter. - map_type – optional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
- map_relief – optional – "yes" if the location map is a relief map; see {{location map}} for more details.
- map_size – optional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
- map_mark – optional – the name of a file to use as the location map marker, e.g. Green_pog.svg; defaults to: "Red_pog.svg".
- map_marksize – optional – width of the location map marker in pixels (px), e.g. "10"; defaults to: "8".
- map_caption – optional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
- map_label – optional – the label placed next to the marker on the location map.
- territory – optional – any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement.
- action – optional – 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.
- result – optional – 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.
- status – optional – for ongoing conflicts, the current status of the conflict. This should not be used if a final result (above) is provided.
- combatants_header – optional – sets the header text for the combatants section. Default is "Belligerents". In case of Coup d'État, use "Government-Insurgents "
- combatant1/combatant2/combatant3 – optional – 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/combatant3a – optional – 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/combatant3b – optional – additional row, as above.
- combatant1c/combatant2c/combatant3c – optional – additional row, as above.
- combatant1d/combatant2d/combatant3d – optional – additional row, as above.
- combatant1e/combatant2e/combatant3e – optional – additional row, as above.
- commander1/commander2/commander3 – optional – 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/commander3a – optional – 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/commander3b – optional – additional row, as above.
- commander1c/commander2c/commander3c – optional – additional row, as above.
- commander1d/commander2d/commander3d – optional – additional row, as above.
- commander1e/commander2e/commander3e – optional – additional row, as above.
- units1/units2/units3 – optional – 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/strength2 – optional – the numerical strength of the units involved.
- polstrength1/polstrength2 – optional – In case of Coup d'Etat, political organizations that supported the government (1) respective the insurgents (2).
- milstrength1/milstrength2 – optional – In case of Coup d'Etat, military units that supported the government (1) respective the insurgents (2).
- strength3 – optional – 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/casualties2 – optional – casualties 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.
- casualties3 – optional – 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.
- notes – optional – optional field for further notes; this should only be used in exceptional circumstances.
- campaignbox – optional – 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}}
{{Infobox military conflict
...
| campaignbox = {{campaignbox XXXX}}
}}
Articles may include multiple campaignboxes; typically, these are stacked under the infobox. The most common scenario occurs when two levels of campaignboxes are present – for example, an article about a battle can include both a campaignbox listing the battle itself and an "enclosing" campaignbox listing the campaign, theater or war during which the battle took place. Similarly, an article about a war can include both a campaignbox listing the war (among a series of wars) and a campaignbox for the war itself, listing the battles that took place during it.
Creating campaignboxes
Existing campaignboxes may be viewed through the Campaignbox template category to which campaignboxes are added automatically. If a new campaignbox becomes necessary, it should be named Template:Campaignbox XXXX (where XXXX is the (shortened) name of the campaign) and should use {{Campaignbox}} thus:
{{Campaignbox
| name =
| title =
| battles =
| notes =
}}
Parameters
- name
- The name by which Wikipedia refers to the template, i.e. "Template:Campaignbox XXXX". This can be produced by using
{{subst:PAGENAME}}. - title
- The name of the campaign or war, which, if an article about the campaign or war exists, should link to it. Dates should not be indicated unless needed for clarity. Note that long links may cause alignment problems; see the troubleshooting guide for more information.
- battles
- A chronological list of battles and operations in the campaign, linked as
[[Battle of YYYY|YYYY]]. A convenient and accessible way to separate the items in the list is to add| listclass = hlistand then use the standard * (asterisk)-based listing format. - notes
- (optional) Any explanatory notes needed to clarify the list. This option should be used sparingly.
- (raw_name)
- (optional; deprecated) This parameter overrides the use of the title in determining the template name and exists for the sake of backward compatibility. When creating a new campaignbox, both title and name should be specified as above and this parameter omitted.
The following optional parameters are passed on to the templates {{Military navigation}} or {{Navbox}} used to create campaignboxes and so can affect their styling. See these two templates' documentation pages for further details.
- state
- To set whether the campaignbox appears fully visible or collapsed (to titlebar only) when it is first presented by a page.
- bodyclass
- CSS styling to affect the whole template.
- listclass
- CSS styling to affect the list of battles, operations, etc. (e.g. to affect
|battles=).
The use of special formatting (such as bolding or changes in font size) in the list of battles – particularly to mark battles as "important" – is generally discouraged; while there are a few cases where such approaches may be both helpful to the reader and sufficiently well-sourced that they do not constitute original research, they are usually both unnecessary and potentially confusing. Similarly, dividing the list of battles into multiple blocks by inserting heading-like separations should be exceptional; if such a division is felt to be needed, a better solution may be to split the one campaignbox into two or more.
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 |
| 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}}} |
.svg)  {{{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 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]]
}}
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.
- partof – optional – the larger conflict containing the event described in the article.
- image – optional – an image for the warbox. Given in the form
File:Example.jpg - image_upright – optional – image upright scaling factor.
- alt – optional – Alternative text for image that is accessible to screen readers to help the visually impaired
- caption – optional – the text to be placed below the image.
- location – optional – the location of the operation.
- coordinates – optional – 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_typeparameter. If coordinates for several locations are given, consider if hany shall have the title display. - map_type – optional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
- map_size – optional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
- map_caption – optional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
- map_label – optional – the label placed next to the marker on the location map.
- scope – optional – the scope of the operation, such as "Strategic", "Operational", or "Tactical".
- type – optional – as an alternative to the scope field above, the type of operation, such as "Suicide attack" or "Ambush".
- planned – optional – the date(s) on which the plan was developed.
- planned_by – optional – the person or group responsible for developing the plan.
- commanded_by – optional – the person commanding the operation.
- objective – optional – the objective(s) of the operation.
- target – optional – as an alternative to the objective field above, the target(s) of the operation.
- date – optional – the date(s), if any, on which the operation was executed. use {{Start date}} (and {{End date}} if required)
- time – optional – the time, if any, at which the operation was executed.
- time-begin and time-end – optional – as an alternative to the time field above, the start and end times, respectively.
- timezone – optional – the timezone of the location of the operation; UTC+X, UTC-X, or UTC (i.e. offset from UTC) is preferred.
- executed_by – optional – the people, groups, units, or formations responsible for executing the operation.
- outcome – optional – the outcome of the operation from the perspective of the planners with a very brief summary of defence if appropriate.
- casualties – optional – any casualties occurring during the execution of the operation.
- fatalities – optional – as an alternative to the casualties field above, the number of fatalities occurring during the execution of the operation.
- injuries – optional – 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
nor collapse nested elements which use them.
TemplateData
|
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.
| ||||||||||
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
TemplateData for WikiProject Military history
TemplateData
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Summarize information about a particular military conflict (a battle, campaign, war, or group of related wars).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See also
| This template is used on many pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
| This template uses Lua: |
 | This template does not display in the mobile view of Wikipedia; it is desktop only. Read the documentation for an explanation. |
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed on the mobile web site of English Wikipedia. Mobile page views account for approximately 66% of all page views (90-day average as of January 2024[update]).
Usage
Campaignboxes
One common type of navigational template in articles concerning conflicts, wars and related topics is the campaignbox template, intended to provide context and convenient navigation among articles on the battles in a campaign, front, theater or war (or, more rarely, among several campaigns or wars).
If the article includes an infobox, the campaignbox/es are usually placed immediately after it (i.e. just below it). If available, as with infoboxes such as {{Infobox military conflict}}, use the infobox's |campaignbox= parameter:
{{Infobox military conflict
...
}}
{{Campaignbox XXXX}}
{{Infobox military conflict
...
| campaignbox = {{campaignbox XXXX}}
}}
Articles may include multiple campaignboxes; typically, these are stacked under the infobox. The most common scenario occurs when two levels of campaignboxes are present – for example, an article about a battle can include both a campaignbox listing the battle itself and an "enclosing" campaignbox listing the campaign, theater or war during which the battle took place. Similarly, an article about a war can include both a campaignbox listing the war (among a series of wars) and a campaignbox for the war itself, listing the battles that took place during it.
Creating campaignboxes
Existing campaignboxes may be viewed through the Campaignbox template category to which campaignboxes are added automatically. If a new campaignbox becomes necessary, it should be named Template:Campaignbox XXXX (where XXXX is the (shortened) name of the campaign) and should use {{Campaignbox}} thus:
{{Campaignbox
| name =
| title =
| battles =
| notes =
}}
Parameters
- name
- The name by which Wikipedia refers to the template, i.e. "Template:Campaignbox XXXX". This can be produced by using
{{subst:PAGENAME}}. - title
- The name of the campaign or war, which, if an article about the campaign or war exists, should link to it. Dates should not be indicated unless needed for clarity. Note that long links may cause alignment problems; see the troubleshooting guide for more information.
- battles
- A chronological list of battles and operations in the campaign, linked as
[[Battle of YYYY|YYYY]]. A convenient and accessible way to separate the items in the list is to add| listclass = hlistand then use the standard * (asterisk)-based listing format. - notes
- (optional) Any explanatory notes needed to clarify the list. This option should be used sparingly.
- (raw_name)
- (optional; deprecated) This parameter overrides the use of the title in determining the template name and exists for the sake of backward compatibility. When creating a new campaignbox, both title and name should be specified as above and this parameter omitted.
The following optional parameters are passed on to the templates {{Military navigation}} or {{Navbox}} used to create campaignboxes and so can affect their styling. See these two templates' documentation pages for further details.
- state
- To set whether the campaignbox appears fully visible or collapsed (to titlebar only) when it is first presented by a page.
- bodyclass
- CSS styling to affect the whole template.
- listclass
- CSS styling to affect the list of battles, operations, etc. (e.g. to affect
|battles=).
The use of special formatting (such as bolding or changes in font size) in the list of battles – particularly to mark battles as "important" – is generally discouraged; while there are a few cases where such approaches may be both helpful to the reader and sufficiently well-sourced that they do not constitute original research, they are usually both unnecessary and potentially confusing. Similarly, dividing the list of battles into multiple blocks by inserting heading-like separations should be exceptional; if such a division is felt to be needed, a better solution may be to split the one campaignbox into two or more.
| This template is used on many pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
 | This template adds an automatically generated short description. If the automatic short description is not optimal, replace it by adding {{Short description}} at the top of the article. |
| This template uses Lua: |
Usage
Military unit infobox
A military unit infobox may be used to summarize information about an individual military unit or formation, such as a regiment or division.
The infobox should be added using the {{Infobox military unit}} template, as shown below:
Military history is the recording (in writing or otherwise) of the events in the history of humanity that fall within the category of conflict. This may range from a melee between two tribes to conflicts between proper militaries to a world war affecting the majority of the human population.
This WikiProject has three main goals:
- To provide a standardized format for articles which describe aspects of military history (especially wars, battles, and related subjects).
- To improve Wikipedia's coverage of military history by creating, expanding, and maintaining such articles.
- To serve as a central point of discussion for issues related to these articles.
Announcements and open tasks
Guidelines
Naming
Articles should be called something like Battle of Gettysburg or Siege of Nuremberg. "Battle" and "Siege" are neutral terms and are 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.
Article structure
The guidelines presented in this section are intended to serve as a starting point for writing a good article; they are not meant to enforce a single structure on all articles, nor to limit the topics an article will discuss.
Battles
The opening paragraph (or lead section in a longer article) should concisely convey:
- The name of the battle (including alternate names).
- When did it happen?
- Where did it happen?
- Which war or campaign does it belong to?
- Who were the combatants?
- What was its outcome or significance?
The article can be structured along these lines:
- The background. Why did it take place? Which campaign did it belong to? What happened previously?
- The prelude. What forces were involved? How did they arrive at the battleground? Was there a plan?
- A description of the battle. What tactics were used?
- 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 Normandy for a longer one.
Wars
The opening paragraph (or lead section) should concisely convey:
- The name of the war (including alternate names).
- When did it happen?
- Who fought in it?
- Why did it happen? (but if it is impossible to simplify complex causes into a one-sentence explanation, leave this for a later section)
- What was the outcome?
- What was its significance, if any?
The article can be structured along these lines:
- The historical background to the conflict, including preceding conflicts, the political situation, military preparedness, and technology.
- The causes of the conflict.
- The trigger, if notable. For example, the murder of Archduke Franz Ferdinand of Austria triggered a sequence of events that led to World War I. Take care to distinguish a trigger or pretext from the underlying causes that allowed the event to trigger a war.
- How the partipants became involved, and the first military moves.
- A summary of the conflict. When a war is large, it can often be divided into phases, geographic regions ("theaters"), or naval and land campaigns. Military actions then be described by phase, theater, or campaign. Don't describe individual battles in detail; refer to a separate article on the battle and just explain the result of the battle and its consequences for the war.
- If the war is very large there should be separate articles for each phase/theater/campaign of the war, and for important tactical, strategic and technological aspects of the war. Give brief summaries of those aspects of the war in the main article, and refer the reader to the detailed article.
- How the war came to an end. If there was an important peace treaty, make a separate article for the peace treaty and refer to it.
- What were the consequences of the war? Who did it affect? What happened next? Did the war lead to peace or to further wars? Were countries conquered or liberated? Were there significant advances in tactics or technology?
- Auxiliary lists and tables: list of battles, list of countries and alliances involved, table casualties by country.
If the article is long, it can be divided into sections along the lines indicated above (if it is short, there is no need). See First Anglo-Dutch War for a short article with this structure, and World War I for a long article.
Infobox templates
| This template is used on approximately 16,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
| This template uses Lua: |
Usage
| Battle of Lützen | |||||||
|---|---|---|---|---|---|---|---|
| Part of the Thirty Years' War | |||||||
The Battle of Lützen by Carl Wahlbom shows the death of King Gustavus Adolphus on 16 November 1632. | |||||||
| |||||||
| Belligerents | |||||||
|
Sweden Protestant Union |
Holy Roman Empire Catholic League | ||||||
| Commanders and leaders | |||||||
|
Gustavus Adolphus † Dodo von Knyphausen Bernhard of Saxe-Weimar Robert Munro, 18th Baron of Foulis |
Albrecht von Wallenstein Heinrich Holk 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").
- width – optional – the width of the infobox, e.g. "400px"; defaults to: "315px".
- partof – optional – 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.
- image – optional – an image for the warbox. Given in the form
Example.jpg - image_size – optional – a size for the image
- alt – optional – Alternative text for image that is accessible to screen readers to help the visually impaired
- caption – optional – the text to be placed below the image.
- date – optional – 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.
- coordinates – optional – 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_typeparameter. - map_type – optional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
- map_relief – optional – "yes" if the location map is a relief map; see {{location map}} for more details.
- map_size – optional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
- map_mark – optional – the name of a file to use as the location map marker, e.g. Green_pog.svg; defaults to: "Red_pog.svg".
- map_marksize – optional – width of the location map marker in pixels (px), e.g. "10"; defaults to: "8".
- map_caption – optional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
- map_label – optional – the label placed next to the marker on the location map.
- territory – optional – any changes in territorial control as a result of the conflict; this should not be used for overly lengthy descriptions of the peace settlement.
- action – optional – 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.
- result – optional – 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.
- status – optional – for ongoing conflicts, the current status of the conflict. This should not be used if a final result (above) is provided.
- combatants_header – optional – sets the header text for the combatants section. Default is "Belligerents". In case of Coup d'État, use "Government-Insurgents "
- combatant1/combatant2/combatant3 – optional – 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/combatant3a – optional – 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/combatant3b – optional – additional row, as above.
- combatant1c/combatant2c/combatant3c – optional – additional row, as above.
- combatant1d/combatant2d/combatant3d – optional – additional row, as above.
- combatant1e/combatant2e/combatant3e – optional – additional row, as above.
- commander1/commander2/commander3 – optional – 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/commander3a – optional – 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/commander3b – optional – additional row, as above.
- commander1c/commander2c/commander3c – optional – additional row, as above.
- commander1d/commander2d/commander3d – optional – additional row, as above.
- commander1e/commander2e/commander3e – optional – additional row, as above.
- units1/units2/units3 – optional – 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/strength2 – optional – the numerical strength of the units involved.
- polstrength1/polstrength2 – optional – In case of Coup d'Etat, political organizations that supported the government (1) respective the insurgents (2).
- milstrength1/milstrength2 – optional – In case of Coup d'Etat, military units that supported the government (1) respective the insurgents (2).
- strength3 – optional – 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/casualties2 – optional – casualties 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.
- casualties3 – optional – 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.
- notes – optional – optional field for further notes; this should only be used in exceptional circumstances.
- campaignbox – optional – 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}}
{{Infobox military conflict
...
| campaignbox = {{campaignbox XXXX}}
}}
Articles may include multiple campaignboxes; typically, these are stacked under the infobox. The most common scenario occurs when two levels of campaignboxes are present – for example, an article about a battle can include both a campaignbox listing the battle itself and an "enclosing" campaignbox listing the campaign, theater or war during which the battle took place. Similarly, an article about a war can include both a campaignbox listing the war (among a series of wars) and a campaignbox for the war itself, listing the battles that took place during it.
Creating campaignboxes
Existing campaignboxes may be viewed through the Campaignbox template category to which campaignboxes are added automatically. If a new campaignbox becomes necessary, it should be named Template:Campaignbox XXXX (where XXXX is the (shortened) name of the campaign) and should use {{Campaignbox}} thus:
{{Campaignbox
| name =
| title =
| battles =
| notes =
}}
Parameters
- name
- The name by which Wikipedia refers to the template, i.e. "Template:Campaignbox XXXX". This can be produced by using
{{subst:PAGENAME}}. - title
- The name of the campaign or war, which, if an article about the campaign or war exists, should link to it. Dates should not be indicated unless needed for clarity. Note that long links may cause alignment problems; see the troubleshooting guide for more information.
- battles
- A chronological list of battles and operations in the campaign, linked as
[[Battle of YYYY|YYYY]]. A convenient and accessible way to separate the items in the list is to add| listclass = hlistand then use the standard * (asterisk)-based listing format. - notes
- (optional) Any explanatory notes needed to clarify the list. This option should be used sparingly.
- (raw_name)
- (optional; deprecated) This parameter overrides the use of the title in determining the template name and exists for the sake of backward compatibility. When creating a new campaignbox, both title and name should be specified as above and this parameter omitted.
The following optional parameters are passed on to the templates {{Military navigation}} or {{Navbox}} used to create campaignboxes and so can affect their styling. See these two templates' documentation pages for further details.
- state
- To set whether the campaignbox appears fully visible or collapsed (to titlebar only) when it is first presented by a page.
- bodyclass
- CSS styling to affect the whole template.
- listclass
- CSS styling to affect the list of battles, operations, etc. (e.g. to affect
|battles=).
The use of special formatting (such as bolding or changes in font size) in the list of battles – particularly to mark battles as "important" – is generally discouraged; while there are a few cases where such approaches may be both helpful to the reader and sufficiently well-sourced that they do not constitute original research, they are usually both unnecessary and potentially confusing. Similarly, dividing the list of battles into multiple blocks by inserting heading-like separations should be exceptional; if such a division is felt to be needed, a better solution may be to split the one campaignbox into two or more.
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
Template loop detected: Template:Parameter names example
{{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 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]]
}}
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.
- partof – optional – the larger conflict containing the event described in the article.
- image – optional – an image for the warbox. Given in the form
File:Example.jpg - image_upright – optional – image upright scaling factor.
- alt – optional – Alternative text for image that is accessible to screen readers to help the visually impaired
- caption – optional – the text to be placed below the image.
- location – optional – the location of the operation.
- coordinates – optional – 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_typeparameter. If coordinates for several locations are given, consider if hany shall have the title display. - map_type – optional – the base map to be used for the location map, e.g. "Scotland"; see {{location map}} for more details.
- map_size – optional – width of the location map in pixels (px), e.g. "150"; defaults to: "220".
- map_caption – optional – caption displayed below the location map; defaults to "Location within {{{map_type}}}", e.g. "Location within Scotland".
- map_label – optional – the label placed next to the marker on the location map.
- scope – optional – the scope of the operation, such as "Strategic", "Operational", or "Tactical".
- type – optional – as an alternative to the scope field above, the type of operation, such as "Suicide attack" or "Ambush".
- planned – optional – the date(s) on which the plan was developed.
- planned_by – optional – the person or group responsible for developing the plan.
- commanded_by – optional – the person commanding the operation.
- objective – optional – the objective(s) of the operation.
- target – optional – as an alternative to the objective field above, the target(s) of the operation.
- date – optional – the date(s), if any, on which the operation was executed. use {{Start date}} (and {{End date}} if required)
- time – optional – the time, if any, at which the operation was executed.
- time-begin and time-end – optional – as an alternative to the time field above, the start and end times, respectively.
- timezone – optional – the timezone of the location of the operation; UTC+X, UTC-X, or UTC (i.e. offset from UTC) is preferred.
- executed_by – optional – the people, groups, units, or formations responsible for executing the operation.
- outcome – optional – the outcome of the operation from the perspective of the planners with a very brief summary of defence if appropriate.
- casualties – optional – any casualties occurring during the execution of the operation.
- fatalities – optional – as an alternative to the casualties field above, the number of fatalities occurring during the execution of the operation.
- injuries – optional – 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
nor collapse nested elements which use them.
TemplateData
|
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.
| ||||||||||
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
TemplateData for WikiProject Military history
TemplateData
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Summarize information about a particular military conflict (a battle, campaign, war, or group of related wars).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See also
| This template is used on many pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
| This template uses Lua: |
| This template does not display in the mobile view of Wikipedia; it is desktop only. Read the documentation for an explanation. |
Templates using the classes class=navbox ({{navbox}}) or class=nomobile ({{sidebar}}) are not displayed on the mobile web site of English Wikipedia. Mobile page views account for approximately 66% of all page views (90-day average as of January 2024[update]).
Usage
Campaignboxes
One common type of navigational template in articles concerning conflicts, wars and related topics is the campaignbox template, intended to provide context and convenient navigation among articles on the battles in a campaign, front, theater or war (or, more rarely, among several campaigns or wars).
If the article includes an infobox, the campaignbox/es are usually placed immediately after it (i.e. just below it). If available, as with infoboxes such as {{Infobox military conflict}}, use the infobox's |campaignbox= parameter:
{{Infobox military conflict
...
}}
{{Campaignbox XXXX}}
{{Infobox military conflict
...
| campaignbox = {{campaignbox XXXX}}
}}
Articles may include multiple campaignboxes; typically, these are stacked under the infobox. The most common scenario occurs when two levels of campaignboxes are present – for example, an article about a battle can include both a campaignbox listing the battle itself and an "enclosing" campaignbox listing the campaign, theater or war during which the battle took place. Similarly, an article about a war can include both a campaignbox listing the war (among a series of wars) and a campaignbox for the war itself, listing the battles that took place during it.
Creating campaignboxes
Existing campaignboxes may be viewed through the Campaignbox template category to which campaignboxes are added automatically. If a new campaignbox becomes necessary, it should be named Template:Campaignbox XXXX (where XXXX is the (shortened) name of the campaign) and should use {{Campaignbox}} thus:
{{Campaignbox
| name =
| title =
| battles =
| notes =
}}
Parameters
- name
- The name by which Wikipedia refers to the template, i.e. "Template:Campaignbox XXXX". This can be produced by using
{{subst:PAGENAME}}. - title
- The name of the campaign or war, which, if an article about the campaign or war exists, should link to it. Dates should not be indicated unless needed for clarity. Note that long links may cause alignment problems; see the troubleshooting guide for more information.
- battles
- A chronological list of battles and operations in the campaign, linked as
[[Battle of YYYY|YYYY]]. A convenient and accessible way to separate the items in the list is to add| listclass = hlistand then use the standard * (asterisk)-based listing format. - notes
- (optional) Any explanatory notes needed to clarify the list. This option should be used sparingly.
- (raw_name)
- (optional; deprecated) This parameter overrides the use of the title in determining the template name and exists for the sake of backward compatibility. When creating a new campaignbox, both title and name should be specified as above and this parameter omitted.
The following optional parameters are passed on to the templates {{Military navigation}} or {{Navbox}} used to create campaignboxes and so can affect their styling. See these two templates' documentation pages for further details.
- state
- To set whether the campaignbox appears fully visible or collapsed (to titlebar only) when it is first presented by a page.
- bodyclass
- CSS styling to affect the whole template.
- listclass
- CSS styling to affect the list of battles, operations, etc. (e.g. to affect
|battles=).
The use of special formatting (such as bolding or changes in font size) in the list of battles – particularly to mark battles as "important" – is generally discouraged; while there are a few cases where such approaches may be both helpful to the reader and sufficiently well-sourced that they do not constitute original research, they are usually both unnecessary and potentially confusing. Similarly, dividing the list of battles into multiple blocks by inserting heading-like separations should be exceptional; if such a division is felt to be needed, a better solution may be to split the one campaignbox into two or more.
Template loop detected: Wikipedia:WikiProject Military history/Unitbox
Categories
The diagram below provides an overview of the category scheme used for wars and battles. Categories are shown in plain text, while articles are shown in bold.
Wars | | Battles Wars by country | | | ,------------+-----------------. ,------------+----------------. | | | | Wars of England Wars of France Battles by country Battles by type | | | | | | | `------------+-------------' | `----+-----' `--------. Sieges | | | | | | | | | | Hundred Years' War Fronde Battles of France Battles of England | | | | | | ,------------+---------------------. `----------+--------' `----+---' | | | | Hundred Years' War | | Siege of York Battles of the Hundred Years' War | Battle of Agincourt
- Wars are categorized primarily by the participating countries (under sub-categories of Category:Wars by country).
- Major wars have dedicated categories (e.g. Category:Hundred Years' War, which are placed under the appropriate country categories.
- Battles are categorized by the participating countries (under sub-categories of Category:Battles by country), by war (under sub-categories of Category:Battles by war), and by type (under sub-categories of Category:Battles by type).
- Battle categories are nested in the corresponding war categories. For instance, Category:Battles of England is a sub-category of Category:Wars of England. Likewise, Category:Battles of the Hundred Years' War is a sub-category of Category:Hundred Years' War.
Please note that there are numerous exceptions and special cases (not shown here) that exist as a matter of convention. If you find a category that seems out of place, it's often useful to ask before trying to move it; there could be a very good reason for its peculiar structure or location.
Project organization
Coordinators
The project coordinators are generally responsible for maintaining the procedural aspects of the project, and serve as the designated points-of-contact for procedural issues. They are not, however, endowed with any executive powers.
The Lead Coordinator has overall responsibility for all procedural and administrative matters within the project, while the Assistant Coordinators focus on specific areas that require special attention.
Lead Coordinator
- To be named after the election concludes.
Assistant Coordinators
Members
Please feel free to add your name to this list if you would like to join the project.
- Adam Bishop (mostly Crusades, some Byzantine and other medieval stuff)
- Abduncan4 (WWII-European and Pacific Theatres, Vietnam War, American Civil War, All American Conficts, also 30 Years War and War of Spanish Succession)
- Albrecht
- Alexander 007 (various)
- ALKIVAR™
(World War II aircraft mostly B-26 Marauder related) - Amir85 (Persian wars in general and Sassanid wars in particular)
- Andreas (World War II, in particular eastern front and Normandy)
- Andres C. (WW1 & 2; South America)
- Anittas - mostly southeastern European battles, but also from other parts of Europe
- Ansbachdragoner (From War of Spanish Succession thru Napoleonic Wars - European, Also WWII ETO [in order of Pref. Eastern, Western and Mediterranean fronts] - Republican Roman c.Punic Wars thru Augustus.)
- bd84 (WW2, military equipment)
- Bedford (American Revolution thru War Between The States)
- Ben D. (Updating Battleboxes)
- Bennmorland (General interest, way too much minutiae in his head. Loves to edit, and proofread. Is otherwise an odd person.)
- H.L.S. Blair (Battle of Tours; Carolinian Empire)
- BlueShirts (Second Sino-Japanese War, Chinese Civil Wars)
- brian0918™ (American Civil War: Battleboxes, Categories, etc.)
- Briangotts (talk) (primarily battles involving Eurasian nomad armies; see, e.g., Battle of Marj Ardebil)
- Bukvoed (mostly military equipment)
- Carptrash - Has a history degree in a trunk, somewhere, that's older than most of the New Mexico histroy that he studies.
- Catalan (talk) (I have an interest in all military history; current project is the Second Battle of Kharkov.)
- CNSW (Ancient Greece (around 4th century BC)
- Bigman (mainly medieval castle sieges in England, but really general info)
- Craig Stuntz (Jacobite rising, especially the Battle of Prestonpans. Will also accept whisky, preferably Talisker :)
- Ctifumdope
- SSG Cornelius Seon (Retired) (Primarily US Army unit histories; insignia; and data.)
- Durova (primarily women's participation in warfare and the Hundred Years War, abundant trivia on other subjects)
- Dvyost (Battles of medieval Africa)
- Eclecticology (suggested a wikiproject battles)
- εγκυκλοπαίδεια* (talk)
- evrik (American Civil War)
- Fra Paolo (Warfare in Ancient Greece, tactical effects of technological interactions on warfare since c. 1850)
- Geira (Wide range of interests. Pet project: A common XML-based format for Orders of Battle. Will code for Highland Park)
- Gentgeen (primarily North America, adding battleboxes to anything I find)
- GregRog (Austria-Hungary in WWI for now..)
- Gsl
- Guapovia (Fighter aircraft, 1910-1994)
- Habap (19th & 20th century, plus general editing. Prefers scotch as payment)
- Halibutt (mostly 20th century battles in Poland and Central Europe)
- Hlj (Hal Jespersen) (American Civil War battles, campaigns, overviews, and biographies)
- Hossen27 (Australian Military History and World War 1 & 2)
- Inge (Mostly Norway)
- Jbetak (Presidio of San Francisco, WW II - European theater)
- JimmyTheOne (Naval history, mostly 18th and 20th centuries)
- Jniemenmaa (Finnish military history. Also ancient and byzantine warfare.)
- Kirill Lokshin (15th–18th century Europe and general organization)
- Kross (no specific era, really)
- ktsquare (suggested a wikiproject battles)
- Lay (Occasional contributor, mostly about cavalry and ancient warfare. Among other things. I'm hoping to extend this into the representation of warfare in fiction)
- Leithp (20th century wars, but mostly WWII)
- Link the windwaker (Fighter and bomber aircraft, also 20th century wars)
- llywrch (Currently working on battles fought in/by/around Ethiopia)
- Looper5920 (American Military History)
- Loopy (British military history mostly - battles in 19th and early 20th a main interest)
- LordAmeth (Japanese history, particularly pre-Meiji)
- Mackensen (First World War)
- Martorius (Mostly work on WWII articles.)
- mav (mostly helping to organize things - I wish I had time for more)
- Messhermit (Soviet-Afghan War - Currently working in several bio's of the main characters involved. Will detail more about the war itself later)
- Miborovsky (working on Chinese battles and military, particularly those of the Second Sino-Japanese war)
- MatthewMitchell (very solid knowledge on American Civil War, WWII, American involvement in Latin America, some post-Cold War conflicts, with helpful general knowledge on causes, practices and effects of WWI, Korean Conflict, Desert Storm, Vietnam, American Independence, Mexican Revolution, and others)
- Mike McGregor (Canadian Mil-history, great lakes military history, French & indian wars, wwI and wwII)
- Mohnish Kamat (Primarily work on battles in Ancient India, also 14th - 19th century battles in and around the Indian Ocean)
- MoRsE (WW2, military equipment, military intelligence)
- Michael Stimson (European History, Napoleonic, Colonial Wars)
- Neutrality (talk) (Battle Boxes, American battles)
- Nick Dowling (Australian military units and military history)
- Oberiko (World War II, military equipment, categorization)
- oldwindybear (Battle of Tours, Carolinian Empire; Roman Empire, Mongols)
- P.MacUidhir (mostly copyedits, fact checking, adding citations/references)
- Phaedriel (generally, Military History of the U.S., currently with a strong focus on Indian Wars)
- R.D.H. (Ghost In The Machine) (Mainly the Roman and Napoleonic eras and WWII. But is interested in all periods and aspects. Also enjoys making battleboxes and will accept beer as payment :)
- Rhion (Roman and Welsh mediaeval)
- Robth (Classical antiquity, 5th and 4th century Greece in particular)
- rogerd (Pre- U.S. Civil War conficts (including American Revolution), World War II, Military Aircraft of any period)
- Roman Babylon (Medieval Warfare mostly, modern day combat as well)
- Rshu (Self proclaimed new member/worked much on Military history of Germany/enjoys correcting stubs on Roman/Medieval/Enlightenment Age-Modern Day)
- Rusty2005 (General Nineteenth and Twentieth centuries, focusing on Africa, China, India, and Europe)
- Sabrebattletank (proofreader, editor, can do anything)
- Searchme
- Semprini (WWI, WWII, Dutch history)
- Spawn Man (Self proclaimed new member greeter/WWI/Anything else)
- SoLando (Generally working on British-related battles of the Napoleonic Wars, rest of the 19th Century, and WWI and WWII)
- Staxringold (minor stuff, working on Battle of Amiens right now)
- szopen (created list of battles)
- Tanzburg (Generalist with primary interest in WW1 and a growing interest in Central & Eastern Europe)
- TeunSpaans
- The Half Gauntlet
- The Minister of War (Generalist, though main interest lies in medieval Europe or Asia. I'd be happy to help do some editing)
- Thmars10 (Edit with what knowledge I have. Willing to do some research and some cleaning upping)
- Tpower
- TSO1D (intersted in European/Western Conflicts throughout history)
- vidarlo (Mostly WWII in Western Norway, will edit what I see though)
- WangKon936 (Although my interests in Military History are varied, I will, for the time being, focus on Korean Military History as it is so little known outside of Asia.)
- Wendell (Plan to peer review articles. Likes to organize. )
- Wikiacc (talk) (Mostly battleboxes)
- Wurkwurk
Development
Task forces
This section is currently under development.
Task forces are informal groups of editors gathered for collaborative work on a particular topic. There is currently one active task force:
- Canadian military history - currently looking for members.
For the time being, please discuss potential task forces with the project before creating them.
Work in progress
- Work list - a list of important articles that may require further improvement.
- Wanted articles - a list, collected from various sources, of non-existent articles that need to be written.
- New articles - a list of newly created military history articles.
Current discussions
Archive
- Battlebox usage instructions (pre-November 2005)
- Battlebox colour scheme (pre-August 2005)
- Campaignbox proposal and alternatives (November 2004)
Resources
Related projects
- Falklands War - the Falklands War.
- Military - current military issues.
- British Army - armed forces of the United Kingdom.
- Hellenic Army - armed forces of Greece.
- Polish Army - armed forces of Poland
- Ships - ships, including naval vessels.
- Vietnam War (inactive) - the Vietnam War.
- World Wars - World War I and World War II.
Internal resources
The following articles may be helpful aids for an editor of a military history article:
- Glossary of German WWII military terms
- List of equipment used in World War II
- List of established military terms
- List of military tactics
- List of modern AFV and artillery related terms and acronyms
- List of modern infantry related terms and acronyms
- List of Roman military terms
- List of Grande Armée Slang terms
- List of World War II electronic warfare equipment
- Naming conventions (military units)
- Various military lists (maintained by the Military WikiProject)
External resources
- The online bookshelves of the U.S. Army's Center for Military History
- The Naval Historical Center of the U.S. Navy.
- An archive of old issues of Naval Aviation News maintained by the U.S. Navy.
- Fields of Conflict - an American Civil War research and discussion group.
- OnWar - A general purpose military site with a focus on World War II.
Auxiliary templates
Category description
| Template | Result |
|---|---|
| {{Battle category by participant}} Placed on sub-categories of Category:Battles by country |
This category includes historical battles in which COUNTRY (CREATED–DESTROYED) participated. Please see the category guidelines for more information. |
| {{Battle category by conflict}} Placed on sub-categories of Category:Battles by war |
This category contains historical battles fought as part of the WAR. Please see the category guidelines for more information. |
| {{War category by participant}} Placed on sub-categories of Category:Wars by country |
This category includes historical wars in which {{{1}}} ({{{2}}}–{{{3}}}) participated. Please see the category guidelines for more information. |
Project notice
| Template | Result | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {{WikiProject Military history}} Placed on article talk page |
Please add {{WikiProject banner shell}} to this page and add the quality rating to that template instead of this project banner. See WP:PIQA for details.
| ||||||||||||||||||||||||
| {{WikiProject Military history category}} Placed on category page |
Template:WikiProject Military history category | ||||||||||||||||||||||||
| {{WikiProject Military history template}} Placed on template talk page |
Template:WikiProject Military history template | ||||||||||||||||||||||||
| {{WikiProject Military history user}} Placed on user or user talk page |
Template:WikiProject Military history user | ||||||||||||||||||||||||
| {{User WikiProject Military history}} Userbox, placed on user page |
| ||||||||||||||||||||||||
Stubs
Other
| Template | Result | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {{WikiProject Military history tasks}} (large version) {{Milbox}} (small version) |
| |||||||||||||||||||||||
| {{History of war}} |
| |||||||||||||||||||||||
.jpg)
{{Infobox military unit
| unit_name =
| native_name =
| image =
| image_size =
| alt =
| caption =
| dates = <!-- or | start_date = | end_date = -->
| disbanded =
| country = <!-- or | countries = -->
| allegiance =
| branch =
| type =
| role = <!-- or | specialization = -->
| size =
| command_structure =
| garrison =
| garrison_label =
| nickname =
| patron =
| motto =
| colors = <!-- or | colours = -->
| colors_label = <!-- or | colours_label = -->
| march =
| mascot =
| anniversaries =
| equipment =
| equipment_label =
| battles =
| battles_label =
| decorations =
| battle_honours =
| battle_honours_label =
| flying_hours =
| website =
<!-- Commanders -->
| current_commander =
| commander1 =
| commander1_label =
| commander2 =
| commander2_label =
| commander3 =
| commander3_label =
| commander4 =
| commander4_label =
| commander5 =
| commander5_label =
| commander6 =
| commander6_label =
| commander7 =
| commander7_label =
| commander8 =
| commander8_label =
| commander9 =
| commander9_label =
| notable_commanders =
<!-- Insignia -->
| identification_symbol =
| identification_symbol_label =
| identification_symbol_2 =
| identification_symbol_2_label =
| identification_symbol_3 =
| identification_symbol_3_label =
| identification_symbol_4 =
| identification_symbol_4_label =
| identification_symbol_5 =
| identification_symbol_5_label =
| identification_symbol_6 =
| identification_symbol_6_label =
<!-- Aircraft -->
| aircraft_attack =
| aircraft_bomber =
| aircraft_electronic =
| aircraft_fighter =
| aircraft_helicopter =
| aircraft_helicopter_attack =
| aircraft_helicopter_cargo =
| aircraft_helicopter_multirole =
| aircraft_helicopter_observation =
| aircraft_helicopter_trainer =
| aircraft_helicopter_utility =
| aircraft_interceptor =
| aircraft_patrol =
| aircraft_recon =
| aircraft_trainer =
| aircraft_transport =
| aircraft_tanker =
| aircraft_general =
}}
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).
- unit_name – The formal name of the unit in English.
- native_name – optional – The formal name of the unit in the local language, if different from unit_name, and if not English. This will display under the unit_name.
- image – optional – An image of the unit insignia (cap badges, tartan or colours), if available; other images may be used if this cannot be obtained. The image should be given in the form
Example.jpg. - image_size – optional – Used to override the default image width of 200 pixels. It should be written as
200px. - alt – optional – Alternative text for visually impaired users, see WP:ALT.
- caption – optional – The text to be placed below the image.
- dates – The period (usually in years) when the unit was active; alternately, the dates may be indicated by using one—or both—of the separate start_date and end_date parameters.
- country – optional – If the unit is part of the armed forces of a sovereign state, the name of that state.
- allegiance – optional – Used to indicate the allegiance of units which are not part of the regular armed forces of a sovereign state; can usually be omitted otherwise. In the case of National Guard or Naval Militia units, the State of origin should be indicated.
- branch – optional – The service branch, in militaries that have them; typically army, navy, air force, etc.
- type – optional – The general type of unit, e.g., cavalry, infantry, artillery, etc. More specific types (airborne infantry, light cavalry, etc.) may be given as appropriate.
- role – optional – Typical strategic or tactical use of unit, e.g., shock troop, special operations, mechanized infantry, ceremonial guard, etc.
- size – optional – The size of the unit; this may include both average and lifetime figures, and should indicate equipment (planes, tanks, cannon, etc.) where applicable. For U.S. units, this should only include Organic elements, not Assigned or Attached elements.
- command_structure – optional – The larger unit(s) of which the unit is a part. This should not be used to provide an exhaustive history of the unit, which is more appropriate in the article itself, for units existing over a long period. For complicated cases, using the auxiliary command structure box may be appropriate.
- garrison – optional – Location of the unit's home base; this is generally applicable only to units in existence.
- garrison_label – optional – The label to use for the garrison field (above).
- nickname – optional – Any commonly-used nicknames for the unit.
- patron – optional – The patron the unit was named after; this is only applicable in armed forces where units are named after individuals.
- motto – optional – The official unit motto (with translation, if necessary).
- colors – optional – The unit colors; this may refer to either the actual colors used on the uniform, or to the colours of the unit.
- colors_label – optional – the label to use for the colors field (above).
- march – optional – The tune(s) commonly or officially played when the unit ceremonially marches; there may be several.
- mascot – optional – Any official or unofficial animal or character maintained by the unit.
- equipment – optional – For units strongly associated with specific equipment or vehicles, such as tanks, artillery, or aircraft, a brief list of the notable types used by the unit; if the number of entries is large, it is recommended that this field not be used, and that the full list be given in the article text instead.
- equipment_label – optional – The label to use for the equipment field (above).
- battles – optional – Any notable engagements in which the unit participated. The decision of what constitutes a notable engagement is left to the editors of the specific article.
- battles_label – optional – The label to use for the battles field (above); this defaults to "Engagements" if left blank.
- anniversaries – optional – Any anniversaries that a unit celebrates.
- decorations – optional – Any decorations (such as the Presidential Unit Citation) that the unit as a whole has received.
- battle_honours – optional – For units in countries that award some type of formal battle honours, the battle honours that the unit has received; while this may have some overlap with the battles field above, the two are not necessarily equivalent.
- battle_honours_label – optional – The label to use for the battle_honours field (above); this defaults to "Battle honours" if left blank.
- disbanded – optional – For units that have been disbanded, the dates and any other relevant notes regarding the disbanding.
- flying_hours – optional – If the formation is an aerial one, the total hours flown.
- website – optional – The official website of the formation, if any.
Commander parameters:
The infobox allows for up to three current commanders to be specified; the exact roles or titles of these individuals should be specified via the corresponding label parameters.
- commander1 – optional – A current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander1_label – optional – The label to use for the field above; for historical reasons, this defaults to "Current commander" if left blank.
- commander2 – optional – A second current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander2_label – optional – The label to use for the field above; for historical reasons, this defaults to "Ceremonial chief" if left blank.
- commander3 – optional – A third current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander3_label – optional – The label to use for the field above; for historical reasons, this defaults to "Colonel of the Regiment" if left blank.
- commander4 – optional – A fourth current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander4_label – optional – The label to use for the field above; for historical reasons, this defaults to "Command Sergeant Major" if left blank.
- commander5 – optional – A fifth current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander5_label – optional – The label to use for the field above; defaults to "Commander".
- commander6 – optional – A sixth current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander6_label – optional – The label to use for the field above; defaults to "Commander".
- commander7 – optional – A seventh current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander7_label – optional – The label to use for the field above; defaults to "Commander".
- commander8 – optional – An eighth current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander8_label – optional – The label to use for the field above; defaults to "Commander".
- commander9 – optional – A ninth current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
- commander9_label – optional – The label to use for the field above; defaults to "Commander".
- notable_commanders – optional – Any notable former commanders of the unit; judgement of notability is left to individual article editors.
Insignia parameters:
- identification_symbol – optional – The unit's identification symbol (such as a tartan, tactical identification patch or morale patch).
- identification_symbol_label – optional – The label to use for the identification symbol field (above).
- identification_symbol_2 – optional – Another identification symbol.
- identification_symbol_2_label – optional – The label to use for the second identification symbol field (above).
- identification_symbol_3 – optional – Another identification symbol.
- identification_symbol_3_label – optional – The label to use for the third identification symbol field (above).
- identification_symbol_4 – optional – Another identification symbol.
- identification_symbol_4_label – optional – The label to use for the fourth identification symbol field (above).
- identification_symbol_5 – optional – Another identification symbol.
- identification_symbol_5_label – optional – The label to use for the fifth identification symbol field (above).
- identification_symbol_6 – optional – Another identification symbol.
- identification_symbol_6_label – optional – The label to use for the sixth identification symbol field (above).
Aircraft parameters:
- aircraft_attack – optional – For aviation units, the attack aircraft flown by the unit.
- aircraft_bomber – optional – For aviation units, the bomber aircraft flown by the unit.
- aircraft_electronic – optional – For aviation units, the electronic warfare aircraft flown by the unit.
- aircraft_fighter – optional – For aviation units, the fighter aircraft flown by the unit.
- aircraft_helicopter – optional – For aviation units, the helicopter aircraft flown by the unit.
- aircraft_helicopter_attack – optional – For aviation units, the attack helicopter aircraft flown by the unit.
- aircraft_helicopter_cargo – optional – For aviation units, the cargo helicopter aircraft flown by the unit.
- aircraft_helicopter_multirole – optional – For aviation units, the multirole helicopter aircraft flown by the unit.
- aircraft_helicopter_observation – optional – For aviation units, the observation helicopter aircraft flown by the unit.
- aircraft_helicopter_trainer – optional – For aviation units, the trainer helicopter aircraft flown by the unit.
- aircraft_helicopter_utility – optional – For aviation units, the utility helicopter aircraft flown by the unit.
- aircraft_interceptor – optional – For aviation units, the interceptor aircraft flown by the unit.
- aircraft_patrol – optional – For aviation units, the patrol aircraft flown by the unit.
- aircraft_recon – optional – For aviation units, the reconnaissance aircraft flown by the unit.
- aircraft_trainer – optional – For aviation units, the trainer aircraft flown by the unit.
- aircraft_transport – optional – For aviation units, the transport aircraft flown by the unit.
- aircraft_tanker – optional – For aviation units, the aerial refueling aircraft flown by the unit.
- aircraft_general – optional – For aviation units, where aircraft used do not fit well into the above categories.
Note that the various xyz_label fields above are intended for overriding the default labels on these fields as needed for particular countries or services; in most cases, however, the default value is sufficient, and the fields need not be included.
| This template uses Lua: |
Command structure box
A command structure box may be used to summarize information about an individual military unit's parent and subordinate units; it should generally be used in conjunction with {{Infobox military unit}}. If needed, multiple boxes may be used to show the unit's command structure during different periods.
The box should be added using the {{Infobox command structure}} template, as shown below:
{{Infobox command structure
| name =
| date =
| parent =
| subordinate =
}}
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 unit or formation.
- date – optional – the dates during which the given structure was in place.
- parent – optional – the unit's parent unit.
- subordinate – optional – the unit's subordinate units.
Infobox service record
| Combat service | |
|---|---|
| Part of | 7. Unterseebootsflottille (1938–41) |
| Identification codes | M 18 837 (feldpost) |
| Commanders | Günther Prien (1938–41) |
| Operations | 10 patrols |
| Victories |
30 ships (162,769 GRT) sunk, 1 warship (29,150 tons) sunk, 8 ships (62,751 GRT) damaged |
A service record box may be used to summarize information about an individual military unit's or ship's service history; it should generally be used in conjunction with the appropriate primary infobox. If needed, multiple boxes may be used to separate the service record for different periods; for example, a unit that fought in several wars may have separate boxes for each.
The box should be added using the {{Infobox service record}} template, as shown below:
{{Infobox service record
| is_ship =
| is_multi =
| label =
| partof =
| codes =
| commanders =
| operations =
| victories =
| awards =
}}
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).
- is_ship – optional – "yes" if the box is being used inside a compound ship infobox.
- is_multi – optional – "yes" if multiple instances of the box are being used inside a single compound ship infobox.
- label – optional – the label to use for the box; this defaults to "Service record" if left blank.
- partof – optional – the unit or formation of which the subject unit or ship was a part; multiple units may be listed with the corresponding dates.
- codes – optional – the identification codes carried by the unit or ship; these should generally be labeled according to what the code indicates.
- commanders – optional – the notable commanding officers for the period covered.
- operations – optional – the operations (such as battles, wars, campaigns, patrols, cruises, etc.) in which the subject unit or ship participated; these may be given as a list, or described in a more condensed form.
- victories – optional – the victories or successes in the subject's service history. For units, this may be battles won; for submarines or merchant raiders, the ships and tonnage sunk; and so forth.
- awards – optional – the awards, decorations, or other honors received by the subject unit or ship.
Example
| 502nd Parachute Infantry Regiment | |
|---|---|
 502d PIR Coat of Arms | |
| Active | 1942–present |
| Country | United States |
| Branch | Army |
| Type | Parachute infantry |
| Part of | 101st Airborne Division |
| Garrison/HQ | Fort Campbell |
| Nickname(s) | "Five-Oh-Deuce" or "The Deuce" |
| Motto(s) | Strike |
| Engagements | World War II |
| Decorations | |
| Commanders | |
| Notable commanders | |
{{Infobox military unit
| unit_name = 502nd Parachute Infantry Regiment
| image = 502 Parachute Infantry Regiment COA.PNG
| caption = 502d PIR Coat of Arms
| nickname = "Five-Oh-Deuce" or "The Deuce"
| motto = ''Strike''
| colors =
| march =
| ceremonial_chief =
| type = [[Parachute infantry]]
| branch = [[United States Army|Army]]
| dates = 1942–present
| country = United States
| allegiance =
| command_structure = [[101st Airborne Division]]
| size =
| specialization =
| current_commander =
| garrison = [[Fort Campbell]]
| garrison_label =
| battles = World War II
*[[Western Front (World War II)|European War]]
*[[Invasion of Normandy|Battle of Normandy]]
*[[Operation Market Garden]]
*[[Battle of the Bulge]]
[[War on Terrorism]]
*[[Iraq War]]
**[[Operation Iraqi Freedom]]
| notable_commanders = {{unbulleted list|[[George V. H. Moseley, Jr.]]|[[John H. Michaelis]]}}
| anniversaries =
| decorations = {{unbulleted list|[[Presidential Unit Citation (United States)|Presidential Unit Citation]] (5)|[[Valorous Unit Award]] (5)|[[Croix de Guerre]]}}
}}
Microformat
The HTML mark-up produced by this template includes an hCard microformat that makes an organization's 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.
- Subtemplates
- Use {{Start date and age}} for the date on which an organisation was "established", "founded", "opened" or otherwise started, unless that date is before 1583 CE.
- Use {{URL}} for an organisation's URL.
Please do not remove instances of these subtemplates.
- Classes used
The HTML classes of this microformat include:
- adr
- agent
- category
- country-name
- extended-address
- fn
- geo
- label
- latitude
- locality
- longitude
- nickname
- note
- org
- region
- street-address
- url
- vcard
nor collapse nested elements which use them.
TemplateData
TemplateData documentation used by 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 A military unit infobox may be used to summarize information about an individual military unit or formation, such as a regiment or division.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Tracking cats
Categories
The diagram below provides an overview of the category scheme used for wars and battles. Categories are shown in plain text, while articles are shown in bold.
Wars | | Battles Wars by country | | | ,------------+-----------------. ,------------+----------------. | | | | Wars of England Wars of France Battles by country Battles by type | | | | | | | `------------+-------------' | `----+-----' `--------. Sieges | | | | | | | | | | Hundred Years' War Fronde Battles of France Battles of England | | | | | | ,------------+---------------------. `----------+--------' `----+---' | | | | Hundred Years' War | | Siege of York Battles of the Hundred Years' War | Battle of Agincourt
- Wars are categorized primarily by the participating countries (under sub-categories of Category:Wars by country).
- Major wars have dedicated categories (e.g. Category:Hundred Years' War, which are placed under the appropriate country categories.
- Battles are categorized by the participating countries (under sub-categories of Category:Battles by country), by war (under sub-categories of Category:Battles by war), and by type (under sub-categories of Category:Battles by type).
- Battle categories are nested in the corresponding war categories. For instance, Category:Battles of England is a sub-category of Category:Wars of England. Likewise, Category:Battles of the Hundred Years' War is a sub-category of Category:Hundred Years' War.
Please note that there are numerous exceptions and special cases (not shown here) that exist as a matter of convention. If you find a category that seems out of place, it's often useful to ask before trying to move it; there could be a very good reason for its peculiar structure or location.
Project organization
Coordinators
The project coordinators are generally responsible for maintaining the procedural aspects of the project, and serve as the designated points-of-contact for procedural issues. They are not, however, endowed with any executive powers.
The Lead Coordinator has overall responsibility for all procedural and administrative matters within the project, while the Assistant Coordinators focus on specific areas that require special attention.
Lead Coordinator
- To be named after the election concludes.
Assistant Coordinators
Members
Please feel free to add your name to this list if you would like to join the project.
- Adam Bishop (mostly Crusades, some Byzantine and other medieval stuff)
- Abduncan4 (WWII-European and Pacific Theatres, Vietnam War, American Civil War, All American Conficts, also 30 Years War and War of Spanish Succession)
- Albrecht
- Alexander 007 (various)
- ALKIVAR™ (World War II aircraft mostly B-26 Marauder related)
- Amir85 (Persian wars in general and Sassanid wars in particular)
- Andreas (World War II, in particular eastern front and Normandy)
- Andres C. (WW1 & 2; South America)
- Anittas - mostly southeastern European battles, but also from other parts of Europe
- Ansbachdragoner (From War of Spanish Succession thru Napoleonic Wars - European, Also WWII ETO [in order of Pref. Eastern, Western and Mediterranean fronts] - Republican Roman c.Punic Wars thru Augustus.)
- bd84 (WW2, military equipment)
- Bedford (American Revolution thru War Between The States)
- Ben D. (Updating Battleboxes)
- Bennmorland (General interest, way too much minutiae in his head. Loves to edit, and proofread. Is otherwise an odd person.)
- H.L.S. Blair (Battle of Tours; Carolinian Empire)
- BlueShirts (Second Sino-Japanese War, Chinese Civil Wars)
- brian0918™ (American Civil War: Battleboxes, Categories, etc.)
- Briangotts (talk) (primarily battles involving Eurasian nomad armies; see, e.g., Battle of Marj Ardebil)
- Bukvoed (mostly military equipment)
- Carptrash - Has a history degree in a trunk, somewhere, that's older than most of the New Mexico histroy that he studies.
- Catalan (talk) (I have an interest in all military history; current project is the Second Battle of Kharkov.)
- CNSW (Ancient Greece (around 4th century BC)
- Bigman (mainly medieval castle sieges in England, but really general info)
- Craig Stuntz (Jacobite rising, especially the Battle of Prestonpans. Will also accept whisky, preferably Talisker :)
- Ctifumdope
- SSG Cornelius Seon (Retired) (Primarily US Army unit histories; insignia; and data.)
- Durova (primarily women's participation in warfare and the Hundred Years War, abundant trivia on other subjects)
- Dvyost (Battles of medieval Africa)
- Eclecticology (suggested a wikiproject battles)
- εγκυκλοπαίδεια* (talk)
- evrik (American Civil War)
- Fra Paolo (Warfare in Ancient Greece, tactical effects of technological interactions on warfare since c. 1850)
- Geira (Wide range of interests. Pet project: A common XML-based format for Orders of Battle. Will code for Highland Park)
- Gentgeen (primarily North America, adding battleboxes to anything I find)
- GregRog (Austria-Hungary in WWI for now..)
- Gsl
- Guapovia (Fighter aircraft, 1910-1994)
- Habap (19th & 20th century, plus general editing. Prefers scotch as payment)
- Halibutt (mostly 20th century battles in Poland and Central Europe)
- Hlj (Hal Jespersen) (American Civil War battles, campaigns, overviews, and biographies)
- Hossen27 (Australian Military History and World War 1 & 2)
- Inge (Mostly Norway)
- Jbetak (Presidio of San Francisco, WW II - European theater)
- JimmyTheOne (Naval history, mostly 18th and 20th centuries)
- Jniemenmaa (Finnish military history. Also ancient and byzantine warfare.)
- Kirill Lokshin (15th–18th century Europe and general organization)
- Kross (no specific era, really)
- ktsquare (suggested a wikiproject battles)
- Lay (Occasional contributor, mostly about cavalry and ancient warfare. Among other things. I'm hoping to extend this into the representation of warfare in fiction)
- Leithp (20th century wars, but mostly WWII)
- Link the windwaker (Fighter and bomber aircraft, also 20th century wars)
- llywrch (Currently working on battles fought in/by/around Ethiopia)
- Looper5920 (American Military History)
- Loopy (British military history mostly - battles in 19th and early 20th a main interest)
- LordAmeth (Japanese history, particularly pre-Meiji)
- Mackensen (First World War)
- Martorius (Mostly work on WWII articles.)
- mav (mostly helping to organize things - I wish I had time for more)
- Messhermit (Soviet-Afghan War - Currently working in several bio's of the main characters involved. Will detail more about the war itself later)
- Miborovsky (working on Chinese battles and military, particularly those of the Second Sino-Japanese war)
- MatthewMitchell (very solid knowledge on American Civil War, WWII, American involvement in Latin America, some post-Cold War conflicts, with helpful general knowledge on causes, practices and effects of WWI, Korean Conflict, Desert Storm, Vietnam, American Independence, Mexican Revolution, and others)
- Mike McGregor (Canadian Mil-history, great lakes military history, French & indian wars, wwI and wwII)
- Mohnish Kamat (Primarily work on battles in Ancient India, also 14th - 19th century battles in and around the Indian Ocean)
- MoRsE (WW2, military equipment, military intelligence)
- Michael Stimson (European History, Napoleonic, Colonial Wars)
- Neutrality (talk) (Battle Boxes, American battles)
- Nick Dowling (Australian military units and military history)
- Oberiko (World War II, military equipment, categorization)
- oldwindybear (Battle of Tours, Carolinian Empire; Roman Empire, Mongols)
- P.MacUidhir (mostly copyedits, fact checking, adding citations/references)
- Phaedriel (generally, Military History of the U.S., currently with a strong focus on Indian Wars)
- R.D.H. (Ghost In The Machine) (Mainly the Roman and Napoleonic eras and WWII. But is interested in all periods and aspects. Also enjoys making battleboxes and will accept beer as payment :)
- Rhion (Roman and Welsh mediaeval)
- Robth (Classical antiquity, 5th and 4th century Greece in particular)
- rogerd (Pre- U.S. Civil War conficts (including American Revolution), World War II, Military Aircraft of any period)
- Roman Babylon (Medieval Warfare mostly, modern day combat as well)
- Rshu (Self proclaimed new member/worked much on Military history of Germany/enjoys correcting stubs on Roman/Medieval/Enlightenment Age-Modern Day)
- Rusty2005 (General Nineteenth and Twentieth centuries, focusing on Africa, China, India, and Europe)
- Sabrebattletank (proofreader, editor, can do anything)
- Searchme
- Semprini (WWI, WWII, Dutch history)
- Spawn Man (Self proclaimed new member greeter/WWI/Anything else)
- SoLando (Generally working on British-related battles of the Napoleonic Wars, rest of the 19th Century, and WWI and WWII)
- Staxringold (minor stuff, working on Battle of Amiens right now)
- szopen (created list of battles)
- Tanzburg (Generalist with primary interest in WW1 and a growing interest in Central & Eastern Europe)
- TeunSpaans
- The Half Gauntlet
- The Minister of War (Generalist, though main interest lies in medieval Europe or Asia. I'd be happy to help do some editing)
- Thmars10 (Edit with what knowledge I have. Willing to do some research and some cleaning upping)
- Tpower
- TSO1D (intersted in European/Western Conflicts throughout history)
- vidarlo (Mostly WWII in Western Norway, will edit what I see though)
- WangKon936 (Although my interests in Military History are varied, I will, for the time being, focus on Korean Military History as it is so little known outside of Asia.)
- Wendell (Plan to peer review articles. Likes to organize. )
- Wikiacc (talk) (Mostly battleboxes)
- Wurkwurk
Development
Task forces
This section is currently under development.
Task forces are informal groups of editors gathered for collaborative work on a particular topic. There is currently one active task force:
- Canadian military history - currently looking for members.
For the time being, please discuss potential task forces with the project before creating them.
Work in progress
- Work list - a list of important articles that may require further improvement.
- Wanted articles - a list, collected from various sources, of non-existent articles that need to be written.
- New articles - a list of newly created military history articles.
Current discussions
Archive
- Battlebox usage instructions (pre-November 2005)
- Battlebox colour scheme (pre-August 2005)
- Campaignbox proposal and alternatives (November 2004)
Resources
Related projects
- Falklands War - the Falklands War.
- Military - current military issues.
- British Army - armed forces of the United Kingdom.
- Hellenic Army - armed forces of Greece.
- Polish Army - armed forces of Poland
- Ships - ships, including naval vessels.
- Vietnam War (inactive) - the Vietnam War.
- World Wars - World War I and World War II.
Internal resources
The following articles may be helpful aids for an editor of a military history article:
- Glossary of German WWII military terms
- List of equipment used in World War II
- List of established military terms
- List of military tactics
- List of modern AFV and artillery related terms and acronyms
- List of modern infantry related terms and acronyms
- List of Roman military terms
- List of Grande Armée Slang terms
- List of World War II electronic warfare equipment
- Naming conventions (military units)
- Various military lists (maintained by the Military WikiProject)
External resources
- The online bookshelves of the U.S. Army's Center for Military History
- The Naval Historical Center of the U.S. Navy.
- An archive of old issues of Naval Aviation News maintained by the U.S. Navy.
- Fields of Conflict - an American Civil War research and discussion group.
- OnWar - A general purpose military site with a focus on World War II.
Auxiliary templates
Category description
| Template | Result |
|---|---|
| {{Battle category by participant}} Placed on sub-categories of Category:Battles by country |
This category includes historical battles in which COUNTRY (CREATED–DESTROYED) participated. Please see the category guidelines for more information. |
| {{Battle category by conflict}} Placed on sub-categories of Category:Battles by war |
This category contains historical battles fought as part of the WAR. Please see the category guidelines for more information. |
| {{War category by participant}} Placed on sub-categories of Category:Wars by country |
This category includes historical wars in which {{{1}}} ({{{2}}}–{{{3}}}) participated. Please see the category guidelines for more information. |
Project notice
| Template | Result | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {{WikiProject Military history}} Placed on article talk page |
Please add {{WikiProject banner shell}} to this page and add the quality rating to that template instead of this project banner. See WP:PIQA for details.
| ||||||||||||||||||||||||
| {{WikiProject Military history category}} Placed on category page |
Template:WikiProject Military history category | ||||||||||||||||||||||||
| {{WikiProject Military history template}} Placed on template talk page |
Template:WikiProject Military history template | ||||||||||||||||||||||||
| {{WikiProject Military history user}} Placed on user or user talk page |
Template:WikiProject Military history user | ||||||||||||||||||||||||
| {{User WikiProject Military history}} Userbox, placed on user page |
| ||||||||||||||||||||||||
Stubs
| Template | Result | Category | ||
|---|---|---|---|---|
| {{Mil-hist-stub}} |
|
Category:Military history stubs | ||
| {{US-mil-hist-stub}} |
|
Category:United States military history stubs | ||
| {{Battle-stub}} |
|
Category:Battle stubs | ||
| {{NapoleonicWars-stub}} |
|
Category:Napoleonic Wars (1792-1815) stubs | ||
| {{Warof1812-stub}} | Category:War of 1812 stubs | |||
| {{AmericanCivilWar-stub}} |
|
Category:American Civil War stubs | ||
| {{WWI-stub}} |
|
Category:World War I stubs | ||
| {{WWII-stub}} | Category:World War II stubs | |||
| {{Vietnam-war-stub}} |
|
Category:Vietnam war stubs |
Other
| Template | Result | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {{WikiProject Military history tasks}} (large version) {{Milbox}} (small version) |
| |||||||||||||||||||||||
| {{History of war}} |
| |||||||||||||||||||||||
- Campaignbox templates
- Templates generating hCalendars
- Templates generating hCalendars and Geo
- War and conflict infobox templates
- Templates based on the Infobox Lua module
- Navigational box wrapper templates
- Military navigational boxes
- Templates that add a category
- Project-Class military history articles
- History WikiProjects
- Templates generating hCards
- Military infobox templates