Template:Old prod

Template documentation follows
Note: the template above may sometimes be partially or fully invisible.
Visit "Template:Old prod/doc" to edit its documentation if it is available. (How does this work?)

Purpose

The purpose for this template is to reduce repeated proposed deletion (PROD) nominations of the same article.

Use this template to flag that this article has gone through a proposed deletion proposal in the past, and is hence ineligible for a second PROD, and also that editors could benefit from checking up on past discussions before nominating it for deletion to AFD.

This template should not be used for Wikipedia:Proposed deletion of biographies of living people / {{prod blp}} deletions, that is a separate process with separate criteria, independent of the regular proposed deletion process.

When to use

Add it mainly to article talk pages where a) you consider future deletion proposals likely, and b) you consider the denial of such proposals equally likely.

Specifically, this template documents the facts that:

1. an article has previously been tagged for a proposed deletion, as well as
2. the PROD may have been seconded by Some Other Editor, as well as
3. the PROD may have been contested by Some Other Editor, either by removing the tag or using WP:REFUND.

Although it can be used for documenting active (seconded) PRODs, it will generally be added only after a PROD has been contested and removed.

This template populates Category:Past proposed deletion candidates.

Ideally, the contester should add it manually to the talk page. This is a courtesy, and also a handy record of the rationales given by the proposer, seconder (if any) and contester.

If you contest a PROD, then you should also notify the nominator by placing a {{Deprod}} on their Talk page.

Usage

Vertical format

copy-paste the following text, then fill in the appropriate parameters:

