User:Hans Adler/MOS (structure)

This is an example of what the three main MOS subpages could look like. It begins with a section that briefly summarises the most important points and is transcluded into the main MOS page. The fact that everything is in one place makes it easier to keep the summary consistent with the detailed rules.

Some topics would fit here but are in the scope of other policy or guideline pages that are not part of the MOS. These are also summarised here, but not duplicated.

Summary
The following is a summary of the main points. For details and additional points follow the links provided at the beginnings of the sections. {{quotation|1=

Titles and headings

 * For details see: User:Hans Adler/MOS (structure)


 * There is a policy for the choice of titles, WP:TITLE.
 * Basic formatting. Generally make them nouns or short noun phrases; keep them short; use sentence case, not title case (i.e., capitalize only the first letter of the first word and any proper nouns); avoid starting with A, An or The (History of gene therapy, not The History of Gene Therapy). Avoid slashes (/), ampersands (&) and other unusual symbols. Don't link from within titles.
 * Section headings only.
 * Hierarchy. Use the hierarchy of section headings in other articles as a model (multiple equal signs are used). Make them unique within the article; they should preferably not refer to the subject of the article or of higher-level headings. *
 * Anchors and stability notes. Described here.
 * Daughter articles. If a section is covered in greater detail in a "daughter" article, flag this by inserting just under the section heading. *
 * Referring to a section without linking. Italicize the section name (italicize the actual section name only if it otherwise requires italics, such as the title of a book).
 * Appendix sections. Optional, but most articles have at least some. The order is (a) the subject's books and other works; (b) internal links to related Wikipedia articles; (c) notes and references; (d) recommended relevant publications not used as sources; (e) recommended websites not used as sources. *

Disambiguation pages

 * For details see: User:Hans Adler/MOS (structure)

Links

 * For details see: User:Hans Adler/MOS (structure)


 * Wikilinks
 * Make links only where they are relevant to the context. It is not useful and can be very distracting to mark all possible words as hyperlinks. Links should add to the user's experience; they should not detract from it by making the article harder to read. A high density of links can draw attention away from the high-value links that you would like your readers to follow up. Redundant links clutter the page and make future maintenance harder. However, ensure that the high-value links are provided.
 * Adjacent links. Avoid where possible (often one will "chain-link" to the other, anyway).
 * Be specific where possible. Link to a target page section using the pound (hash) sign where it is more focused ( Guitar, usually piped for ease of reading thus: Types of guitar ).
 * Piped links. Linking can be either direct (History of Johannesburg) or piped for the linguistic context (Johannesburg's rich history, displayed as Johannesburg's rich history).
 * Check the target. Ensure the destination is the intended article and not a disambiguation page.
 * Initial capitalization. The first letter should be capitalized only where this is normally called for, or when specifically referring to the linked article by name: Cane toads are poisonous, but lizards are typically not (see Venom).


 * External links
 * Placement. Articles can include an external links section at the end to list links to websites outside Wikipedia that contain further information, as distinct from citing sources. External links are not normally used in the body of an article.
 * Rationing. Avoid listing an excessive number of external links; Wikipedia is not a link repository.
 * Formatting. The standard format is a primary heading  followed by a bulleted list of links. External links should identify the link and briefly indicate its relevance to the article subject. For example:

The first gap triggers the boundary between link and pipe, so these will appear as:
 * History of NIH
 * National Institutes of Health homepage

Infoboxes

 * For details see: User:Hans Adler/MOS (structure)

Quotations, citations and bibliographies

 * For details see: User:Hans Adler/MOS (structure)

}}

Article titles
This section contains a summary of the policy governing the titles of Wikipedia's articles. Its guidance applies to the titles of Wikipedia articles, not to the titles of external articles that are cited. The guidance here also applies to Section headings, below.
 * Article titles should conform to Wikipedia's Article titles, including Use English.
 * Titles should match the article contents, and should be neither too narrow nor too broad.
 * Titles should be nouns or noun phrases (nominal groups): Effects of the wild, not About the effects of the wild.
 * Titles should be short—preferably fewer than ten words.
 * The initial letter of a title is capitalized (except in very rare cases, such as eBay). Otherwise, capital letters are used only where they would be used in a normal sentence (Funding of UNESCO projects, not Funding of UNESCO Projects).
 * Do not use a, an, or the as the first word (Economy of the Second Empire, not The economy of the Second Empire), unless by convention it is an inseparable part of a name (The Hague).
 * Avoid special characters such as the slash (/), plus sign (+), braces ({ }), and square brackets ([ ]); use and instead of an ampersand (&), unless the ampersand is an accepted part of a name (Emerson, Lake & Palmer).
 * The final visible character of a title should not be a punctuation mark, unless the punctuation is part of a name (Saint-Louis-du-Ha! Ha!), or an abbreviation is used (Inverness City F.C.), or a closing round bracket or quote mark is needed (John Palmer (schooner)).

