Template:Infobox artwork/doc

Usage

{{{title}}}
{{{other_language_1}}}: {{{other_title_1}}}, {{{other_language_2}}}: {{{other_title_2}}}
[[File:{{{image}}}|frameless|alt={{{alt}}}|upright={{{image_upright}}}]] {{{caption}}}
Artist	{{{artist}}}
Year	{{{year}}}
Catalogue	{{{catalogue}}}
Medium	{{{medium}}}
Movement	{{{movement}}}
Subject	{{{subject}}}
Dimensions	{{{height_metric}}} cm × {{{width_metric}}} cm × {{{length_metric}}} cm ({{{height_imperial}}} in × {{{width_imperial}}} in × {{{length_imperial}}} in); {{{diameter_metric}}} cm diameter ({{{diameter_imperial}}} in); {{{dimensions}}}‍{{{dimensions_ref}}}
Weight	{{{weight}}}
Designation	{{{designation}}}
Condition	{{{condition}}}
Location	{{{museum}}}, {{{city}}}
Coordinates
Owner	{{{owner}}}
Accession	{{{accession}}}
Preceded by	{{{preceded_by}}}
Followed by	{{{followed_by}}}
{{{module}}}
Website	{{{website}}}

<syntaxhighlight lang="wikitext" style="overflow:auto"> </syntaxhighlight>

Parameters

title

The title of the artwork. Defaults to the page name.

painting_alignment

The alignment of the infobox. Defaults to right-alignment. It should almost always be "right", but can also be "left".

other_language_1

Language of secondary title

other_title_1

Secondary title. Italicized unless |italic other_title_1=no.

other_language_2

Language of tertiary title

other_title_2

Tertiary title. Italicized unless |italic other_title_2=no.

wikidata

QID of the specific Wikidata item

image

The name of the image file to display, without the "File:" prefix

image_upright

Image scaling factor; see WP:IMGSIZE for the image size policy

alt

Alternative text for image

caption

Caption for image

artist

Name of the artist(s) who created the piece

year

Use {{start date}} unless before 1583 CE.

completion_date

Use {{start date}}; alternative to |year=.

catalogue

Reference in a catalogue raisonné.

type

Deprecated due to ambiguity. Use medium and movement instead.

medium

Material used by the artist or designer to create the work of art. Examples: "Oil on canvas", "Bronze sculpture", "Ceramic tile"

movement

Art movement, or movements, typically associated with work of art or time during artist's career when work of art was created. Must be verifiable through sources. Examples: "Post-Impressionism", "Pop art"

subject

Subject(s) of the artwork

dimensions

See #Dimensional parameters section below

weight

Weight of the artwork ()

designation

Legal protection granted to the artwork

condition

Condition of the artwork

museum

Museum that currently houses the artwork

city

City in which the artwork is currently located

coordinates

Use {{coord}}, but only for the exact coordinates (when known) of the artwork's own location, i.e. not coordinates for the site, building, structure, etc. where it is kept; leave blank otherwise.

owner

Current owner of the artwork

accession

Accession or similar reference in the museum's database.

preceded_by

Preceding work by the same artist

followed_by

Next work by the same artist

module

an embedded template

website

Use {{URL}}, but only for an official webpage or website.

Dimensional parameters

This template includes code that allows input of dimensional information: any of height, width, length, and diameter, as well as a freeform parameter for adding nonstandard information.

There are 11 parameters, of which most fall into two groups of unit types:

• height_imperial
• width_imperial
• length_imperial
• diameter_imperial

These define the respective values for Imperial or US customary units such as the foot or inch. If the imperial unit is set to feet, inch specification can be added with height_inch, width_inch, length_inch, otherwise these _inch-suffixed parameters should not be used.

• height_metric
• width_metric
• length_metric
• diameter_metric

These define the respective values for SI (metric) units such as the metre (meter) or centimetre (centimeter).

Once raw numerical values are established in the above parameters, the units are set in the imperial_unit and metric_unit parameters, which default to inches and centimetres respectively.