{{Old prod
| nom       = 
| nomdate   = {{SUBST:#time: Y-m-d}}
| nomreason = 
| 2nd       = 
| 2nddate   = {{SUBST:#time: Y-m-d}}
| 2ndreason = 
| con       = 
| condate   = {{SUBST:#time: Y-m-d}}
| conreason = 
}}

Depending on the value of |nomdate=, the template takes different appearances:

• If nomdate is within the past 7.25 days, the template produces: (nomdate set to today in example)

• If nomdate is older than 7.25 days, the template produces: (nomdate 8 days ago, in example)

However, it takes the latter appearance, regardless of nomdate, if the |declined= is set (to any value), or if |con= is specified.

There are three types of editors (TLA), each with two optional parameters:

1. nom is the editor who initiated the PROD.
2. 2nd is the editor who seconded the PROD.
3. con is the editor who contested the PROD.

There are two optional parameters for each editor:

1. TLAdate is the appropriate date in ISO 8601 format, e.g., YYYY-MM-DD.
   (Note that {{#time: Y-m-d}} will supply the current date. Please do not use {{ISO date}}, as it introduces unwanted HTML tags.)
2. TLAreason is the text they provided (perhaps copied from the Edit summary).

This template will automagically generate appropriate output based on the parameters supplied, e.g., only the editors.

Examples

Using just the editor parameters:

{{Old prod
| nom= MBisanz 
| 2nd= 72.75.72.63 
| con= Callelinea 
}}

---

Using some of the parameters:

{{Old prod
| nomreason= Part of a batch of articles with [[WP:COI/N]] issues
| 2nd=       72.75.72.63 
| 2nddate=   2008-02-03
| con=       Callelinea 
| conreason= Added reference and external link … will edit later
}}

---

Using all of the parameters (notice that the order does not matter):

{{Old prod
| nom=       MBisanz 
| 2nd=       72.75.72.63 
| con=       Callelinea 
| nomdate=   2008-02-03
| 2nddate=   2008-02-03
| condate=   2008-02-03
| nomreason= Part of a batch of articles with [[WP:COI/N]] issues
| 2ndreason= See [[Category talk:Cuban contemporary artists/Checklist]]
| conreason= Added reference and external link … will edit later
}}

See also

• Category:Endorsed proposed deletions
• Category:Past proposed deletion candidates

Template:Old prod invokes Module:Navbox using Lua.

Usage

This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.

The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.

Syntax

{{navbox
|state      = uncollapsed, collapsed, plain, autocollapse (default)
|name       = mandatory - name of the template
|style      = optional - style for the whole table
|title      = mandatory - navbox header
|gtitleN    = optional - title of N-th group of items
|styleN     = optional - style for groupN; i.e. text-align
|groupN     = mandatory - list of groups of items
|fstyle     = optional - style for footer ; i.e. text-align
|footer     = optional - navbox footer
}}

• Groups: Currently there is no technical limit to the maximum number of groups.
  • Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
• Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
• Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
  • Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
• Line breaks: Line-breaks (<br />) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN.
• Bullets: Create unordered lists with lines beginning with *.
• Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! ({{!}}).

States

• Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
  • Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
• Uncollapsed: Forces the navbox to be displayed.
  • All of the navboxes in this documentation are in the uncollapsed state.
• Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
  • Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
• Plain: Removes the "show/hide" link.

Sub-groups

• For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
• To create sub-groups within {{navbox}}, certain parameters are to be included:
  • The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
  • The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.

{{navbox
|name    =
|title   =
|gtitle1 =
|group1  =
|gtitle2 =  
|gtype2  = Subgroup (mandatory)
|group2  = 
  {{navbox
  |subgroup = yes (mandatory)
  |gtitle1  = 
  |group1   =
  |gtitle2  = 
  |group2   = 
  }}
}}

Collapsible sub-groups

• For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
• To create collapsible sub-groups within {{navbox}}, these parameters need to be included:
  • The parent navbox is almost always uncollapsed (state=uncollapsed).
  • The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
  • The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
  • The nested collapsible navbox is forcefully collapsed (state=collapsed).

{{navbox
|state  = uncollapsed
|name   = 
|gtype1 = Subgroup
|group1 = 
  {{navbox
  |collapsible = yes
  |state   = collapsed
  |title   = 
  |gtitle1 = 
  |group1  = 
  |gtitle2 = 
  |group2  = 
  }}
}}

Use of images

• The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
• Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.

Link and file share the same name

{{plink|Item}}

File name differs from the link

{{plink|Item|File}}

Link and file share the same name, but different text is desired to display

{{plink|Item|alt=Text}}

File name differs from the link and different text is desired to display

{{plink|Item|File|alt=Text}}

Categorising

Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.

There are 2 methods of categorising pages with navboxes:

The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.

Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.

Examples

To see the following navboxes in action, see Template:Navbox.

Single line navbox with centered list

{{navbox
|name    = 
|title   = 
|style1  = text-align:center
|group1  =
}}

Navbox with standard footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|footer  = Centered footer
}}

Navbox with styled footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|fstyle  = text-align:right
|footer  = Right-aligned footer
}}

Multiple line navbox

{{navbox
|name    = 
|title   = 
|gtitle1 = Group title 1
|group1  = 
|gtitle2 = Group title 2
|group2  = 
|gtitle3 = Group title 3
|group3  = 
}}

Collapsed navbox

{{navbox
|state   = collapsed
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox with Tnavbar

{{navbox
|state   = plain
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox without Tnavbar

{{navbox
|state   = plain
|title   = 
|style1  = text-align:center
|group1  = 
}}

Complicated navbox

{{navbox
|state   = uncollapsed
|name    = 
|title   = 
|gtitle1 = Level 1 Title 1
|group1  = 
|gtitle2 = Level 1 Title 2
|group2  = 
|gtitle3 = Level 1 Title 3
|group3  = 
|gtitle4 = Level 1 Title 4
|group4  = 
|gtitle5 = Level 1 Title 5
|gtype5  = Subgroup
|group5  = 
  {{navbox
  |subgroup = Yes
  |gtitle1  = Level 2 Title 1
  |group1   =
  |gtitle2  = Level 2 Title 2
  |group2   =
  |gtitle3  = Level 2 Title 3
  |gtype3   = Subgroup
  |group3   = 
    {{navbox
    |subgroup = Yes
    |gtitle1  = Level 3 Title 1
    |group1   =
    |gtitle2  = Level 3 Title 2
    |group2   =
    }}
  |gtitle4  = Level 2 Title 4
  |group4   = 
  }}
|gtitle6 = Level 1 Title 6
|group6  = 
|gtitle7 = Level 1 Title 7
|group7  = 
|fstyle  = 
|footer  = 
}}

Preventing unwanted documentation

The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).

Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.