Wikipedia:WikiProject Aviation/Style guide/Lists/draft

Draft additions

The purpose of these additions is to reflect the consensus reached/clarified on various issues at Wikipedia talk:WikiProject Aviation#List of aircraft of X Air Force/Military table formats, especially as related to images (and if need be to resolve consensus on any outstanding details).

It is intended that this additional material be merged into to the current guideline, so some copyediting will also be needed.

MOS applicability

Wikipedia's general policies and guidelines apply to lists of aircraft. They are not repeated here but the more important are linked to above.

The MOS:TABLES default is to avoid the use of in-table CSS styling. Special cases for its use may be agreed by a relevant WikiProject. The Aviation WikiProject has established no special cases where it may be used, therefore it should not be used in lists of aircraft types.

General requirements

These requirements apply equally to lists in larger articles and to lists which have their own page.

No images should be included in lists of aircraft, such as small photographs or national flag icons. (National flag icons may only be used to denote an operator's nationality in the Operators section of an aircraft article.)

Images should not be placed before the table such that they push it downwards from the section heading or page title in mobile browsers or shrink it sideways in desktop browsers.

Lists of aircraft types

Lists should be sortable. Use

{| class="wikitable sortable"

Do not use rowspan or colspan markup, as it is difficult for inexperienced editors and assistive technologies to make sense of. For example this requires that you:

• Do not use full-width subheadings.
• Do not break up any cells into multiple rows for sub-types.

Lists of types relating to an organisation

These lists include types associated with national services, airlines and other organisations that operate many aircraft of different types. They should comply with the general guidelines except where these conflict with the detail guidelines below.

Lists should comprise the following columns:

Type	Origin	Role	Adopted	[Status]	No.	Notes

Type

This should be the top-level type designator. In general, there should be only one entry (row) for each type.

Exceptions may be allowable where:

• A production variant evolved from the same basic design has been given a different name.
• A production variant has a different role and is so distinct as to be virtually a different type.
• A production variant incorporates a major airframe redesign such as swept wings.

Origin

The origin is the country of origin for the top-level type designator. A country of local manufacture or modification should only be given if it incorporates a major airframe redesign such as swept wings, and/or a change of name.

Role

As per general lists.

Adopted

Date on which the first machine was delivered.

[Status]

A given list may include types currently in service, historical types no longer in service, or both these groups. Heading and usage of this column vary accordingly:

• For lists of types in service, this should be headed In service and include the number currently in service (this includes "hangar queens" and other individual craft which may not currently be airworthy).
• For lists of historical types it should be headed Retired and include the year of last retirement.
• For lists including both, it should be headed Status and should contain entries only of the forms:
  • [No.] in service
  • Retired [Year]

No.

This should be the total number of aircraft taken on over the type's service lifetime. It includes machines which may never have flown.

Notes

Notes should be kept short and confined to key information, for example if some examples have been locally manufactured or modified, but not to detail the sub-types or modifications.

Any citations or inline notes for the type should go at the end of this entry.