Template:Class mask/doc: Difference between revisions

{{TemplateData header}}

{{TemplateData header}}

<templatedata>{

<templatedata>{

“description”: “This template provides the project-specific valid Wikipedia 1.0 assessment scheme classes to Template:WPBannerMeta“,

“description”: “This template provides the project-specific valid Wikipedia 1.0 assessment scheme classes to :”,

“format”: “inline”,

“format”: “inline”,

“paramOrder”: [

“paramOrder”: [

“1”: {

“1”: {

“label”: “Assessment class”,

“label”: “Assessment class”,

“description”: “Passthrough for {{{class}}} parameter from Template:WPBannerMeta“,

“description”: “Passthrough for {{{class}}} parameter from :”,

“example”: “{{{class|}}}”,

“example”: “{{{class|}}}”,

“type”: “content”,

“type”: “content”,

This template is used on approximately 370,000 pages, or roughly 1% of all pages. To avoid major disruption and server load, any changes should be tested in the template’s /sandbox or /testcases subpages, or in your own user subpage. The tested changes can be added to this page in a single edit. Consider discussing changes on the talk page before implementing them.

This template is designed for use in WikiProject banners, and provides an easy way to construct a bespoke class mask. The class parameter must be passed to the template as the first unnamed parameter.

The template provides the default class masks for WikiProject’s quality scales, and is also used by a few projects which have opted out of the standard scale and use a custom class mask by setting |QUALITY_CRITERIA=custom and |QUALITY_SCALE=subpage in the WikiProject’s banner template, and creating a /class subpage.

When used on a /class subpage, the template should be called in the following way:

{{Class mask<noinclude>/templatepage</noinclude>|1={{{class|}}}
 |topic=
 |all other optional parameters desired, one per line…
}}

The <noinclude>...</noinclude> tags allow the documentation from {{Class mask/templatepage}} to be displayed directly on the banner template’s /class subpage, where it can provide useful information and category prompts for WikiProject admins and other interested users without any adverse effects to the banner template.

• the |topic= parameter defines the main naming scheme of the assessment categories used by the project (i.e. the part of its assessment category names that comes after Category:Whatever-Class and before articles) and is used to check the existence of the categories that are required. For example, if your project uses categories such as Category:B-Class mathematics articles, etc., then set |topic=mathematics.
  • if the template uses task forces, the parameters |topic1=, |topic2=, |topic3=, |topic4=, |topic5= and |topic6= can be used to check for the corresponding categories needed by each.

• If one or more of these nine is set to no, the class will be switched off. Their default is yes:
• |FQS= – if set to yes, these seven additional assessment classes are activated (FQS stands for Full Quality Scale). Undesired classes may then be switched off individually by setting them to no. When |FQS= is absent, setting one or more to yes will switch on only that class.
• If either of these is set to yes, that class will be switched on. The default is no, regardless of the |FQS= setting:
• |forceNA= – if set to yes, will automatically classify pages tagged as |class=NA depending on the namespace of the page. The default setting is no.
• |b1=, |b2=, |b3=, |b4=, |b5=, |b6= – if the B-class checklist is used, these parameters must be passed through.

Add a class in lowercase as the name of a parameter followed by the value “yes”. For example, |future=yes would add the

class. This is the simplest way of adding a class but has the following two limitations:

• The name of the class must have an initial capital letter and all following letters in lowercase. In other words, the capitalisation must be of the form Xxxxxx.
• It is not possible to use this method to add a shortcut or alternative alias for a different class, for example “Cur” for Current-class.

If either of these are required, the uppercase parameter syntax must be used (see below).

If |FQS=yes is used, then a value of “no” may be used to switch off that individual class. Thus, on a /class subpage:

{{Class mask<noinclude>/templatepage</noinclude>|1={{{class|}}}
 |topic=physics
 |FQS=yes
 |portal=no
}}

would support six of the seven additional classes listed above but not support Portal-Class.

Add a class in UPPERCASE as the name of a parameter followed by the exact, case-sensitive name of the class as the value of the parameter. For example,

would add SIA-Class and

would add CheeseCake-Class.

You can use this method to add a shortcut or alias for a class, too, as in the case of

which would have the effect that defining either |future= or |fut= (not case sensitive) with a valid value would result in an assessment into Future-Class for that page.

You can add as many aliases for a class as needed, so this would work just as well for SIA-Class,

|SIA=SIA
|SETINDEX=SIA
|SET INDEX ARTICLE=SIA

and would mean that an input of |sia=, |setindex= or |set index article= (again, these are case-insensitive) would each result in an SIA-Class page assessment.

The following code is placed in the banner template,

|QUALITY_SCALE=subpage
 |class={{{class|}}}

and on the /class subpage (for example {{WikiProject Highways}} uses the subpage Template:WikiProject Highways/class), the following code is used:

{{Class mask<noinclude>/templatepage</noinclude>|1={{{class|}}}
 |topic=Highways
 |FQS=yes
 |redirect=yes
}}

In this case all seven of the “extended” quality classes are used, plus the additional Redirect-Class, and because the |topic= parameter is set, specific documentation will be displayed on the /class subpage for it.

• This shows all /class subpages which use this template.