Section headings

 * All of the guidance in Article titles immediately above applies to section headings, as well.
 * Headings provide an overview in the table of contents and allow readers to navigate through the text more easily.
 * Change a heading only after careful consideration, because this will break section links to it within the same article and from other articles. If changing a heading, try to locate and fix broken links.
 * Section names should preferably be unique within a page; this applies even for the names of subsections. The disadvantages of duplication are that:
 * after editing, the display can arrive at the wrong section; see also below; and
 * the automatic edit summary on editing a section with a non-unique name is ambiguous.
 * Section names should not normally contain links, especially ones that link only part of the heading; they will cause accessibility problems.
 * Section names should not explicitly refer to the subject of the article, or to higher-level headings, unless doing so is shorter or clearer. For example, Early life is preferable to His early life when his refers to the subject of the article; headings can be assumed to be about the subject unless otherwise indicated.
 * Capitalize the first letter of the first word and any proper nouns in headings, but leave the rest in lower case (Rules and regulations, not Rules and Regulations).
 * Spaced or unspaced multiple equal signs are the style markup for headings. The triple apostrophes that make words appear in boldface are not used in headings. The nesting hierarchy for headings is as follows:
 * the automatically generated top-level heading of a page is H1, which gives the article title;
 * primary headings are then, followed by  ,  , and so on.
 * Spaces between the  and the heading text are optional (  is equivalent to  ). These extra spaces will not affect the appearance of the heading, except in the edit window. (Some common bots, however, are programmed to remove them.) While editing, the spaces afford greater compatibility with browser spell checking software.
 * A blank line below the heading is optional; but do include one blank line above the heading, for readability in the edit window. (Only two or more blank lines above or below will add more white space in the public appearance of the page.)

Main article link
If the topic of a section is also covered in a dedicated article, then this should be marked by inserting directly beneath the section heading.

Section management

 * When linking to a section of an article, go to that section and leave an editor's note to inform others that the section's title is linked. List the names of the linking articles, so that if the title is altered, others can fix the links without having to perform exhaustive searches. For example:


 * As well, consider a preemptive measure to minimize link corruption when the text of a heading changes: insert an anchor with the old name, which will then still work as an alternative link to that section. For example:


 * As explained in more detail at Layout, optional appendix sections containing the following information may appear after the body of the article, in the following order: (a) a list of books or other works created by the subject of the article; (b) a list of internal links to related Wikipedia articles; (c) notes and references; (d) a list of recommended relevant books, articles, or other publications that have not been used as sources; and (e) a list of recommended relevant websites that have not been used as sources and do not appear in the earlier appendix sections.

Other pages discussing section titles

 * WP:LAYOUT

Disambiguation pages (details)
Disambiguation pages ("dab pages") are non-article pages in the article namespace, similar to redirect pages. Disambiguation pages are solely intended to allow the user to choose from a list of Wikipedia articles, usually when searching for a term that is ambiguous.

This style guideline is intended to make the process more efficient, by giving disambiguation pages a consistent look and by avoiding distracting information, such as extraneous links (internal or external). The pages should contain only disambiguation content, whether or not the page title contains the word (disambiguation). This guideline does not apply to any articles that are primary topics, even if the articles contain a "see also" notice or the like.

Page naming

 * Covered at Wikipedia:Disambiguation.

Linking to Wiktionary
Rather than including a dictionary definition of a word, create a cross-link to our sister project, Wiktionary. To do this, use one of these Wiktionary link templates on the first line:


 * Wiktionary – - up to five optional parameters; useful for linking dictionary entries with multiple capitalizations (star, Star, and STAR).
 * Wiktionary pipe – - without parameters, defaults to using the current page's name

Check the links created by these templates, as Wiktionary is case-sensitive on the first letter, using proper capitalization for its entries, unlike Wikipedia's use of an uppercase first letter for each page name.

Linking to a primary topic
When a page has "(disambiguation)" in its title – i.e., it is the disambiguation page for a term that has a primary topic – users are most likely to arrive there by clicking on a top link from the primary topic article, generated by a template in the otheruses series. For example, the article School contains the hatnote:

Since it is unlikely that this primary meaning is what readers are looking for if they have reached the disambiguation page, it should not be mixed in with the other links. It is recommended that the link back to the primary topic appear at the top, like this:


 * {| style="border: 1px solid black" width=70%

A school is an institution for learning.

School may also refer to:
 * School (discipline) or school of thought, a number of individuals with shared styles, approaches or aims
 * School (fish), a group of fish swimming in the same direction in a coordinated manner
 * }
 * }