If information is provided in only one unit system, it is automatically converted to the other using the unit that is defined for that system. In general, this should be used, as for most pieces of artwork measurements will only be taken in one unit system. Do not use a comma as decimal indicator for metric units (as used in some European and other countries) since the conversion does not recognize commas and the imperial measurement will be calculated incorrectly (e.g. use 30.8 not 30,8).

Users should take care to avoid false precision: measurements should be provided in the same unit, and with the same number of significant digits, as when they were taken. ("1 metre" is far less precise than "1000.00 millimetres", even though they are, in theory, the same length!)

If additional dimensional data is needed, the dimensions parameter can be used to add freeform information to the end of the rendered string. This parameter accepts raw wikitext and is not subject to any automatic conversion or modification ({{convert}} would have to be used manually).

References concerning artwork dimensions can be appended to the dimensional data by placing them in the optional dimensions_ref parameter.

Map and coordinates

The coordinates= parameter is used to display coordinates in the infobox, and optionally at the top of the page; use the {{coord}} template.

Two types of maps are available: pushpin maps (static) or mapframe maps (dynamic).

Pushpin maps

<syntaxhighlight lang="wikitext" style="overflow:auto"> {{Infobox artwork ... | coordinates = | pushpin_map = | pushpin_map_alt = | pushpin_relief = | pushpin_label_position = | map_dot_label = | map_size = | pushpin_map_caption = ... }} </syntaxhighlight>

Mapframe maps

A Mapframe map is automatically included if:

• It has been turned on by setting |mapframe=yes
• There are coordinates specified in |coord=, or if the Wikidata item for the page (or as specified in |qid=) has a value for (P625)
• No pushpin map has been specified

The following optional parameters can then be used to adjust the map

• Basic parameters:
  • mapframe – Specify yes or no to show or hide the map, overriding the default. Default: no
  • mapframe-caption – Caption for the map. Default: blank (or if |mapframe-geomask= is set, "Location in geomask's label")
  • mapframe-custom – Use a custom map instead of the automatic mapframe. Specify either a {{maplink}} template, or another template that generates a mapframe map, or an image name. If used, the subsequent mapframe parameters will be ignored. Default: not specified
  • mapframe-id or id or qid – Id (Q-number) of Wikidata item to use. Default: item for current page
  • mapframe-coordinates or mapframe-coord or coordinates or coord – Coordinates to use, instead of any on Wikidata. Use the {{Coord}} template, e.g. |coord={{Coord|12.34|N|56.78|E}}. Default: coordinates from Wikidata
  • mapframe-wikidata – Set to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

to show shape/line features from the wikidata item, if any, when |coord= is set. Default: not specified

• Customise which features are displayed:
  • mapframe-shape – Turn off display of shape feature by setting to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

. Use an inverse shape (geomask) instead of a regular shape by setting to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

. Default: not specified

• • mapframe-point – Turn off display of point feature by setting to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

. Force point marker to be displayed by setting to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

. Default: not specified

• • mapframe-line – Turn off display of line feature by setting to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

. Default: not specified

• • mapframe-geomask – Wikidata item to use as a geomask (everything outside the boundary is shaded darker). Can either be a specific Wikidata item (Q-number), or a property that specifies the item to use (e.g. P17 for (P17), P131 for (P131)). Default: monument
  • mapframe-switcher – set to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

or

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

or

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

to enable Template:Switcher-style switching between multiple mapframes. Default: not specified

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

– switch geomasks found in  (P276) and  (P131) statements on the page's Wikidata item, searching recursively. E.g. an item's city, that city's state, and that state's country.

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

– switch between the geomasks specified as a comma-separated list of Wikidata items (Q-numbers) in the mapframe-geomask parameter

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

– switch between "zoomed in"/"zoomed midway"/"zoomed out", where "zoomed in" is the default zoom (with a minimum of

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, {{code}} generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

), "zoomed out" is

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

, and "zoomed midway" is the average

• Other optional parameters:
  • mapframe-frame-width or mapframe-width – Frame width. Default: 270
  • mapframe-frame-height or mapframe-height – Frame height. Default: 200
  • mapframe-shape-fill – Color used to fill shape features. Default: #606060
  • mapframe-shape-fill-opacity – Opacity level of shape fill, a number between 0 and 1. Default: 0.5
  • mapframe-stroke-color or mapframe-stroke-colour – Color of line features, and outlines of shape features. Default: #ff0000
  • mapframe-stroke-width – Width of line features, and outlines of shape features; default is "5". Default: 5
  • mapframe-marker – Marker symbol to use for coordinates; see mw:Help:Extension:Kartographer/Icons for options. Default: monument
    • Can also be set to

