Difference between revisions of "Template:Multiple issues/doc"

From LIMSWiki
Jump to navigationJump to search
(Created as needed.)
 
 
(One intermediate revision by the same user not shown)
Line 24: Line 24:
{{POV|date=June 2009}}
{{POV|date=June 2009}}
{{One source|date=March 2011}}
{{One source|date=March 2011}}
{{Notability|Corp|date=June 2012}}
}}</pre>
}}</pre>
produces
produces
Line 31: Line 30:
{{POV|date=June 2009}}
{{POV|date=June 2009}}
{{One source|date=March 2011}}
{{One source|date=March 2011}}
{{Notability|Corp|date=June 2012}}
}}
}}


Line 55: Line 53:
== Old syntax ==
== Old syntax ==
Please see [[Template:Multiple issues/doc/old]] for the deprecated syntax this template used previously.
Please see [[Template:Multiple issues/doc/old]] for the deprecated syntax this template used previously.
== TemplateData ==
{{TemplateDataHeader}}
<templatedata>
{
"description": "This template is used to tag articles or sections for multiple maintenance issues and display the alerts in a single box.",
"params": {
"1": {
"label": "Issues",
"type": "content",
"description": "The issues that you want to include. Use the full template syntax, with newlines between them.",
"suggested": true,
}
}
}
</templatedata>


== See also ==
== See also ==
* {{tl|Stub}} and the [[:Category:Stub categories]] for a more appropriate way to tag most very short articles.
* {{tl|Stub}} and the [[:Category:Stub categories]] for a more appropriate way to tag most very short articles.
; Hidden tracking/maintenance categories
* [[:Category:Pages using multiple issues with incorrect parameters]] (via [[Module:Check for unknown parameters]])


<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox | |
<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox | |

Latest revision as of 23:59, 18 August 2016

Using too many individual article message boxes can distract from the article and make it unpleasant to look at, as in this example. This template tags articles or sections for multiple maintenance issues and then displays the alerts in a single box, as an alternative to using several space-consuming boxes.

Usage

The syntax for the template is:

{{Multiple issues|section=|
{{Issue 1}}
{{Issue 2}}
{{Issue 3}}
...
}}

where Issue 1, Issue 2, Issue 3, etc. are article maintenance templates, which take their usual parameters, and {{Ambox}} templates, which usually should not be used. Each of these templates should be placed on individual lines, but must not be separated from each other by pipes or template parameters, because that would cause some or all of the banners to be hidden.

A |section=yes parameter can be used to modify the template to be used below a section header.

Example for an article

{{Multiple issues|
{{Orphan|date=January 2008}}
{{POV|date=June 2009}}
{{One source|date=March 2011}}
}}

produces

Example for a section

{{Multiple issues|section=yes|
{{Unreferenced section|date=January 2012}}
{{Disputed-section|date=April 2012}}
{{Expand section|1=examples and additional citations|demospace=main|date=June 2012}}
}}

produces

General notes

  • Redundant issues: Please do not insert tags that are too similar to or redundant with each other. All articles that read like essays have an inappropriate tone, and in fact they end up in the same category, so it is unnecessary to add {{tone}} in addition to {{essay-like}}. {{Cleanup}} is very vague and so should be replaced with a more specific template.
  • Too many issues: Similarly, if an article has many problems, please consider listing only the most important. A lengthy list is often less helpful than a shorter one. Remember that this tag is not intended as a badge of shame.
  • Only one issue: Don't use this template for a single issue; just use the stand-alone template.
  • Custom text: If no article maintenance template describes a problem, an {{Ambox}} lets you write custom text. Don't use it to add more than an article maintenance template says, since what is said should be concise and article maintenance templates usually are. In your custom text, link to a relevant policy or guideline so other editors understand why adherence to your Ambox is important. While an article maintenance template generally causes categorization that invites editing, an Ambox template does not, so, if at all feasible, use an article maintenance template instead.

Old syntax

Please see Template:Multiple issues/doc/old for the deprecated syntax this template used previously.

See also