TechInfoDepot:Manual of Style/Layout



This is a guide to laying out a typical basic article. Complicated articles may be best modeled on the layout of an existing article of appropriate structure. For advice on how to use wiki markup, see Help:Editing; and for guidance on writing style, see Manual of Style.

The lead section
As explained in detail at Elements of the lead section, the lead section may contain optional elements presented in the following order:
 * 1) disambiguation links (dablinks)
 * 2) maintenance tags
 * 3) infoboxes
 * 4) images
 * 5) navigational boxes (navigational templates)
 * 6) introductory text
 * 7) table of contents moving to the heading of the first section.

Headings and sections
Sections and subsections are introduced by headings. These headings clarify articles by breaking up text, organizing content, and populating the table of contents. Very short or very long sections and subsections in an article look cluttered and inhibit the flow of the prose.

Headings follow a six-level hierarchy, starting at 1 and ending at 6. The level of the heading is defined by the number of equal signs on either side of the title. Heading 1 is automatically generated as the title of the article, and is never appropriate within the body of articles. Sections start at the second level, with subsections at the third level , and additional levels of subsections at the fourth level , fifth level, and sixth level. Sections should be consecutive, such that they do not skip levels from sections to sub-subsections; the exact methodology is part of the Accessibility guideline. Between sections (and paragraphs), there should be a single blank line; multiple blank lines in the edit window create too much white space in the article.

Section templates and summary style
When a section is a summary of another article that provides a full exposition of the section, a link to that article should appear immediately under the section heading. You can use the Main template to generate a Main article; link.

If one or more articles provide further information or additional details (rather than a full exposition—see above), references to such articles may be placed immediately after the section heading for that section, provided this does not duplicate a wikilink in the text. These additional references should be grouped along with the template (if there is one), for easy selection by the reader, rather than being scattered throughout the text of a section. You can use one of the following templates to generate these links:
 * —this generates For more details on this topic, see:
 * —this generates Further information:
 * —this generates See also:

For example, to generate a "See also" link to the article on TechInfoDepot:How to edit a page, type, which will generate:

Paragraphs
Sections usually consist of paragraphs of running prose. Bullet points should be minimized in the body and lead of the article, if they are used at all; however, a bulleted list may be useful to break up what would otherwise be a large, grey mass of text, particularly if the topic requires significant effort on the part of readers. Bulleted lists are typical in the reference and reading sections at the bottom. Between paragraphs—as between sections—there should be only a single blank line; bullet points are usually not separated by a blank line.

The number of single-sentence paragraphs should be minimized, since they can inhibit the flow of the text; by the same token, paragraphs that exceed a certain length become hard to read. Short paragraphs and single sentences generally do not warrant their own subheading; in such circumstances, it may be preferable to use bullet points. See also TechInfoDepot:Writing better articles.

Standard appendices and footers
When certain optional standard appendix sections are used, they should appear at the bottom of an article, with, Syntax: 

Order of sections
Where present, appendix and footer sections are presented in this order.
 * 1) Works or publications
 * 2) See also
 * 3) Notes and references
 * 4) Further reading
 * 5) External links
 * 6) Navigation templates (footer navboxes)
 * 7) Geographical coordinates (if not in Infobox) or coord missing
 * 8) Authority control template
 * 9) Persondata template
 * 10) Defaultsort
 * 11) Categories
 * 12) Stub template

Works or publications
Contents: A bulleted list, usually ordered chronologically, of the works created by the subject of the article.

Title: Many different titles are used, depending on the subject matter. "Works" is preferred when the list includes items that are not written publications (e.g., music, films, paintings, choreography, or architectural designs), or if multiple types of works are included. "Bibliography", "Discography", or "Filmography" are occasionally used where appropriate; however, "Bibliography" is discouraged because it is not clear whether it is limited to the works of the subject of the article. "Works"/"Publications" should be plural, even if it lists only a single item.

See also section
Contents: A bulleted list, preferably alphabetized, of internal links to related TechInfoDepot articles. Portal and TechInfoDepot books links are usually placed in this section. Consider using Columns-list or Div col if the list is lengthy.

Editors should provide a brief annotation when a link's relevance is not immediately apparent, when the meaning of the term may not be generally known, or when the term is ambiguous. For example:


 * Related person—made a similar achievement on April 4, 2005
 * Ischemia—restriction in blood supply

Whether a link belongs in the "See also" section is ultimately a matter of editorial judgment and common sense. The links in the "See also" section should be relevant, should reflect the links that would be present in a comprehensive article on the topic, and should be limited to a reasonable number. As a general rule the "See also" section should not repeat links which appear in the article's body or its navigation boxes. Thus, many high-quality, comprehensive articles do not have a "See also" section.

The links in the "See also" section do not have to be directly related to the topic of the article, because one purpose of "See also" links is to enable readers to explore tangentially related topics. The "See also" section should not link to pages that do not exist (red links) nor to disambiguation pages (unless used for further disambiguation in a disambiguation page).

Title: The most common title for this section is "See also".

Notes and references


Contents: This section, or series of sections, may contain any or all of the following:


 * 1) explanatory footnotes that give information which is too detailed or awkward to be in the body of the article,
 * 2) citation footnotes (either short citations or full citations) that connect specific material in the article with specific sources,
 * 3) full citations to sources, if short citations are used in the footnotes, or
 * 4) general references (full bibliographic citations to sources that were consulted in writing the article but that are not explicitly connected to any specific material in the article).

