ᱪᱷᱟᱸᱪ:Military navigation
 | This template uses Lua: |
Navigation templates
[ᱯᱷᱮᱰᱟᱛ ᱥᱟᱯᱲᱟᱣ]ᱪᱷᱟᱸᱪ:Grand Armee Corps The various navigation templates maintained by the Military history WikiProject are all intended to be implemented through a single base template, which combines the project's common template style with the standard navigation box format. This is needed primarily to allow multiple such templates to be stacked together—with each other, or with infobox templates—to present the appearance of a continuous block; it is also beneficial for providing a consistent appearance to the entire set of articles within our scope.
Any military-related navigational template should be created using the {{military navigation}} base template, as shown below:
{{Military navigation
| name =
| raw_name =
| state =
| style =
| title =
| image =
| imageleft =
| odd_color =
| even_color =
| above =
| listclass =
| group1 =
| list1 =
| group2 =
| list2 =
| group3 =
| list3 =
...
| group30 =
| list30 =
| below =
}}
- name
- The actual page name (i.e. "XYZ" for Template:XYZ) of the newly-created template.
- raw_name
- Use instead of "name" to omit the V · T · E links from the title bar.
- title
- The displayed title of the navigation box.
- listclass
- Optional – but typically
hlist, to format content as horizontal lists. In the case of hlists in above or below fields, set bodyclass=hlist, instead. - style
- Optional – an alternative style for the template; this may be set to "wide" to produce a full-width box. The alternative style should be used sparingly; it is intended that the majority of navigational templates will use the default style (in the wild, "wide" has become quite common). The above example template formatted with
style=wideis shown below:
- state
- Optional – may be set to "collapsed" to force the template to render in its closed state by default.
- odd_color/even_color
- Optional – the stripe colors for alternating listN items to use. These parameters should be used sparingly; in the absence of a good reason to do otherwise, templates should use the default stripe colors.
- groupN/listN
- The body of the navigation box, consisting of successive horizontal blocks of content (the listN fields) with optional labels (the corresponding groupN fields). Please see the documentation for {{navbox}} for more details on the different layouts possible.
- above
- Optional – the sub-header of the navigation box; please see the documentation for {{navbox}} for more details on the resulting layout when this is used.
- below
- Optional – the footer of the navigation box; please see the documentation for {{navbox}} for more details on the resulting layout when this is used.
- image
- Optional – an image to be displayed at the right of the box, given in the form
[[File:Example.jpg|100px]]. This parameter should be used sparingly, and typically only in conjunction with the full-width template style. - imageleft
- Optional – an image to be displayed at the left of the box, given in the form
[[File:Example.jpg|100px]]. This parameter should be used sparingly, and typically only in conjunction with the full-width template style.
Common problems with navigation templates
[ᱯᱷᱮᱰᱟᱛ ᱥᱟᱯᱲᱟᱣ]
There are several known issues with the current navigation template design that editors should be aware of:
- Shifted header wrapping
- A long header used in a narrow navigation template may wrap incorrectly, with the second line being indented further than necessary. A workaround is possible by adding a
<br />tag between the words where the wrapping is to occur. This should be done to separate link-text to the right of the 'pipe' (|), as follows:[[Article title|Article <br /> title]]. An alternative method is to use {{allow wrap}} for the link-text as follows:[[A very long article title|{{allow wrap|A very long article title}}]], which allows the browser to break as-needed. - Stretching or overflowed boxes
- A very long header formatted as a single link may cause a template to stretch beyond its normal width, or the whole link to extend off too far to the right. A workaround is possible by breaking the header onto multiple lines, as shown above.