The markup language called wikitext, also known as wiki markup or wikicode, consists of the syntax and keywords used by the MediaWiki software to format a page. (Note the lowercase spelling of these terms.[a]) To learn how to see this hypertext markup, and to save an edit, see Help:Editing. Generally, coding can be copied and pasted, without writing new code. There is a short list of markup and tips at Help:Cheatsheet.
In addition to wikitext, some HTML elements are also allowed for presentation formatting. See Help:HTML in wikitext for information on this.
Layout
Sections
Article sections in a page will follow that page's lead or introduction and, if there are four or more, the table of contents.
The = through ====== markup are headings for the sections with which they are associated.
A single = is styled as the article title and should not be used within an article.
Headings are styled through CSS and add an [edit] link. See this section for the relevant CSS.
Four or more headings cause a table of contents to be generated automatically.
Do not use any markup after the final heading markup – this will either break the heading, or will cause the heading to not be included in an edit summary.
The horizontal rule represents a paragraph-level thematic break. Do not use in article content, as rules are used only after main sections, and this is automatic.
Markup
Renders as
----
HTML equivalent: <hr /> (which can be indented, whereas ---- always starts at the left margin.)
When a page has at least four headings, a table of contents (TOC) will automatically appear after the lead and before the first heading. The TOC can be controlled by magic words or templates:
__FORCETOC__ forces the TOC to appear at the normal location regardless of the number of headings.
__TOC__ forces the TOC to appear at the point where the magic word is inserted instead of the normal location.
__NOTOC__ disables the TOC entirely.
{{TOC limit}} template can be used to control the depth of subsections included in the TOC. This is useful where the TOC is long and unwieldy.
Line breaks or newlines are used to add whitespace between lines, such as separating paragraphs.
A line break that is visible in the content is inserted by pressing ↵ Enter twice.
It's good practice to do this by itself when publishing changes. Leave additional changes to another edit because otherwise only the line break will be highlighted in the diff.
Pressing ↵ Enter once will place a line break in the markup, but it will not show in the rendered content, except when using list markup.
Markup such as bold or italics will be terminated at a line break.
Blank lines within indented wikitext should not be added due to accessibility issues.
Markup
Renders as
A single newline here
has no effect on the layout.
But an empty line starts a new paragraph,
or ends a list or an indented part.
A single newline here
has no effect on the layout.
But an empty line starts a new paragraph,
or ends a list or an indented part.
HTML equivalent: <br> or <br /> can be used to break line layout.
Indentation as used on talk pages:
:Each colon at the start of a line
::causes the line to be indented by three more character positions.
:::(The indentation persists
so long as no carriage return or line break is used.)
:::Repeat the indentation at any line break.
::::Use an extra colon for each response.
:::::And so forth ...
::::::And so on ...
{{Outdent|::::::}}The outdent template can give a visual indicator that we're deliberately cancelling the indent (6 levels here)
Indentation as used on talk pages:
Each colon at the start of a line
causes the line to be indented by three more character positions.
(The indentation persists
so long as no carriage return or line break is used.)
Repeat the indentation at any line break.
Use an extra colon for each response.
And so forth ...
And so on ...
The outdent template can give a visual indicator that we're deliberately cancelling the indent (6 levels here)
When there is a need for separating a block of text. This is useful for (as the name says) inserting blocks of quoted (and cited) text.
Markup
Renders as
Normal text
<blockquote>
The '''blockquote''' tag will indent both margins when needed instead of the left margin only as the colon does.
</blockquote>
Normal text
Normal text
The blockquote tag will indent both margins when needed instead of the left margin only as the colon does.
Normal text
This uses an HTML tag; template {{quote}} results in the same render.
Template {{center}} uses the same markup. To center a table, see Help:Table#Centering tables.
Please do not use <center>...</center> tags, as it is obsolete.
Align text to right
You can align content in a separate container:
Markup
Renders as
<divstyle="text-align: right; direction: ltr; margin-left: 1em;">Text on the right</div>
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Text on the right
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Or; make the text float around it:
Markup
Renders as
<divclass="floatright">Text on the right</div>
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Text on the right
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
{{stack|Text on the right}}
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Text on the right
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Do not leave blank lines between items in a list unless there is a reason to do so, since this causes the MediaWiki software to interpret each item as beginning a new list.
To list terms and definitions, start a new line with a semicolon (;) followed by the term. Then, type a colon (:) followed by a definition. The format can also be used for other purposes, such as make and models of vehicles, etc.
Description lists (formerly definition lists, and a.k.a. association lists) consist of group names corresponding to values. Group names (terms) are in bold. Values (definitions) are indented. Each group must include one or more definitions. For a single or first value, the : can be placed on the same line after ; – but subsequent values must be placed on separate lines.
Do not use a semicolon (;) simply to bold a line without defining a value using a colon (:). This usage renders invalid HTML5 and creates issues with screen readers. Also, use of a colon to indent (other than for talk page responses) may also render invalid HTML5 and cause accessibility issues per MOS:INDENTGAP.
Markup
Renders as
; Term : Definition1
Term
Definition1
; Term
: Definition1
: Definition2
: Definition3
: Definition4
Term
Definition1
Definition2
Definition3
Definition4
HTML equivalent: <dl><dt>...</dt>, <dd>...</dd></dl>
The MediaWiki software suppresses single newlines and converts lines starting with a space to preformatted text in a dashed box. HTML suppresses multiple spaces. It is often desirable to retain these elements for poems, lyrics, mottoes, oaths and the like. The Poem extension adds HTML-like <poem>...</poem> tags to maintain newlines and spaces. These tags may be used inside other tags such as <blockquote>...</blockquote>; the template {{poemquote}} provides a convenient shorthand. CSS styles may be applied to this tag, e.g.: <poemstyle="margin-left: 2em;">.
In Xanadu did Kubla Khan
A stately pleasure-dome decree:
Where Alph, the sacred river, ran
Through caverns measureless to man
Down to a sunless sea.
So twice five miles of fertile ground
With walls and towers were girdled round:
And there were gardens bright with sinuous rills,
Where blossomed many an incense-bearing tree;
And here were forests ancient as the hills,
Enfolding sunny spots of greenery.
Poems and their translation can be presented side by side, and the language can be indicated with lang="xx". Following the last side-by-side block, {{Clear|left}} must be used to cancel "float:left;" and to re-establish normal flow. Note that this method does not require a table and its columns to achieve the side-by-side presentation.
Markup
<poemlang="fr"style="float:left;">Frère Jacques, frère Jacques,
Dormez-vous? Dormez-vous?
Sonnez les matines! Sonnez les matines!
Ding, dang, dong. Ding, dang, dong.</poem><poemstyle="margin-left:2em; float:left;">Are you sleeping? Are you sleeping?
Brother John, Brother John,
Morning bells are ringing! Morning bells are ringing!
Ding, dang, dong. Ding, dang, dong.</poem>{{Clear|left}}
Renders as
Frère Jacques, frère Jacques,
Dormez-vous? Dormez-vous?
Sonnez les matines! Sonnez les matines!
Ding, dang, dong. Ding, dang, dong.
Are you sleeping? Are you sleeping?
Brother John, Brother John,
Morning bells are ringing! Morning bells are ringing!
Ding, dang, dong. Ding, dang, dong.
Format
Text formatting
Description
What you type
What it looks like
italics, bold, small capital letters
To ''italicize text'', put two consecutive apostrophes on each side of it.
Three apostrophes each side will '''bold the text'''.
Five consecutive apostrophes on each side (two for italics plus three for bold) produces '''''bold italics'''''.
'''''Italic and bold formatting''''' works correctly only within a single line.
For text as {{smallcaps|small caps}}, use the template {{tl|smallcaps}}.
To italicize text, put two consecutive apostrophes on each side of it.
Three apostrophes each side will bold the text.
Five consecutive apostrophes on each side (two for italics plus three for bold) produces bold italics.
Italic and bold formatting works correctly only within a single line.
To reverse this effect where it has been automatically applied, use {{nobold}} and {{noitalic}}.
For text as small caps, use the template {{smallcaps}}.
Small chunks of source code within a line of normal text.
Use <small>small text</small> only
when necessary.
Use small text only when necessary.
a <small> span
To match, for example, the font-size used in an [[Help:Visual file markup#Caption|image caption]], the "small" tag can also be used to
<smallstyle="font-size:87%;">reduce a text's font-size to 87%</small>.
To match, for example, the font-size used in an image caption, the "small" tag can also be used to reduce a text's font-size to 87%.
Big text
Better not use <big>big text</big>, unless <small>it's <big>within</big> small</small> text.
Better not use big text, unless it's within small text.
To prevent two words from becoming separated by a linewrap (e.g. Mr. Smith or 400 km/h) a non-breaking space, sometimes also called a "non-printing character", may be used between them. (For three or more words, the template {{nowrap}} is probably more suitable.)
Mr.&nbsp;Smith or 400&nbsp;km/h
Mr. Smith or 400 km/h
Extra spacing within text is usually best achieved using the {{pad}} template.
The <pre>, <nowiki>, and <code> markup tags are also available, for writing "[", "{", "&", "}", "]" for example. These tags prevent these characters from being recognised as wiki markup, which is a possibility in some circumstances.
WikiHiero is a software extension that renders Egyptian hieroglyphs as PNG images using <hiero> HTML-like tags.
Example:
Markup
Renders as
<hiero>P2</hiero>
Subscripts and superscripts
The Manual of Style prefers the <sub> and <sup> formats, for example x<sub>1</sub>. So this should be used under most circumstances.
The latter methods of sub/superscripting cannot be used in the most general context, as they rely on Unicode support that may not be present on all users' machines.
Invisible and PUA (Private Use Areas) characters should be avoided where possible. When needed, they should both be replaced with their (hexa)decimal code values (as "&#(x)...;"). This renders invisible characters visible, for manual editing, and allows AWB to process pages with PUA characters. The latter should also be tagged with the {{PUA}} template for tracking and future maintenance.
Formulae that include mathematical letters, like x, and operators like × should not use the plain letter x. See math font formatting. For a comprehensive set of symbols, and comparison between <math> tags and the {{math}} template see section TeX vs HTML.
The <math> tag typesets using LaTeX markup,[b] which may render as an image or as HTML, depending on environmental settings. The <math> tag is best for the complex formula on its own line in an image format. If you use this tag to put a formula in the line with text, put it in the {{nowrap}} template.
The {{math}} template uses HTML, and will size-match a serif font, and will also prevent line-wrap. All templates are sensitive to the = sign, so remember to replace = with {{=}} in template input, or start the input with 1=. Use wiki markup '' and ''' inside the {{math}} template, as well as other HTML entities. The {{math}} template is best for typeset formulas in line with the text.
Using to prevent line break is not needed; the {{math}} template will prevent line breaks anyway; you can use <br /> if you need an explicit line break inside a formula.
Markup
Renders as
It follows that {{math|''x''<sup>2</sup>≥ 0}} for real {{mvar|x}}.
Wikilinks are used in wikitext markup to produce internal links between pages. You create wikilinks by putting double square brackets around text designating the title of the page you want to link to. Thus, [[Texas]] will be rendered as Texas. Optionally, you can use a vertical bar (|) to customize the link title. For example, typing [[Texas|Lone Star State]] will produce Lone Star State, a link that is displayed as "Lone Star State" but in fact links to Texas.
Link to another wiki article
Internally, the first letter of the target page is automatically capitalized and spaces are represented as underscores (typing an underscore in the link has the same effect as typing a space, but is not recommended).
Thus the link hereafter is to the Web address en.wikipedia.org/wiki/Public_transport, which is the Wikipedia article with the name "Public transport". See also Canonicalization.
A red link is a page that doesn't exist yet; it can be created by clicking on the link.
Simply typing the pipe character | after a link will automatically rename the link in certain circumstances. The next time you open the edit box you will see the expanded piped link. When previewing your edits, you will not see the expanded form until you press Save and Edit again. The same applies to links to sections within the same page.
The part after the hash sign (#) must match a section heading on the page. Matches must be exact in terms of spelling, case, and punctuation. Links to non-existent sections are not broken; they are treated as links to the beginning of the page.
Include "| link title" to create a stylish (piped) link title.
If sections have the same title, add a number to link to any but the first. #Example section 3 goes to the third section named "Example section". You can use the pipe and retype the section title to display the text without the # symbol.
What you type
What it looks like
[[Wikipedia:Manual of Style#Italics]] is a link to a section within another page.
[[#Links and URLs]] is a link to another section on the current page. [[#Links and URLs|Links and URLs]] is a link to the same section without showing the # symbol.
#Links and URLs is a link to another section on the current page. Links and URLs is a link to the same section without showing the # symbol.
[[Wikipedia:Manual of Style#Italics|Italics]] is a piped link to a section within another page.
Italics is a piped link to a section within another page.
Create a page link
To create a new page:
Create a link to it on some other (related) page.
Save that page.
Click on the link you just made. The new page will open for editing.
Redirect one article title to another by placing a directive like the one shown to the right on the first line of the article (such as at a page titled "US").
It is possible to redirect to a section. For example, a redirect to United States#History will redirect to the History section of the United States page, if it exists.
After the launch of Wikidata, interlanguage links are now added through it. Links in articles should exist only in special cases, for example when an article in one language has two articles in another language.
To link to a corresponding page in another language, use the form: [[language code:Foreign title]].
It is recommended interlanguage links be placed at the very end of the article.
Interlanguage links are NOT visible within the formatted article, but instead appear as language links on the sidebar (to the left) under the menu section "languages".
To put an article in a category, place a link like [[Category:Example]] into the article. As with interlanguage links, placing these links at the end of the article is recommended.
To link to a category page without putting the article into the category, use a colon prefix (":Category") in the link.
Single-square brackets indicate an external link. Note the use of a space (not a pipe |) to separate the URL from the link text in a named link. Square brackets may be used as normal punctuation when not linking to anything – [like this].
A URL must begin with a supported URI scheme: https:// (preferably) and http:// will be supported by all browsers; irc://, ircs://, ftp://, news://, mailto:, and gopher:// will require a plugin or an external application. IPv6 addresses in URLs are currently not supported.
A URL containing certain characters will display and link incorrectly unless those characters are percent encoded. For example, a space must be replaced by %20. Encoding can be achieved by:
Use the link button on the enhanced editing toolbar to encode the link; this tool will add the bracket markup and the linked text, which may not always be desirable.
Or manually encode the URL by replacing these characters:
space
"
'
,
;
<
>
?
[
]
%20
%22
%27
%2c
%3b
%3c
%3e
%3f
%5b
%5d
Or use the {{urlencode:}} magic word. See Help:Magic words in the MediaWiki documentation for more details.
These create links that directly go to the edit or view source tab. For example, to create links to the edit tab for this page, either of the following works:
The picture name alone places the image in the text, or on the next line if there is insufficient space.
Embedding the image in the text is only possible for very small images.
Embedding the image will affect the vertical formatting of text.
With alternative text:
[[File:wiki.png|alt=Puzzle globe logo]]
With alternative text:
Alternative text, used when the image is unavailable or when the image is loaded in a text-only browser, or when spoken aloud, is strongly encouraged. See Alternative text for images for help on choosing it.
With link:
[[File:wiki.png|link=Wikipedia]]
With link:
The link directs to the Wikipedia page, Wikipedia, instead of the image file page.
Forced to the centre of the page
using the ''frame'' tag (attribute), a ''centre'' tag and a caption:
[[File:wiki.png|frame|centre|alt=Puzzle globe|Wikipedia logo]]
Forced to the centre of the page using the frame tag (attribute), a centre tag and a caption:
The frame tag automatically floats the image right.
The frame tag is only of use with very small images or ones using the px tag
The attributes left, center or centre override this, and places the image to the left or the centre of the page.
The last parameter is the caption that appears below the image.
Forced to the left side of the page
using the ''thumb'' attribute, the ''left'' attribute and a caption:
[[File:wiki.png|thumb|left|alt=Puzzle globe|Wikipedia logo]]
Forced to the left side of the page using the thumb attribute, the left attribute and a caption:
The thumb tag automatically floats the image right.
An enlarge icon is placed in the lower right corner.
The attributes left, center or centre override this, and places the image to the left or the centre of the page.
Forced to the right side of the page
''without'' a caption:
[[File:wiki.png|right|Wikipedia encyclopedia]]
Forced to the right side of the page without a caption:
Captions are only displayed when the thumb or frame attributes are present
Making a reference citing a printed or online source can be accomplished by using the <ref> wiki markup tags. Inside these tags details about the reference are added.
Details about the citation can be provided using a structure provided by various templates; the table below lists some typical citation components.
Examples for templates: {{pad|...}}, {{math|...}}, {{as of|...}}, {{edit}}
Templates are segments of wiki markup that are meant to be copied automatically ("transcluded") into a page.
They are specified by putting the template's name in {{double braces}}. Most templates are pages in the Template namespace, but it is possible to transclude mainspace pages (articles) by using {{:colon and double braces}}.
There are three pairs of tags that can be used in wikitext to control how transclusion affects parts of a template or article.
They determine whether or not wikitext renders, either in its own article, which we will call "here", or in another article where it is transcluded, which we will call "there".
<noinclude>: the content will not be rendered there. These tags have no effect here.
<includeonly>: the content will render only there, and will not render here (like invisible ink made visible by means of transclusion).
<onlyinclude>: the content will render here and will render there, but it will only render there what is between these tags.
There can be several such section "elements". Also, they can be nested. All possible renderings are achievable. For example, to render there one or more sections of the page here use <onlyinclude> tags. To append text there, wrap the addition in <includeonly> tags before, within, or after the section. To omit portions of the section, nest <noinclude> tags within it.
If a page is transcluded without transclusion markup, it may cause an unintentional categorization. Any page transcluding it will contain the same category as the original page. Wrap the category markup with <noinclude> tags to prevent incorrect categorization.
Some templates take parameters, as well, which you separate with the pipe character |.
This transclusion demo is a little bit of text from the page Help:Transclusion demo to be included into any file.
This template takes two parameters,
and creates underlined text with a
hover box for many modern browsers
supporting CSS:
{{Tooltip|Hover your mouse over this text
|This is the hover text}}
Go to this page to see the Tooltip
template itself: {{tl|Tooltip}}
This template takes two parameters,
and creates underlined text with a
hover box for many modern browsers
supporting CSS:
Hover your mouse over this text
Go to this page to see the Tooltip
template itself: {{Tooltip}}
Linking to old revisions of pages, diffs, and specific history pages
The external link function is mainly used for these. Open an old revision or diff, and copy the URL from the address bar, pasting it where you want it.
What you type
What it looks like
[https://en.wikipedia.org/w/index.php?title=Help:Wiki_markup&diff=330350877&oldid=330349143Diff between revisions 330349143 and 330350877]
For an old revision, you can also use a permalink. Though here only the main text is guaranteed to be retained (images and templates will be shown as they are today, not as they were at the time).
I will change the color in {{color|blue|the middle part of}} this sentence.
I will change the color in the middle part of this sentence.
This is how to {{Font color||yellow|highlight part of a sentence}}.
This is how to highlight part of a sentence.
Example text
The {{xt}} family of templates can be used to highlight example text. These templates do not work in mainspace—that is, in regular articles—they are intended for use on project pages (such as Wikipedia:Manual of Style), help pages, and user pages.
What you type
What you get
This is {{xt|a correct example}} for comparison {{tick}}
This is a correct example for comparison Y
This is {{!xt|an incorrect example}} for contrast {{cross}}
When editing regular Wikipedia articles, just make your changes, and do not mark them up in any special way, except when the article itself discusses deleted or inserted content, such as an amendment to a statute:
to indicate deleted content, use <del>...</del>
to indicate inserted content, use <ins>...</ins>
This also applies to changing one's own talk page comments.
What you type
What it looks like
You can <del>indicate deleted material</del> and <ins>inserted material</ins>.
You can indicate deleted material and inserted material.
The {{Strikethrough}} template marks up a span of text with the <s>...</s> tag. This is usually renderend visually by drawing a horizontal line through it. Outside of articles, it can be used to mark something as no longer accurate or relevant without removing it from view. Do not use it, however, to indicate document edits. For that, use the <del>...</del> tag instead. See § Show deleted or inserted text for details.
What you type
What you get
This is {{Strikethrough|an obsolete stretch of text}} for comparison
This is an obsolete stretch of text for comparison
Limiting formatting / escaping wiki markup
A few different kinds of formatting will tell the wiki to display things as you typed them – what you see is what you get!
What you type
What it looks like
'''<nowiki> tag:'''<nowiki>
The <nowiki> tag ignores [[wiki]]
''markup''. It reformats text by
removing newlines and multiple
spaces. It still interprets
characters specified by
&name;: →</nowiki>
<nowiki> tag:
The <nowiki> tag ignores [[wiki]]
''markup''. It reformats text by
removing newlines and multiple
spaces. It still interprets
characters specified by
&name;: →
'''<pre> tag:'''<pre>The <pre> tag ignores [[wiki]]
''markup'' as does the <nowiki>
tag. Additionally, <pre> displays
in a mono-spaced font, and does
not reformat text spaces.
It still interprets special
characters: →</pre>
<pre> tag:
The <pre> tag ignores [[wiki]]
''markup'' as does the <nowiki>
tag. Additionally, <pre> displays
in a mono-spaced font, and does
not reformat text spaces.
It still interprets special
characters: →
'''[Text without a URL]:'''
Single square brackets holding
[text without a HTTP URL] are
preserved, but single square
brackets containing a URL are
treated as being an external
[https://example.com/ Web link].
[Text without a URL]:
Single square brackets holding
[text without a HTTP URL] are
preserved, but single square
brackets containing a URL are
treated as being an external
Web link.
'''Leading space:'''
Leading spaces are another way
to preserve formatting.
Putting a space at the
beginning of each line
stops the text from
being reformatted.
It still interprets [[wiki]]''markup'' and special characters: &
Leading space:
Leading spaces are another way
to preserve formatting.
Putting a space at the
beginning of each line
stops the text from
being reformatted.
It still interprets wikimarkup and special characters: →
<nowiki>...</nowiki> (wiki markup contained between these two tags is displayed as normal text)
<nowiki /> (wiki markup that is interrupted by this tag is displayed as normal text, as detailed in examples below)
These two kinds of nowiki operate in different ways, but both neutralize the rendering of wiki markup as shown in the examples below. For example, the characters that have wiki markup meaning at the beginning of a line (*, #, ; and :) can be rendered in normal text. Editors can normalize the font of characters trailing a wikilink, which would otherwise appear in the wikilink font. And newlines added to wikitext for readability can be ignored.
Note to template editors: tag <nowiki> works only on its source page, not the target.
The rest of the section consists of simple, live examples showing how a single nowiki tag escapes entire linkage structures, beyond [[wikilink]] and {{template}}:
Unless you use the two "balanced" nowiki tags, troubleshooting strip marker errors and template parameter-handling inconsistencies is a risk. Also, a rendering error may arise when two [[...]] square brackets are on the same line, or two {{...}} curly brackets are in the same section, but only when the two have the nowiki markup placed inconsistently.
Displaying wikilinks
(These are all live examples.)
Markup
Renders as
[[ wp:pagename | page name ]]
[<nowiki/>[ wp:pagename | page name ]]
[[<nowiki/> wp:pagename | page name ]]
[[ wp:pagename <nowiki/>| page name ]]
[[ wp:pagename | page name ]<nowiki/>]
page name [[ wp:pagename | page name ]] [[ wp:pagename | page name ]] [[ wp:pagename | page name ]] [[wp:pagename | page name ]]
For nested structures, escaping an inner structure escapes its outer structure too.
For input parameters, {{{1}}}, {{{2}}}, just write them out, unless they have a default (which goes behind their pipe):
{{<nowiki />{1|default}}} → {{{1|default}}}
For a parser function nowiki goes between bracketing-pair characters, or anywhere before the : colon.
Tags do not display; they are just markup. If you want them to, insert <nowiki /> after an < opening angle bracket; it goes only in the very front. Opening tags and closing tags must be treated separately.
Markup
Renders as
<spanstyle=color:blue> Blue </span>
<<nowiki/>span style=color:blue> Blue <<nowiki/>/span>
<sectionend=la<nowiki/>bel />
<<nowiki/>section end=label />
Blue <span style=color:blue> Blue </span> bel /> N <section end=label /> Y
Use template {{tag}} instead of nowiki tags to display parser tags:
Character entities, nowiki cannot escape.
To escape HTML or special character entities, replace & with &.
For example, &lt; → <
To display a nowiki tag, you can (1) use {{tag}}, (2) replace the < left angle bracket with its HTML character entity, or (3) nest nowiki tags in each other:
12<nowiki>34</nowiki> second and fourth {{!}}<nowiki>|</nowiki>
These simply scan from left to right.
The paired tags cannot overlap, because the very first pair-match nullifies any intervening tags inside. Unbalanced tags always display.
Nowiki tags do not display table markup, use <pre>...</pre>.
<pre> is a parser tag that emulates the HTML <pre> tag. It defines preformatted text that is displayed in a fixed-width font and is enclosed in a dashed box. HTML-like and wiki markup tags are escaped, spaces and line breaks are preserved, but HTML elements are parsed.
<pre> examples
Markup
Renders as
<pre><!--Comment-->
[[wiki]] markup &</pre>
<!--Comment-->
[[wiki]] markup &
As <pre> is a parser tag, it escapes wikitext and HTML tags. This can be prevented with the use of <includeonly></includeonly> within the <pre>, making it act more like its HTML equivalent:
It's uncommon – but on occasion acceptable for notes to other editors – to add a hidden comment within the text of an article. These comments are visible only when editing or viewing the source of a page. Most comments should go on the appropriate Talk page. The format is to surround the hidden text with "<!--" and "-->" and may cover several lines, e.g.:
<!-- An example of hidden comments
This won't be visible except in "edit" mode. -->
Another way to include a comment in the wiki markup uses the {{Void}} template, which can be abbreviated as {{^}}. This template "expands" to the empty string, generating no HTML output; it is visible only to people editing the wiki source. Thus {{^|A lengthy comment here}} operates similarly to the comment <!-- A lengthy comment here -->. The main difference is that the template version can be nested, while attempting to nest HTML comments produces odd results.
{{ns:index}} e.g. {{ns:1}} → full name of namespace
{{SITENAME}}
Wikipedia
{{NUMBEROFARTICLES}} is the number of pages in the main namespace that contain a link and are not a redirect. This includes full articles, stubs containing a link, and disambiguation pages.
{{CURRENTMONTHNAMEGEN}} is the genitive (possessive) grammatical form of the month name, as used in some languages but not in English; {{CURRENTMONTHNAME}} is the nominative (subject) form, as usually seen in English.
In languages where it makes a difference, you can use constructs like {{grammar:case|word}} to convert a word from the nominative case to some other case. For example, {{grammar:genitive|{{CURRENTMONTHNAME}}}} means the same as {{CURRENTMONTHNAMEGEN}}.
* {{subst:uw-vandalism1|PageName}}~~~~ (unintentional vandalism/test)
* {{subst:uw-delete1|PageName}}~~~~ (unintentional removal of content)
* {{subst:uw-vandalism2|PageName}}~~~~ (suitable for intentional nonsense or disruption)
* {{subst:uw-delete2|PageName}}~~~~ (variant for removal of content)
* {{subst:uw-vandalism3|PageName}}~~~~ ("please stop" for use after level 2 warning)
* {{subst:uw-delete3|PageName}}~~~~ (please stop removing content)
* {{subst:uw-vandalism4|PageName}}~~~~ (last warning for vandalism)
* {{subst:uw-delete4|PageName}}~~~~ (last warning for removing content)
* {{subst:uw-vandalism4im|PageName}}~~~~ (only warning; for severe or grotesque vandalism only)
* {{subst:uw-delete4im|PageName}}~~~~ (only warning; for many blankings in a short period of time)
For a listing of current collaborations, tasks, and news, see the Community portal. For a listing of ongoing discussions and current requests, see the Dashboard.