When the primary topic is a redirect, the primary topic line normally links to the redirect:
 * {| style="border: 1px solid black" width=70%


 * Danzig is the former name of Gdańsk, a city in northern Poland.
 * }
 * }

In some cases it may be clearer to link directly to the redirect target:
 * {| style="border: 1px solid black" width=70%


 * Wolfgang Amadeus Mozart (1756–1791) was a famous composer during the Classical period.
 * instead of the more awkward
 * Mozart was Wolfgang Amadeus Mozart (1756–1791), a famous composer during the Classical period.
 * }
 * Mozart was Wolfgang Amadeus Mozart (1756–1791), a famous composer during the Classical period.
 * }
 * }

Introductory line
As in articles, the title of the page should be in bold (not italics). It should begin a sentence fragment ending with a colon, introducing a bulleted list:


 * {| style="border: 1px solid black" width=60%

Interval may refer to:

John Smith may refer to:
 * or

John Smith is the name of:

ABC may refer to:
 * or

ABC may stand for:
 * }

Where several variants of a term are being disambiguated together, significant variants may be included in the lead sentence. For example:
 * {| style="border: 1px solid black" width=60%

Bang or bangs may refer to:
 * or

Bang(s) may refer to:
 * }


 * {| style="border: 1px solid black" width=60%

Arc or ARC may refer to:
 * }


 * {| style="border: 1px solid black" width=60%


 * Angus McKay, MacKay or Mackay may refer to:
 * }
 * Angus McKay, MacKay or Mackay may refer to:
 * }

However, it is not necessary to mention minor variations of capitalization, punctuation or diacritics. For example, AU may refer to: is preferable to "AU, au, Au or A-U may refer to"; and Saiyuki may refer to: is preferable to "Saiyuki, Saiyūki or Saiyûki may refer to".

Individual entries
Individual entries follow the primary topic (if any) and the introductory line. Keep in mind that the primary purpose of the disambiguation page is to help people find the information they want quickly and easily. These pages are to help the user navigate to a specific article. Example:
 * Preface each entry with a bullet (an asterisk in wiki markup).
 * Every entry must have a link, and the link should be the first word or phrase in each entry. For example:
 * Neapolitan chord, in music theory, a major chord built on the lowered second scale degree
 * not: In music theory, a Neapolitan chord is a major chord built on the lowered second scale degree.
 * but: see Red links and Items appearing within other articles below for exceptions to this rule.
 * Start with a capital letter, unless the target article is marked with lowercase.
 * The link should not be emphasized with bolding or italics, although titles (such as for books and movies) may need to be italicized, in conformance with Manual of Style (titles). If the article's title contains both a title and a clarifier, use a piped link to quote or italicize only the part requiring such treatment, as opposed to the entire link (see below).
 * Entries should not be pipe-linked—refer to the article name in full. See below for several exceptions to this rule.
 * Entries should nearly always be sentence fragments, with no final punctuation (commas, full-stops, semicolons, etc.).


 * {| style="border: 1px solid black" width=100%


 * Interval may refer to:
 * Interval (mathematics), a certain subset of an ordered set
 * Interval (music), the relationship between two notes
 * }
 * }

There are some further points on the design of links and their entries, based on practical experience.
 * The description associated with a link should be kept to a minimum, just sufficient to allow the reader to find the correct link.


 * Each bulleted entry should have exactly one navigable (blue) link to efficiently guide users to the most relevant article for each use of the ambiguous term. Do not wikilink any other words in the line; for example:


 * {| style="border: 1px solid black" width=100%

or but not
 * "Dark Star" (song), a song by the Grateful Dead
 * "Dark Star" (song), a song by the Grateful Dead
 * "Dark Star" (song), a song by the Grateful Dead
 * "Dark Star" (song), by the Grateful Dead
 * "Dark Star" (song), a song by the psychedelic rock band The Grateful Dead
 * }
 * Including no links at all makes the entry useless for further navigation. (See "red links" below for cases in which no article yet exists.) Never link days or dates.


 * A disambiguation page should not be made up completely of red links or have only one blue link on the entire page, because the basic purpose of disambiguation is to refer users to other Wikipedia pages.
 * Never include external links, either as entries or in descriptions. Disambiguation pages disambiguate Wikipedia articles, not the World-Wide Web. To note URLs that might be helpful in the future, include them on the talk page.
 * References should not appear on disambiguation pages. Dab pages are not articles; instead, incorporate the references into the target articles.

 Examples of individual entries that should not be created
