Template:Sandbox other

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together,

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 Sandbox other

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

, at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.

• Note that the closing template braces (

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 Sandbox other

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

) are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

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 Sandbox other

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together,

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 Sandbox other

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together, , at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.
• Note that the closing template braces () are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.

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

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together, , at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.
• Note that the closing template braces () are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

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 Sandbox other

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.

, at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.

• Note that the closing template braces (

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 Sandbox other

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together, , at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.
• Note that the closing template braces () are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.

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

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together, , at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.
• Note that the closing template braces () are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

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 Sandbox other

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.

) are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

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 Sandbox other

This template allows to differentiate between regular Template:... and Template:.../sandbox pages. It is typically used to prevent a /sandbox page being categorised with their main page.

Also

when numbered /sandbox1

Any subpage /sandboxANYTEXT is considered a /sandbox. So this includes /sandbox1, /sandbox_2.

Also

/doc

A /doc subpage is also considered a /sandbox.

Usage

This template can be used on template documentation pages to ensure that any given template sandbox or template documentation does not populate its main template's category(ies).

This template has two unnamed parameters, |1= and |2=. Near the bottom of a /doc page where the categories are usually placed, install this template as follows:

{{Documentation subpage}}
<!-- all /documentation code goes here -->
<includeonly>{{sandbox other||
<!-- categories the main template should be in, but not the /sandbox: -->
[[Category:(first category)]]
[[Category:(second category)]]

}}</includeonly>

• Usage of an empty first parameter (two pipes together,

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.

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

, at the end of the first line of code above) essentially means |1=(do nothing) and will not allow the sandbox page to populate the listed categories.

• Note that the closing template braces (

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.

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

) are placed just before the </includeonly> tag. This is the same as |2=(category comment and categories). In "long hand" it may appear as follows:

<includeonly>{{sandbox other|1=<!-- keep sandbox out of categories -->|2=
<!-- Categories go below this line; interwikis go to Wikidata -->
[[Category:(first category)]]
[[Category:(second category)]]
(more categories if needed)

}}</includeonly>

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.

See also

• {{Sandbox other}} — Distinguishes between the /sandbox subpages and the root template page and other subpages.
• {{Testcases other}} — Distinguishes between the /testcases subpages and the root template page and other subpages.
• {{Template other}} — Distinguishes between pages in the template namespace and other namespaces.
• {{When on basepage}} — Distinguishes between the root template page and subpages, without special consideration in the mainspace.
• {{Subpage other}} — Distinguisheds between the root page and subpages (any subpage), classifying pagenames in the mainspace with a slash as being the root page.