Help:Wikitext

src: clipart-library.com

Wikitext, also known as Wiki markup or Wikicode, consists of the syntax and keywords used by the MediaWiki software to format a page. To learn how to see this markup, and to save an edit, see: Help:Editing. 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.

Video Help:Wikitext

Layout

Sections

Sections in a page will follow the page's lead/introduction and (under certain conditions,) the Table of Contents.

Section headings

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.

Templates: {{fake heading}} for use in documentation.

Horizontal rule

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.

HTML equivalent: <hr />

Table of contents

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}} can be used to control the depth of subsections included in the TOC. This is useful where the TOC is long and unwieldy.
• Category:Wikipedia table of contents templates contains a number of specialized TOC templates.

Line breaks

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.
• 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.

HTML equivalent: <br> or <br />

Templates:

• {{break}} adds multiple line breaks.
• {{-}} and {{clear}} adds a break with styling, to clear floating elements.
• {{plainlist}} and {{unbulleted list}} both create an unbulleted list.

Indent text

Indentation is most commonly used on talk pages.

Templates: {{outdent}}, {{outdent2}}

Blockquote

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.

Center text

Template {{center}} uses the same markup. To center a table, see Help:Table#Centering tables. Please do not use <center>...</center>, as it is obsolete.

Align text to right

You can align content in a separate container:

Or; make the text float around it:

Lists

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.

Unordered lists

Ordered lists

Description lists

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.

HTML equivalent: <dl> <dt>...</dt>, <dd>...</dd> </dl>

Templates: {{defn}}

Retaining newlines and spaces

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>. CSS styles may be applied to this tag, e.g.: <poem style="margin-left: 2em;">.

Maps Help:Wikitext

Format

Text formatting

Special characters

Special characters can often be displayed using numeric character references or character entity references. See Character encodings in HTML for more information. For example, À and À both render À (A-grave). Percent-encoding can't be used, as it works only in URLs.

Diacritical marks

Diacritic marks, using character entity references.

Punctuation special characters

Using character entity references.

Escaping punctuation characters

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.

Commercial symbols

Using character entity references.

Greek characters

Using character entity references.

Egyptian hieroglyphs

WikiHiero is a software extension that renders Egyptian hieroglyphs as PNG images using <hiero> tags.

Example:

Chess symbols

For example, ♔ displays ?

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.

Characters in the Private Use Area, and invisible formatting characters

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.

Mathematical characters and formulae

Mathematical characters

• See also Wikipedia:Mathematical symbols, WikiProject Mathematics and TeX.

Mathematical formulae