On a page called Title, do not create entries merely because Title is part of the name (see Disambiguation).

Common examples:


 * Title City
 * Title Hospital
 * Title University

The above does not apply if the subject is commonly referred to simply by Title. For instance, Oxford (disambiguation) should link University of Oxford and Catalina might include Santa Catalina Island, California. If there is disagreement about whether this exception applies, it is often best to assume that it does.

You may want to create entries on the same page for:
 * TITLE and Title
 * Title town and Title township
 * An example is Willow Valley, which lists a town of that name as well as "Willow Valley Township" in another state.

Given names or surnames
Persons who have the disambiguated term as surname or given name should not be mixed in with the other links unless they are very frequently referred to simply by the single name (e.g. Elvis, Shakespeare). For short lists of such persons, new sections of Persons with the surname Xxxx and/or Persons with the given name Xxxx can be added below the main disambiguation list. For longer lists, create an article called Xxxx (name), Xxxx (surname), Xxxx (given name), or List of people with surname Xxxx, and link to it from the disambiguation page. If it isn't clear that the article includes a list, then consider mentioning that in the description. For example: Pages only listing persons with a certain given name or surname (unless they are very frequently referred to by that name alone) are not disambiguation pages, and this Manual of Style does not apply to them. In such cases, do not use disambig or hndis, but given name or surname instead.
 * Florence (name), a female given name (includes a list of people with this name)
 * Hunter (name), a given name and a family name (including a list of people with that name)

Misspellings
Common misspellings should be listed only if there is a genuine risk of confusion or misspelling. These cross-links should be placed in a separate section entitled "Common misspellings" or "See also". For example, in a page called Kington (disambiguation), a link to Kingston (disambiguation) would appropriately be included in the "See also" section.

Piping and redirects
Piping and redirects are two different mechanisms, both having the effect that the displayed text of a link is not the same as the title of the article at which readers will arrive when they click that link.
 * Piping means concealing the actual title of a linked article by replacing it with other text, often to suppress parenthetical expressions in an article. For example, instead of linking Moment (physics) in a normal article, it will be presented as  Moment  to display as a single word: Moment.
 * A redirect is a special page used to "jump" readers from one page title to an article with a different title. For example, a redirect is used at the title 9/11 to send users who navigate there to the article at September 11 attacks.

Subject to certain exceptions as listed below, piping or redirects should not be used in disambiguation pages. This is to make it clear to the reader which article is being suggested, so that the reader remains in control of the choice of article. For example, in the Moment disambiguation page, with the entry for Moment (physics), "physics" should be visible to the reader. In many cases, what would be hidden by a pipe is exactly what the user would need to be able to find the intended article. In addition, raw section and anchor points should not be displayed. See section and anchor point linking for the handling of these cases.

Even when the disambiguated term is an acronym, initialism or alphabetism, links should not use redirects to conceal the expanded version of that initialism. For example, on the disambiguation page BNL, linking to the full article title Banca Nazionale del Lavoro is preferable to linking to a redirect at BNL (bank).

Exceptions
Though piping and redirects should generally not be used in disambiguation pages, there are certain cases in which they may be useful to the reader:

Where redirecting may be appropriate

 * A redirect should be used to link to a specific section of an article only if the title of that section is more or less synonymous with the disambiguated topic. This indicates a higher possibility that the topic may eventually have its own article. For example:
 * {| style="border: 1px solid black" width=100%


 * Delta may refer to:
 * (correct) Delta Quadrant, in the Star Trek universe ( Delta Quadrant, in the Star Trek universe )
 * (incorrect) Delta Quadrant, in the Star Trek universe ( Delta Quadrant, in the Star Trek universe )
 * }
 * }


 * The above technique should be used only when the link is the subject of the line, not when it is in the description. For description sections, consider piping instead.
 * Linking to a redirect can also be helpful when the redirect contains the disambiguated term and could serve as an alternative name for the target article, meaning an alternate term which is already in the article's lead section. For example:
 * {| style="border: 1px solid black" width=100%


 * James Cary may refer to:
 * (correct) James Carrey or Jim Carrey (born 1962), Canadian actor ( James Carrey or Jim Carrey, (born 1962), Canadian actor )
 * (incorrect) James Carrey or Jim Carrey (born 1962), Canadian actor ( James Carrey or Jim Carrey, (born 1962), Canadian actor )
 * }
 * }


 * The above example of a redirect is only appropriate because James Carrey is indicated as a name in the lead section of the Jim Carrey article. If it were not, then the second example could have been used instead.
 * For situations where the primary topic is a redirect, see Linking to a primary topic above.