Usage

Wraps a short span of text in <syntaxhighlight> tags (see mw:Extension:SyntaxHighlight). This template should be used for short samples; longer content should use <pre>...</pre> or <syntaxhighlight>...</syntaxhighlight>. See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly: {{code|1=date=30 Feb 2010}}.

The template uses the <syntaxhighlight> tag with the attribute inline=1. This works like the combination of the <code> and <nowiki> tags, applied to the expanded wikitext. For example, {{code|some '''wiki''' text}} will not render the word "wiki" in bold, and will render the tripled-single-quotes:

However, {{code|a {{template}} call}} will still invoke the template:

Use <nowiki>...</nowiki> around the template name to avoid this problem:

When used inline with regular text, generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:

is well spaced:

foo    quux.

versus:

which is going to be visually confusing for many:

foo quux.

because "foo" and "" will seem more closely associated than "" and ""; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter {{{2}}} (unnamed, as |2=, or more explicitly as |lang=) to specify a language for mw:Extension:SyntaxHighlight. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though and are valid values, as are , , , , and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Examples

Markup	Renders as

Included templates

Embedded templates do not function as expected inside {{code}}; for longer, free-form blocks of code, which can contain templates such as {{var}} and {{samp}}, use <code>...</code> as a wrapper instead of this template.

Templates used inside {{code}} expose the rendered HTML— this can be useful. For example:

Markup	Renders as

The above example shows the HTML rendered by the citation template, including the hidden metadata.

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Infobox artwork

See also

• {{codett}}, wrapper for this template that removes background and border styling
• {{mono}}, monospaced font only
• {{param value}}, monospaced; friendly handling for blank space
• {{Syntaxhighlight}}
• {{kbd}}, for keyboard input
• Help:Wiki markup

to override any default marker symbol

• • mapframe-marker-color or mapframe-marker-colour – Background color for the marker. Default: #5E74F3
  • mapframe-geomask-stroke-color or mapframe-geomask-stroke-colour – Color of outline of geomask shape. Default: #555555
  • mapframe-geomask-stroke-width – Width of outline of geomask shape. Default: 2
  • mapframe-geomask-fill – Color used to fill outside geomask features. Default: #606060
  • mapframe-geomask-fill-opacity – Opacity level of fill outside geomask features, a number between 0 and 1. Default: 0.5
  • mapframe-zoom – Set the zoom level, from "1" (map of earth) to "18" (maximum zoom in), to be used if the zoom level cannot be determined automatically from object length or area. Default: 10
  • mapframe-length_km or mapframe-length_mi or mapframe-area_km2 or mapframe-area_mi2 – Determine zoom level by passing in object's length (in kilometres or miles) or area (in square kilometres or square miles). Default: not specified
  • mapframe-frame-coordinates or mapframe-frame-coord – Alternate latitude and longitude coordinates for initial placement of map, using {{coord}}. Default: derived from item coordinates

Map type

A list of modules containing maps that may be used can be found at:

• Special:PrefixIndex/Module:Location map/data/

Examples

<syntaxhighlight lang="wikitext" style="overflow:auto;"> </syntaxhighlight>

<syntaxhighlight lang="wikitext" style="overflow:auto">

</syntaxhighlight>

TemplateData

TemplateData documentation used by VisualEditor and other tools

