Template:Multiple issues/doc

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
Do not use this as the only message box on the article or section; it should be used with at least two other message boxes contained inside it. Search for the best templates to express your issues at Template messages or Template messages/Examples.

The syntax for the template is: where Issue 1, Issue 2, Issue 3, etc. are article maintenance templates (see Template messages/Cleanup), 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 yes parameter can be used to modify the template to be used below a section header.

Example for an article
produces

Example for a section
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 whenever possible.
 * 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. See Template messages/Cleanup for a list of available tags.
 * Custom text: If no article maintenance template describes a problem, an 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.

TemplateData
{	"description": "This template is used to tag articles or sections for multiple maintenance issues and display the alerts in a single box.", "format": "inline", "params": { "1": {			"label": "Issues", "type": "content", "description": "The issues to include. Use full template syntax, with new lines between them.", "suggested": true },		"collapsed": { "label": "Collapsed by default?", "description": "Enter \"yes\" or \"y\" here to make the multiple issues hidden by default.", "type": "line", "autovalue": "yes", "example": "yes" },		"section": { "label": "Section, not article?", "description": "Enter \"yes\" or \"y\" here to replace the word \"article\" with \"section\" in the template.", "type": "line", "autovalue": "y", "example": "y" }	} }