Where piping may be appropriate

 * Use piping to add italics or quotation marks to part of an article name; for instance, Harvey (film), USS Adder (SS-3), "School" (song), Saturnalia (dinosaur), "Hush" (Buffy episode), Neo (The Matrix).
 * Similarly, use piping if the article title differs from what it should be due to technical limitations per wrongtitle; for instance, The Singles 86>98 or Softimage&#124;XSI.
 * When the link is in the description, rather than at the start of the entry, piping can be used more freely. However, the text of the link should still be close to the title of the target article, to avoid confusing the reader. For example:
 * {| style="border: 1px solid black" width=100%

Switch may refer to:
 * "Switch", a song by Siouxsie & the Banshees from The Scream ( "Switch", a song by Siouxsie & the Banshees from The Scream )
 * }
 * When a disambiguation page is linking to a specific section of an article, rather than an entire article, piping may be used for linking to that section via anchor points or section linking. This technique is used commonly for piping to the track listing section of an album; a further example, from E (disambiguation), is that the piped ESRB ( ESRB ) is preferred to simply linking to the top of the target page ESRB.


 * When piping is used on a disambiguation page to link to an article section, the link should be in the description, and should avoid surprising the reader. The text of the link should not be the title of a different article. For example:
 * {| style="border: 1px solid black" width=100%

Ten may refer to:
 * (correct) Ten or Tien Shinhan, a character in Dragon Ball media ( Ten or Tien Shinhan, a character in Dragon Ball media )
 * (incorrect) Ten or Tien Shinhan, a character in Dragon Ball media ( Ten or Tien Shinhan, a character in Dragon Ball media )
 * }

Section and anchor point linking
Section and anchor points in links should not be visible to the reader (e.g., Galactic quadrant ). If an anchor-point link is needed: When creating a redirect to a section, add the template R to section on the redirect page.
 * For linking the subject, link to a redirect to the anchor point (or leave the subject unlinked and move the link to the description).
 * For links in the description, link to a redirect or use an anchor-point link with piping to display text similar to the article title.

Foreign languages
For foreign-language terms, be sure an article exists or could be written for the word or phrase in question. Usually this means that the term has been at least partially adopted into English or is used by specialists.


 * {| style="border: 1px solid black" width=100%


 * Tambo may refer to:
 * Tambo (weapon), a very short staff used in martial arts
 * }
 * }

Avoid adding lines for words or phrases that are simply spelled the same as an English term. For example, do not include:
 * Tambo, a Japanese word (田んぼ) for rice paddy

Instead, consider linking to Wiktionary.

People
For people, include their birth and death years (when known), and only enough descriptive information that the reader can distinguish between different people with the same name. Keep in mind the conventions for birth and death dates—see Manual of Style (dates and numbers). Do not include a, an or the before the description of the person's occupation or role.


 * {| style="border: 1px solid black" width=100%


 * John Adams (1735–1826) was the second President of the United States.
 * John Adams (1735–1826) was the second President of the United States.

John Adams may also refer to:
 * John Adams (composer) (born 1947), American composer who came to prominence with his opera Nixon in China
 * John Adams (physicist) (1920–1984), Director general of CERN and particle accelerator designer
 * John Adams (martyr) (died 1586), Catholic priest and martyr under Elizabeth I of England
 * }

Places
For places, it may only be necessary to write the name of the article.


 * {| style="border: 1px solid black" width=100%


 * Jacksonville may refer to:
 * Jacksonville, Florida
 * Jacksonville, Alabama
 * Jacksonville, Arkansas
 * }
 * }

It may be appropriate to add the country after the link. Leave the country unlinked.


 * {| style="border: 1px solid black" width=100%


 * Kimberley may refer to:
 * Kimberley, Nottinghamshire, England
 * Kimberley, British Columbia, Canada
 * }
 * }

Red links
A link to a non-existent article (a "red link") should only be included on a disambiguation page when an article (not just disambiguation pages) also includes that red link. Do not create red links to articles that are unlikely ever to be written, or are likely to be removed as insufficiently notable topics. To find out if any article uses the red link, click on it, and then click "What links here" on the toolbox on the left side of the page. If the only pages that use the red link are disambiguation pages, unlink the entry word but still keep a blue link in the description.

Red links should not be the only link in a given entry; link also to an existing article, so that a reader (as opposed to a contributing editor) will have somewhere to navigate to for additional information. The linked article should contain some meaningful information about the term.

In the following (made-up) example, the architectural motif is judged to be appropriate for a future article, but the noodle is not; therefore, only the entry for the architectural motif includes a red link (and this assumes that the fictitious "flibbygibby" entries are described in their respective linked articles):


 * {| style="border: 1px solid black" width=100%


 * Flibbygibby may refer to:
 * Flibbygibby (architecture), a flamingo motif used on cornices
 * Flibbygibby, a type of noodle
 * }
 * }

