Template:KeySuffixDescription/doc

This is a documentation subpage for Template:KeySuffixDescription.
It contains usage information, categories and other content or metadata that is not part of the original template.

Parameters

suffix — the suffix described by the template (without the *:)

Example:

{{KeySuffixDescription
| suffix = lanes
}}

for other parameters see Template:KeyDescription

TemplateData

This is the TemplateData for this template used by VisualEditor.
TemplateData for KeySuffixDescription

This template provides a description box suitable for key prefixes (or namespace keys).

Template parameters
This template prefers block formatting of parameters.
Parameter		Description	Type	Status
suffix	`suffix`	key suffix Example lane	String	required
image	`image`	image of the feature suffix or namespace Example File:...	File	optional
description	`description`	a short description of the suffix or namespace	String	required
group	`group`	The name of the broader group to which this feature belongs. Please use lower-case names from Category:Features or from your namespaced (Category:DE:Features) or l10n version. Example highways	Page name	suggested
onNode	`onNode`	If the feature can be used on a node. Example yes, no	String	suggested
onWay	`onWay`	If the feature can be used on a way. Example yes, no	String	suggested
onArea	`onArea`	If the feature can be used on an area. Example yes, no	String	suggested
onRelation	`onRelation`	If the feature can be used on a relation. Example yes, no	String	suggested
combination	`combination`	A bulleted-list of example tag(s) that can be used in combination with this feature. Example * {{Tag\|key name\|value}} * {{Tag\|key name\|value}}	Unknown	optional
implies	`implies`	A list of tag(s) that the feature implies in its definition. Example * {{Tag\|key name\|value}} * {{Tag\|key name\|value}}	String	optional
requires	`requires`	A list of tag(s) which are necessary (often higher/lower in hierarchy) for this tag and must be set to give its actual meaning Example * {{Tag\|key name\|value}}	Unknown	optional
seeAlso	`seeAlso`	a list of similar tags Example {{Tag\|key name\|value}}	String	optional
status	`status`	The [[approval status]] of this feature Example approved, de facto, deprecated, discardable, in use, obsolete, proposed, undefined, voting	String	suggested
statuslink	`statuslink`	The name of the proposal page, for linking.	String	optional
language	`lang`	the ISO 639-2 code for the language used to document this feature: this will generate aspects of the description box in the specified language, if translations are available. If not set, language of page or namespace will be used. Example es, de	Unknown	optional
class	`class`	The CSS class of the HTML table used to form the description box. (Not used in most cases.)	String	optional
float	`float`	The CSS float value of the table: set to none to disable the standard right float. (Not used in most cases.) Example left, right, none	String	optional
style	`style`	The CSS style to be applied to the HTML table. (Not used in most cases.)	String	optional
languagelinks	`languagelinks`	If the langauge links should not appear. (Not used in most cases.) Example no	String	optional

Examples

{{KeySuffixDescription
| suffix        = both_ways
| image         = 
| description   = The *:both_ways keys are used to specify properties for lanes or similar features running in both directions of a way. 
| group         = 
| onNode        = no
| onWay         = yes
| onArea        = no
| onRelation    = no
| status        = approved
| statuslink    = Proposed_features/Suffix_both_ways
}}

Description
v · d · e Suffix *:both_ways

The *:both_ways keys are used to specify properties for lanes or similar features running in both directions of a way.
Group: properties
Used on these elements

See also
`both_ways=*`
Status: approved
taginfo: *:both_ways