Click here to see a monthly parameter usage report for this template based on this TemplateData. TemplateData for Infobox artwork An infobox for artwork Template parameters This template prefers block formatting of parameters. Parameter Description Type Status Title title The title of the artwork. Defaults to the page name. String optional Image file image image_file The name of the image file to display, without the "File:" prefix File optional Image size image_size The size of the image in pixels, optionally suffixed by "px" Number deprecated Image scale image_upright Image scaling factor; reduce for portraits Default 1.36 Example 1.1 Number optional Image alternative text alt A description of the image that can be displayed instead of the image and/or read by the blind String optional Caption caption A caption to be displayed under the image String optional Infobox alignment painting_alignment The alignment of the infobox. It should almost always be "right", but can also be "left". Defaults to right-alignment. String optional Secondary title language other_language_1 The language of a secondary title String optional Secondary title other_title_1 A secondary title. String optional Tertiary title language other_language_2 The language of a tertiary title String optional Tertiary title other_title_2 A tertiary title. String optional Wikidata wikidata The QID of the specific Wikidata item String optional Artist name artist The name of the artist(s) who created the piece String optional Year year The year the artwork was created String optional Completion date completion_date The date the artwork was completed. Appears only if the year parameter is undefined. String optional Catalogue number catalogue The number of the artwork in a catalogue raisonné, e.g. "F454" String optional Type type <span style="color: #FF0000;">Deprecated:</span> The type of the artwork. Use "medium" and "movement" instead. String deprecated Medium medium The material used by the artist or designer to create the work of art Example Charcoal on paper String optional Movement movement [[Art movement]], or movements, typically associated with work of art or time during artist's career when work of art was created. Must be verifiable through sources. Example Post-Impressionism Auto value String optional Subject subject The subject(s) of the artwork String optional Height (metric) height_metric The height of the artwork in metres, centimetres, etc., without unit Number optional Width (metric) width_metric The width of the artwork in metres, centimetres, etc., without unit Number optional Length (metric) length_metric The length of the artwork in metres, centimetres, etc., without unit Number optional Height (imperial) height_imperial The height of the artwork in feet, inches, etc., without unit Number optional Height (inch addition) height_inch If the imperial unit is set to feet, this allows inch precision to be added to the height Number optional Width (imperial) width_imperial The width of the artwork in feet, inches, etc., without unit Number optional Width (inch addition) width_inch If the imperial unit is set to feet, this allows inch precision to be added to the width Number optional Length (imperial) length_imperial The length of the artwork in feet, inches, etc., without unit Number optional Length (inch addition) length_inch If the imperial unit is set to feet, this allows inch precision to be added to the length, without unit Number optional Diameter (metric) diameter_metric The diameter of the artwork in metres, centimetres, etc., without unit Number optional Diameter (imperial) diameter_imperial The diameter of the artwork in feet, inches, etc., without unit Number optional Metric unit metric_unit The unit to use as the metric unit, e.g. "m" or "cm" Default cm String optional Imperial unit imperial_unit The unit to use as the imperial or US customary unit, e.g. "in" or "ft" Default in String optional Dimensions dimensions Additional or nonstandard dimensional data can be placed here as raw wikitext. String optional Dimensions reference(s) dimensions_ref Any references concerning the artwork's dimensions can be placed here as raw wikitext (including "ref" tags). String optional Weight weight The weight of the artwork String optional Designation designation The legal protection granted to the artwork String optional Condition condition The condition of the artwork String optional Museum museum The museum that currently houses the artwork String optional City city The city in which the artwork is currently located String optional Coordinates coordinates Coordinates for the artwork, input as a coordinate template String optional Owner owner The current owner of the artwork String optional Accession number accession The accession number(s) for the artwork String optional Module module An embedded template String optional Website website Website for the artwork, input as a URL template String optional Italic title italic title Set to no if automatic title italicization is not required. Set to force if the title is not being italicized when it should be. Example no Line optional

Microformat

The HTML mark-up produced by this template includes an hCalendar microformat that makes event details readily parsable by computer programs. This aids tasks such as the cataloguing of articles and maintenance of databases. For more information about the use of microformats on Wikipedia, please visit the Microformat WikiProject.

Classes used

The HTML classes of this microformat include:

Please do not rename or remove these classes
nor collapse nested elements which use them.

Tracking categories

• [[:Category:|Category:]] (0)
• [[:Category:|Category:]] (0) (can be safely removed or ignored)
• [[:Category:|Category:]] (0) (can be replaced with |medium=)
• [[:Category:|Category:]] (0) (for potential linking)

See also

• {{Infobox artwork/wikidata}}
• {{Infobox artist}}
• {{Image information art}}, for image pages.