Synonyms
If the link is to a synonym, simply use it as it is named:


 * {| style="border: 1px solid black" width=100%


 * Serving spoon may also refer to:
 * Tablespoon
 * }
 * }

Items appearing within other articles
If a topic does not have an article of its own, but is mentioned within another article, then a link to that article should be included. In this case, the link does not start the line, but it should still be the only blue wikilink. For example:


 * {| style="border: 1px solid black" width=100%


 * Tail may also refer to:
 * The empennage of an aircraft
 * The luminous matter anti-sunwards from a comet
 * }
 * }

It is often useful to link to the relevant section of the target page (using the #anchor notation) and conceal that by making it a piped link. For examples, see "Where piping may be appropriate" under Exceptions, above.

Order of entries
Entries should generally be ordered as follows:
 * 1) The primary topic should be placed at the top. In unusual cases, several of the most common meanings may be placed at the top, with other meanings below.
 * 2) Long dab pages should be organized into subject sections, as described below.
 * 3) Within each section, entries should then be grouped by how similar the name of the target article is to the name of the disambiguation page. A recommended order is:
 * 4) Articles with a clarifier in parentheses: e.g., South Pacific (film)
 * 5) Articles with a clarifier following a comma: e.g., Kneeland, California
 * 6) Articles with the item as part of the name: e.g., Electronic keyboard as part of a Keyboard dab page (Only include articles whose subject might reasonably be called by the ambiguous title.)
 * 7) Synonyms: e.g., Bite as part of a Nibble dab page
 * 8) Broader-subject articles that treat the topic in a section: e.g., Medieval art as part of a Fresco dab page Often, the latter two groups (synonyms and broader articles) should be separated from the rest of the entries, into a See also section.
 * 9) Finally, within the above groups, entries should be ordered to best assist the reader in finding their intended article.  This order might be alphabetical, chronological, by most likely target, or by some other method.

Organizing long lists by subject
Longer pages should be broken up by subject area. Subject areas should be chosen carefully to simplify navigation. Use subject areas that are well-defined, and that group the entries into similarly-sized sections. Very small sections may impede navigation, and should usually be avoided. Disambiguation pages will often have an "Other uses" section at the end for entries that don't fit neatly into another section; this is perfectly acceptable. Keep in mind that a particular division scheme may not work equally well on all disambiguation pages. An example:


 * {| style="border: 1px solid black" width=100%

Thingamajig may refer to:

In science:
 * Thingamajig (chemistry), an isotope of chlorine
 * Thingamajig (physics), a kind of pulsar
 * Thingamajig (biology), an invasive plant used as ground cover

In world music:
 * Thingamajig (Qatar), a seven-stringed musical instrument
 * Thingamajig (Peru), a wind instrument similar to an aulos
 * Thingamajig (UK), a wind instrument, similar to, but longer than the Peruvian one
 * }

On longer lists, section headings should be used instead of, or in addition to, bold headings. Using more than one level may be necessary, as on Aurora (disambiguation). Always use ==Level two== as the highest-level header. Section headings should not include links. See Writing better articles for more.

On longer lists, TOCright may be used to move the table of contents to the right hand side of the page. This reduces the amount of white space and may improve the readability of the page. (For more information, see Help:Section.) If used, TOCright should be placed after the lead section of the wiki markup and immediately before the first section heading. Users of screen readers do not expect any text between the TOC and the first heading, and having no text above the TOC is confusing. (For more information, see Accessibility.)

"See also" section
There may be a "See also" section, which can include such items as:
 * Terms which can be confused with Title, for example New Market and Newmarket
 * Likely misspellings of Title, for example Belmont, Belmonte and Bellmont
 * Different forms of Title, for example Splitting, Split, and Splitter
 * Links to indexes of article titles beginning with Title (using ) and/or article titles containing Title (using )

The "See also" should always be separated from the other entries with a section header. Links to other disambiguation pages should use the "(disambiguation)" link per WP:INTDABLINK. When appropriate, place easily confused terms in a hatnote.

Images and templates
Including images and templates is discouraged unless they aid in selecting between articles on the particular search term in question. Examples of this are the images at Congo (disambiguation) and Mississippi Delta (disambiguation).

The disambig notice and categorization
After all of the disambiguation content (including the See also section, if present), but before any categories (see below) or interlanguage links, a template should be placed identifying the page as a disambiguation page. This generates a message to the reader explaining the purpose of the page, and also places the page in the appropriate category or categories.