If there are both citation footnotes and explanatory footnotes, then they may be combined in a single section, or separated using the grouped footnotes function. General references and other full citations may similarly be either combined or separated. There may therefore be one, two, three, or four sections in all.

It is most common for only citation footnotes to be used, and therefore it is most common for only one section to be needed. Usually, if the sections are separated, then explanatory footnotes are listed first, short citations or other footnoted citations are next, and any full citations or general references are listed last.

Title: Editors may use any section title that they choose. The most frequent choice is "References"; other articles use "Notes", "Footnotes", or "Works cited" (in diminishing order of popularity) for this material.

Several alternate titles ("Sources", "Citations", "Bibliography") may also be used, although each is problematic in some contexts: "Sources" may be confused with source code in computer-related articles, product purchase locations, river origins, Journalism sourcing, etc.; "Citations" may be confused with official awards or a summons to court; "Bibliography" may be confused with the complete list of printed works by the subject of a biography.

If multiple sections are wanted, then some possibilities include:
 * for a list of explanatory footnotes and/or shortened citation footnotes: "Notes", "Endnotes", or "Footnotes"
 * for a list of full citations and/or general references: "References" or "Works cited"

With the exception of "Bibliography", the heading should be plural even if it lists only a single item.

Links to sister projects
Links to Wikimedia sister projects and Spoken TechInfoDepot should generally appear in "External links", not under See also. Two exceptions are Wiktionary and Wikisource links that may even be linked inline (e.g., to the text of a document being discussed or to a word that might not be familiar to all readers).

More precisely, box-type templates such as shown at right have to be put at the beginning of the last section of the article (which is not necessarily the "External links" section) so that boxes will appear next to, rather than below, the list items. Do not make a section whose sole content is box-type templates.

If box-type templates are not good, either since they result in a long sequence of right-aligned boxes hanging off the bottom of the article, or there are not any external links except sister project ones, then consider using "inline" templates, such as Commons-inline in the "External links" section, so that links to sister projects appear as list items, like this:

Navigation templates
Contents: Navigation templates (footer navboxes), including succession boxes and geography boxes such as. Most navboxes do not appear in printed versions of TechInfoDepot articles.

Images
Images should ideally be spread evenly within the article, and relevant to the sections they are located in. All images should also have an explicative caption. An image that would otherwise overwhelm the available text space on a 800×600 window should be shrunk or formatted as a panorama. It is a good idea to try to maintain visual coherence by aligning the sizes of images and templates on a given page.

When placing images, be careful not to stack too many of them within the lead, or within a single section to avoid bunching up several section edit links in some browsers. Generally, if there are so many images in a section that they strip down into the next section at 1024×768 screen resolution, that probably means either that the section is too short, or that there are too many images. If an article has many images—so many, in fact, that they lengthen the page beyond the length of the text itself—you can use a gallery. Another solution might be to create a page or category combining all of them at Wikimedia Commons and use a relevant template (Commons, Commons category, Commons-inline or Commons category-inline) to link to it instead, so that further images are readily found and available when the article is expanded. Please see WP:IG for further information on the use of galleries.

As a general rule, images should not be set to a larger fixed size than the 220px default. If an exception to the general rule is warranted, forcing an image size to be either larger or smaller than the 220px default is done by placing a parameter in the image coding in the form. Lead images should usually be no wider than "300px" ("upright=1.35"). Larger images should generally be a maximum of 500 pixels tall and 400 pixels wide, so that they can comfortably be displayed on the smallest displays in common use.

Avoid referring to images as being on the left or right. Image placement is different for viewers of the mobile version of TechInfoDepot, and is meaningless to people having pages read to them by assistive software. Instead, use captions to identify images.

Links
As part of Wikifying articles, you should link words in this article to other relevant articles. To create an intrawiki hyperlink, place two square brackets around important words or phrases, like this:. Normally, the first occurrence of a word is the one chosen for a link. Do not link to the same article more than once in a section. Avoid creating adjacent links to separate articles, because the reader cannot tell whether the link is to one or two articles without pointing to the link.

If the phrase or word in the article you are editing does not match the name of the article you want to link, use a piped link. Type the exact name of the target article followed by a pipe " " (vertical bar, shift backward slash on some keyboards) followed by the phrase you wish to see in the context of the article you are editing. Place two square brackets around this code. This creates a hyperlink that will allow the reader to click through to other TechInfoDepot articles:



When saved, this produces:

 Lennie and George came to a ranch near Soledad southeast of Salinas, California, to "work up a stake".

Horizontal rule
Horizontal rules—a series of hyphens resulting in a straight line—are deprecated; that is, they are no longer used in articles. Rules were once employed to separate multiple meanings of a single article's name, but this task is now accomplished through disambiguation pages.

Rules can be used to provide separation inside certain templates (for example, sidebar derivatives), within discussions, or when needed in some other formats.

Specialized layout

 * Category:Style guidelines of WikiProjects
 * TechInfoDepot:Stand-alone lists
 * TechInfoDepot:Talk page layout

Other project pages

 * Help:Editing
 * Help:Preferences
 * Help:Section
 * TechInfoDepot:Article titles
 * TechInfoDepot:Disinfoboxes (essay)
 * TechInfoDepot:Related information (essay)—optional heading for end of article navboxes
 * TechInfoDepot:Talk page guidelines—shows how to use headings on talk pages