• 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, 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 wikimarkup '' and ''' inside the {{math}} template, as well as other HTML entities. The {{math}} template is best for typeset formulas in line with the text.

Spacing in simple math formulae

• 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.

Complicated formulae

• See Help:Displaying a formula for how to use <math>.
• A formula displayed on a line by itself should probably be indented by using the colon (:) character.

src: i.ytimg.com

Links and URLs

Free links

In Wikipedia and some other wikis, free links are used in wikitext markup to produce internal links between pages, as opposed to the concept of CamelCase for the same purpose, which was used in the early days of Wikipedia - see CamelCase and Wikipedia.

In Wikipedia's markup language, you create free links 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.
• A link to its own page will appear only as bold text.

Renamed link

• Same target, different name.
• The target ("piped") text must be placed first, then the text to be displayed second.

Automatically rename links

• 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.
• See Pipe trick for details.

Blend link

• Endings are blended into the link.
  • Exception: a trailing apostrophe (') and any characters following the apostrophe are not blended.
• Preferred style is to use this instead of a piped link, if possible.
• Blending can be suppressed by using the <nowiki /> tag, which may be desirable in some instances.

Link to a section of a 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.

Create a page link

• To create a new page:
  1. Create a link to it on some other (related) page.
  2. Save that page.
  3. Click on the link you just made. The new page will open for editing.
• For more information, see starting an article and check out Wikipedia's naming conventions.
• Please do not create a new article without linking to it from at least one other article.

Redirects

• 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 "USA").
• 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.

Link to another namespace

• The full page name should be included in double square brackets.

Link to the same article in another language (interlanguage links)

• 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".

• NOTE: To create an inline link (a clickable link within the text) to any foreign language article, see Help:Interlanguage links#Inline interlanguage links and consider the usage notes.

Interwiki link

• Interwiki links link to any page on other wikis. Interwikimedia links link to other Wikimedia wikis.
• Note that interwikimedia links use the internal link style, with double square brackets.
• See MetaWikiPedia:Interwiki_map for the list of shortcuts; if the site you want to link to is not on the list, use an external link.
• See also Wikimedia sister projects.

Categories

• 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.

External links

• 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: http:// and https:// 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:

• Or use the {{urlencode:}} magic word. See Help:Magic words in the MediaWiki documentation for more details.

• See External links for style issues, and External link file type templates for indicating the file type of an external link with an icon.

Automatic links

Magic links are automatic links for certain unique identifiers that require no markup. They can be used for ISBN numbers, RFC numbers, and PMID numbers.

Book sources

• Link to books using their ISBN, which creates a link to Special:BookSources. This is preferred to linking to a specific online bookstore, because it gives the reader a choice of vendors. However, if one bookstore or online service provides additional free information, such as table of contents or excerpts from the text, then a link to that source will aid the user and is recommended. ISBN links do not need any extra markup, provided you use one of the indicated formats.
• To create a link to Special:BookSources using alternative text (e.g. the book's title), use the internal link style with the appropriate namespace.

RFC number

• Link to an Internet Engineering Task Force Request for Comments (RFC).

Miscellaneous

"As of" template

• The As of template generates phrases like "As of April 2009" or "as of April 2009", and categorize information that will need updating. For an explanation of the parameters see the {{As of}} documentation.

Media link

• To include links to non image uploads such as sounds, use a "media" link. For images, see next section.
• Some uploaded sounds are listed at Commons:Sound.

Links directly into edit mode

• 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:

Links partially italicized

• Linking to a page with a title containing words that are usually italicized, such as the Hindenburg disaster article.

src: upload.wikimedia.org

Pronunciation aids

It is often desirable to provide an aid to pronunciation for a word. The IPAc-en and Respell templates can be of assistance.

Refer to Wikipedia:Manual of Style (pronunciation) for more information.

src: i.ytimg.com

Musical notation

Musical notation is added by using the <score>...</score> extension tag. For example:

src: pbs.twimg.com

Images

Only images that have been uploaded to Wikipedia can be used. To upload images, use the upload page. You can find the uploaded image on the image list.

See the Wikipedia's image use policy for the policy used on Wikipedia.

For further help on images, including some more versatile abilities, see the picture tutorial and extended image syntax.

src: i.ytimg.com

Tables

There are two ways to build tables:

• In special wiki-markup (see Help:Table).
• Using HTML elements: <table>, <tr>, <td> or <th>.

See also When tables are appropriate.

src: wiki.phdsc.org

Columns

Use {{colbegin}} and {{colend}} to produce columns.

src: i.ytimg.com

References and citing sources

Making a reference citing a printed or online source can be accomplished by using the <ref>...</ref> 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.

src: i.ytimg.com

Templates and transcluding pages

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. You add them by putting the template's name in {{double braces}}. It is also possible to transclude other pages 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 |.

src: upload.wikimedia.org

Talk and project pages

These are likely to be helpful on talk and project pages.

Signing comments

• The tilde character (~) is used when signing a comment on a talk page. Your username provides a link to your user page.

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.

• You can also use an internal diff link. Unlike the template {{diff}}, this kind of link can even be used in edit summaries.

• If the diff intended to be shown is between an immediately previous revision, the first parameter can be dropped.

• 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).

What links here, and recent changes linked

• The following markup can be used. For example, for the article Beetroot:

User edits

• Link to a user's contributions page.

Coloring and highlighting text

• Using the {{Color}} and {{Font color}} templates:

Show deleted or inserted text

• When editing your own previous remarks in talk pages, it is sometimes appropriate to mark up deleted or inserted content:
  • It is best to indicate deleted content using the strike-through markup <s>...</s>.
  • It is best to indicate inserted content using the underline markup <u>...</u>.
• When editing regular Wikipedia articles, just make your changes, and do not mark them up in any special way. However, when the article itself discusses deleted or inserted content, such as an amendment to a statute:
  • It is best to indicate deleted content using the strike-through markup <del>...</del>.
  • It is best to indicate inserted content using the underline markup <ins>...</ins>.

Note: <s></s> and <u></u> (speced in HTML 3 & 4) are considerably more popular than <del></del> and <ins></ins> (speced in HTML 5) on Wikipedia.

src: i.ytimg.com

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!

Nowiki

In order for the software to interpret wiki markup, its parser first scans the page. When it sees its nowiki tags

<nowiki>...</nowiki> (escapes all contained wiki markup), and

<nowiki /> (escapes the interpretations it is designed to "break"),

it escapes its wikicode, so editors can document its markup using its markup.

Article editors can normalize the font of characters trailing [[...]]outside a wikilink, which would otherwise adhere to the wikilink font. They can also add line-spacing in the wikitext. Template editors: tag <nowiki> works only on its source page, not the target; also {{#tag:nowiki | content}}, although it wraps that content in nowiki tags, it also does a pre-save transform on that content, which is entirely at odds with the intended purpose of nowiki for templates, subst, signatures, and the pipe-trick.

The two kinds of nowiki operate in different ways to target content, but they both remove meaning (subtract rendering) of wiki markup, then disappear into the background font. Nowiki does nothing toward rendering, but it can add newlines to wikitext (for readability), just like the HTML comment (the preferred method) can. Unlike it does for wiki markup, nowiki does not remove the meaning of character entities, either HTML or MediaWiki special characters.

There is only one meaning for what <nowiki>...</nowiki> contains, so it needs few examples; but the singular <nowiki /> tag "contains" many linkage structures, where it is expected between bracketing-pair characters or in the keyword area. So this section has many examples and few mis-examples.

For example, only at the beginning of a line (bol of wikitext, bol in a transclusion, or beginning of a table cell), do *, #, ; or : mean something.

The rest of the section consists of simple, live examples showing how a single nowiki tag escapes entire linkage structures, beyond [[ wikilink ]] and {{ template }}:

[[ fullpagename | label ]]

{{ pagename | parameter }}

[[fullpagename | {{ pagename }} ]]

{{ pagename | [[ fullpagename ]] }}

{{ pagename | {{ pagename }} }}

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.)

  [[ wp:pagename | page name ]]  [<nowiki />[ wp:pagename | page name ]]  [[<nowiki /> wp:pagename | page name ]]  [[ wp:pagename <nowiki />| page name ]]  [[ wp:pagename | page name ]<nowiki />]  

For nested structures, escaping an inner structure escapes its outer structure too.

  [[ wp: {{ 1x | pagename }} ]]  [[ wp: {<nowiki />{ 1x | pagename }} ]]  [[ wp: {{<nowiki /> 1x | pagename }} ]]  [[ wp: {{ 1x <nowiki />| pagename }} ]]  

For two, first pipes, two nowiki tags are required:

  [[ wp: pagename | {{ 1x | label }} ]]  [[ wp: pagename <nowiki />| {{ 1x <nowiki />| label }} ]]  <nowiki>[[ wp: pagename | {{ 1x | label }} ]] </nowiki>  

Displaying template calls

For templates, put nowiki before the first pipe. If a parameter has a wikilink, put it in that, an inmost position.

  {<nowiki />{ val | u=&gt; [[ms]] | 49082 }}  {{<nowiki /> val | u=&gt; [[ms]] | 49082 }}  {{ val <nowiki />| u=&gt; [[ms]] | 49082 }}  {{ val | u= > [[ms]] | 49082 }<nowiki />}  {{ val | u= > [[ ms ]<nowiki />] | 49082 }}   

Displaying magic words

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.

  {{ #ifeq: inYes | inYes | outYes | outNo }}  {<nowiki />{ #ifeq: inYes | inYes | outYes | outNo }}  {{<nowiki /> #ifeq: inYes | inYes | outYes | outNo }}  {{ #ifeq<nowiki />: inYes | inYes | outYes | outNo }}  {{ #ifeq: inYes | inYes | outYes | outNo }<nowiki />}  

Behavioral switches expect the tag anywhere:

   1. __HIDDENCAT__   2. __HIDDENCAT<nowiki />__  

1.

2. __HIDDENCAT__

Displaying tags

<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.

  <span style=color:blue> Blue </span>  <<nowiki />span style=color:blue> Blue <<nowiki />/span>  <section end=la<nowiki />bel />   

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, < -> <

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:

  {{ tag | nowiki }}  <code>&lt; nowiki>...&lt;/ nowiki ></code>  <code><<nowiki />nowiki>...<<nowiki />/ nowiki ></code>  

  {{ tag | nowiki | s }}  <code>&lt; nowiki /></code>  <code><<nowiki /> nowiki /></code>  <code><nowiki>< nowiki /></nowiki></code>  

Nowiki tags do not otherwise nest, so it is the second and fourth that displays:

  1<nowiki>2<nowiki>3</nowiki>4</nowiki>  <nowiki>{{!}}<nowiki></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

<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 and wiki markups are escaped and spaces and line breaks are preserved, but HTML entities are parsed.

<pre> formatted text does not wrap, thus text may extend past the browser window:

  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.  

To resolve this, <pre> may use CSS styling to add wrapping or a horizontal scrollbar:

• Wrapping: <pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word;">
• Scroll bar: <pre style="overflow:auto; width:auto;">

Alternatively, consider using {{pre2}} template or <syntaxhighlight lang="text">...</syntaxhighlight>.

src: d2.alternativeto.net

Invisible text (comments)

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.

src: i.ytimg.com

Variables

{{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}}.

src: upload.wikimedia.org

HTML

Many HTML tags can be used in wiki markup. You can check your HTML by using markup validation.

src: i.ytimg.com

Common templates

src: upload.wikimedia.org

See also

See the 'Coding wiki markup' section of the Help navigation navbox below for additional links.

• Help:Magic links: magic links are automatic links for certain unique identifiers that require no markup.
• Wikipedia:Extended image syntax: advanced visual file markup.
• Help:A quick guide to templates: an introduction to templates.
• Help:Substitution: substitution is an alternative way of including templates than transclusion
• Help:Score: how to render musical scores.
• Help:Displaying a formula: displaying mathematical formulae.

Source of the article : Wikipedia