The usual template to use is disambig, which produces a general disambiguation notice, and places the page in Category:Disambiguation pages. Parameters can be added to place the page additionally into other more specific disambiguation categories. For example, if a page includes multiple places and multiple people with the same surname (and possibly other items), use. A full list of available parameters and their corresponding categories can be found in the disambig template documentation.

If a disambiguation page consists exclusively of items in one of the more specific classes, then a specific template should be used instead of disambig. For example, use roaddis for highways, geodis for locations, hndis for human names and so on. A full list can be found in the disambig template documentation.

If a disambiguation page needs cleaning up to bring it into conformance with this style manual, use disambig-cleanup. This replaces both disambig and cleanup-date.

Do not use or , as the contents of this notice may change in the future (see Transclusion costs and benefits). Also, the Wikipedia software relies on links to the templates to determine which pages are disambiguation pages (see MediaWiki:Disambiguationspage), and subst'ing breaks this feature.

Most disambiguation pages do not need to be placed into any categories other than those generated by the template. If such cases do arise (for example, specific categories of personal names that do not have corresponding template parameters), then the additional categories should be placed after the template.

If new topical categories of disambiguation pages seem to be needed, please bring this up for discussion at Wikipedia talk:Disambiguation.

Set index articles
Set index articles are list articles about a set of items that have similar or identical names. Set index articles are disambiguation-like pages that do not obey the style outlined on this page. Note that the set index article exception was designed to be narrow: for pages that contain links to articles about different topics, please follow this style guide for disambiguation pages. One example of a set index article is a list of ships with the same name. For more information about such ship lists, see WikiProject Ships/Guidelines.

Disambiguation pages with only two entries
Some disambiguation pages with "(disambiguation)" in the title list only two meanings, one of them being the primary topic. In such cases, the disambiguation page is not strictly necessary, but is harmless. The recommended practice in these situations is to place a hatnote on the primary topic article to link directly to the secondary topic. The for and redirect templates are useful.

If neither of the two meanings is primary, then a normal disambiguation page is used at the base name.

Break rules
Application of these guidelines will generally produce useful disambiguation pages which are consistent with each other and therefore easily usable by most readers. Usefulness to the reader is their principal goal. However, for every style recommendation above, there may be pages in which a good reason exists to use another way; so ignore these guidelines if doing so will be more helpful to readers than following them.

Other pages discussing infoboxes

 * Disambiguation dos and don'ts
 * Disambiguation pages with links
 * Category:Disambiguation pages in need of cleanup

Links (details)
See WP:Linking for details.

Wikilinks
See WP:Wikilinks, WP:Linking, WP:Guide to layout and Help:Contents/Links for details,

Infoboxes (details)
An infobox template is an infobox that uses the template software feature. They are a broad class of templates commonly used in articles to present certain summary or overview information about the subject. In theory, the fields in an infobox should be consistent across every article using it; in practice, however, this is rarely the case, for a number of reasons. When this occurs, the infobox templates should be designed to dynamically adapt themselves to the absence or presence of particular fields.

Like static infoboxes, they are designed to present summary information about an article's subject, such that similar subjects have a uniform look and in a common format. However, the template technique allows updates of style and of common text from a central place, the template page.

These boxes are designed to be placed into main articles related to the topic area, and are usually associated with on-going WikiProjects. They have parameters; to work properly, the parameter values have to be specified when the template is inserted in the page. This allows each infobox to show information relevant to the article subject, while requiring only a minimal amount of coding within each article.

Design and usage
The recommended process for creating an infobox template is to simply begin, and gather as many requirements as possible. Test the base format for a new template as a static table first, then once consensus is reached, migrate it into template format. The template should be reviewed before being used extensively in articles in case the template or defined parameters need modification to minimize re-works. If new fields and parameters are added, articles must be updated to reflect the new requirements. If parameters are renamed or removed, many articles will likely be unaffected, since extraneous parameters are ignored.

For consistency the following guidelines apply:
 * 1) Standard suggested width of 300 pixels or 25 ems (  or   in CSS).
 * 2) Insert at the top of articles and right-align
 * 3) Using   is a good start.
 * 4) The top text line should be bold and contain the full (official) name of the article's subject; for people common name is optional. This does not need to match the article's Wikipedia title. It should not contain a link. Avoid   as pages may be moved for disambiguation.
 * 5) Name the template  Template:Infobox some subject  (some subject should be in the singular and capitalized as per normal usage – see WP:NAME).
 * 6) Start words in parameter names with a small letter unless they are proper nouns.

When creating a new infobox template the content of Template:Infobox is a convenient starting point.

Parameters in infoboxes should be named, not numbered, to provide for future use. A parameter value can contain images (i.e. full image tags), or parameters for parts of an image tag such as the image name, size and caption. In the latter case, if an image is not applicable or available consider using a dummy image such as Image:No image.png.

If a parameter is not applicable, or no information is available, it should still be assigned a value. This can be the empty string, or if it is the only thing in a table cell use " ". The field will appear blank; the code is needed by some browsers for drawing the lines of the table itself properly.

There are alternative ways to make a template selectively hide information or provide default values if not defined. For an example and explanation of how these methods apply to infoboxes, see Infobox.

Geographical infoboxes
Infoboxes for geographical items should generally be headed with the article title, although the formal version of a name (e.g. Republic of Montenegro at Montenegro) can be substituted. Alternate or native names can appear beneath this. Extensive historic names are often better in a second infobox, as at Augsburg.

Causes of inconsistency
A number of factors can cause inconsistency in available summary information for a particular type of article:


 * Historical incompleteness : Certain desired information may simply have been lost over time. For example, an infobox describing a modern bank may provide certain financial information that would be unavailable for a medieval one.


 * Hierarchical inconsistency : Infoboxes that indicate hierarchical relationships may have subtly different requirements depending on where in the hierarchy the subject of the article is located. For example, an infobox for corporations will be different between an article describing a parent company and indicating its subsidiaries and an article describing a subsidiary and indicating its parent.


 * Feature inconsistency : Items within a single set may have optional features that would commonly be listed in an infobox. For example, an infobox for an article about a university may include a motto; but not all universities have them.


 * Lack of information : Some items in infoboxes may not be readily available or not available at all, such as the producers of an album or film. In these cases it is better to provide available information  while concealing fields for which information may not be available.

Why dynamic templates?
While there are several alternatives to dynamic infoboxes, such as using multiple (forked) templates or leaving fields blank, they should be avoided, for a number of reasons:


 * Readers greatly outnumber editors : The most important group to consider are the casual readers of Wikipedia, who will never do any significant editing. Infobox templates that contain many blank fields, question marks, or "Unknown"s present an unprofessional appearance, diminishing Wikipedia's reputation as a high-quality encyclopedia.


 * Article editors greatly outnumber template editors : The average editor will merely use templates without making changes to them. To make things easier for them, we should aim to minimize the number of different templates they must be familiar with; creating multiple forks of templates is therefore undesirable.

General advice
The availability of optional fields does not mean that all fields should be made optional, nor that large numbers of rarely used fields should be added without regard for the layout and ease-of-use of the infobox template. In some cases, the markup for the field still needs to be downloaded even if it is not displayed. Creating overly long templates with a number of irrelevant fields is not recommended.

As you design an infobox template, consider the following questions:


 * Is the field of value? : How important is the field to the articles that will use the infobox? Is it summary information, or more extended detail that may be better placed within the body of an article?


 * Will the field be relevant to many of the articles that will use the infobox? : If the field is relevant to very few articles, it should probably not be included at all. Conversely, very common fields may be included—and made optional—even if they are not applicable to a few of the articles in question.


 * How likely is the field to be empty? : Any field that might reasonably be empty should probably be optional. However, a field that is usually empty may not be particularly useful or relevant.


 * Is it for people, places or organisations? : If so, include an hCard microformat - see the microformat project


 * Is it for a dated event? : (Such as a record release, or sport fixture) If so, include an hCalendar microformat - see the microformat project

Conditional templates
Special "templates" that selectively show or hide particular content (such as table rows) within an infobox based on the value of one or more template parameters.

Name-resolved meta-templates
Several sub-templates (or even independent templates) with a common name prefix. They are included in an infobox based on the value of a particular parameter, which acts as the name suffix. For example, we create  and   and use. Using  in an article causes   to be used.

Multi-part infoboxes
Rather than having each field correspond to a parameter on one template, the infobox consists of an individual sub-template for each field; see, for example, Template:Taxobox.

Interaction between multiple templates
Templates can be designed in a modular way, such that various combinations are possible. A combination may even appear on the page as a single infobox.

For example, if the WikiProject Saints group wanted to design a template based on their static Infobox, they could use Template:Infobox Biography, and design a project-specific template with only additional information, and the pages would render both "stacked" together.

List of templates

 * See Category:Infobox templates for the main listing. See also any relevant WikiProjects, and a list of templates starting with "Infobox ...".

Pages related to infoboxes

 * Help:Infobox
 * Template messages/Cleanup
 * Disinfoboxes

Other types of templates:
 * Template messages are used primarily to insert simple "boilerplate" messages for Wikipedia maintenance or editing purposes.
 * Navigational templates are article footers designed to provide links to several related articles.
 * MediaWiki interface messages are reserved for internal system use, and can only be modified by administrators.