Yahoo Web Search

  1. About 87 search results
  1. This is a documentation subpage for Template:User Good Articles. It contains usage information, categories and other content that is not part of the original template page. Usage [ edit ]

    • Order of Article Elements
    • Body Sections
    • Standard Appendices and Footers
    • Specialized Layout
    • Formatting
    • See Also

    A simple articleshould have, at least, (a) a lead section and (b) references. The following list includes additional standardized sections in an article. A complete article need not have all, or even most, of these elements. 1. Before the article content 1.1. Short description 1.2. {{DISPLAYTITLE}}, {{Lowercase title}}, {{Italic title}} (may also b...

    Articles longer than a stub are generally divided into sections, and sections over a certain length are generally divided into paragraphs; these divisions enhance the readability of the article. The names and orders of section headings are often determined by the relevant WikiProject, although articles should still follow good organizational and wr...


    When appendix sections are used, they should appear at the bottom of an article, with ==level 2 headings==,[f] followed by the various footers. When it is useful to sub-divide these sections (for example, to separate a list of magazine articles from a list of books), this should be done using level 3 headings (===Books===) instead of definition list headings (;Books), as explained in the accessibility guidelines.

    Works or publications

    Contents:A bulleted list, usually ordered chronologically, of the works created by the subject of the article. Heading names: Many different headings 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. "Publications", "Discography", or "Filmography" are occasionally used where appropriate; however, "Bibli...

    "See also" section

    A "See also" section is a useful way to organize internal links to related or comparable articles and build the web. The section is not required; many high-quality and comprehensive articles do not have one. Whether a link belongs in the "See also" section is ultimately a matter of editorial judgment and common sense. The section should be a bulleted list, limited to a reasonable number, sorted either logically (for example, by subject matter), chronologically, or alphabetically. Consider usi...

    Stand-alone lists and talk pageshave their own layout designs. Certain topics have Manual of Style pages that include layout advice, including: 1. Chemistry 2. Film 3. Medicine, for articles on treatments, procedures, medical products, fields of medicine, and other concepts 4. Television 5. Video games Some WikiProjects have advice pages that inclu...


    Each image should ideally be located in the section to which it is most relevant, and most should carry an explanatory caption. An image that would otherwise overwhelm the text space available within a 1024×768 window should generally be formatted as described in relevant formatting guidelines (e.g. WP:IMAGESIZE, MOS:IMGSIZE, Help:Pictures#Panoramas). Try to harmonize the sizes of images on a given page in order to maintain visual coherence. If "stacked" images in one section spill over into...

    Horizontal rule

    Horizontal rules are sometimes used in some special circumstances, such as inside {{sidebar}} template derivatives, but not in regular article prose.

    Collapsible content

    As explained at MOS:COLLAPSE, limit the use of {{Collapse top}}/{{Collapse bottom}} and similar templates in articles. That said, they can be useful in talk pages.

  2. People also ask

    Can I create articles about anything on Wikipedia?

    How do I list navigational templates in Wikipedia?

    What are the guidelines for editing a Wikipedia page?

    What is a featured article on Wikipedia?

  3. › wiki › Wikipedia:Requested_templatesWikipedia:Requested templates

    Template:Welcome-MOS. This template should be used for users who violated the Manual of Style with their first contributions to Wikipedia. The templateshould say something like "Hello, User:Example, and welcome to Wikipedia! Unfortunately, one or more of your edits have not conformed to Wikipedia's Manual of Style, and may have been removed."

  4. › wiki › Wikipedia:Template_indexWikipedia:Template index

    • Using This Page
    • Search
    • Article-Related Namespace
    • Related Pages For Specific Types of Templates
    • WikiProjects and Standardisation
    • See Also

    The bold linksat the top of each cell lead to detailed pages which describe the templates in that section in detail and explain how and when to use them. If you cannot find the template you are looking for, please click on the section headers that seem most relevant, since there may be templates for a particular usage covered on the detailed pages,...

    As an alternative to using this index, you can search the Template namespace using the box below: You can also search Wikipedia:Template messages in the box below:

    Please list navigational templates (as, for example, between pages relating to a specific topic) at Wikipedia:Navigation template or at the appropriate WikiProjectpage.

    Wikipedia:Template index/Main page and alternatives – templates used on the Main Page.
    Wikipedia:Hatnote and Template:Hatnote templates – documentation for hatnotes.
    Wikipedia:Template index/Links § External links and Category:External link templates – templates for links to external sites.
    • What to Include
    • Where to Place It
    • How to Create A Documentation Subpage
    • Blank
    • Examples
    • Categories and Interwiki Links
    • /Sandbox and /Testcases
    • Several Templates, One Documentation Page
    • Directly on A Template Page
    • When No Documentation Is Needed

    Template documentation should cover: 1. The basic purpose of the template: what it does and if it is not immediately obvious, why it needs to be done. If there are other templates with similar names or purposes, it's a good idea to mention those, in order to reduce the chance of the wrong one being used. Include important limitations, such as the l...

    When viewing the rendered template page itself (as opposed to its wikicode), what is usually visible right under the title is the rendered template itself, followed by a separate section to display the template's rendered documentation, followed by the categories to which the template belongs. Categories and documentation of any sort on a template ...

    Put documentation in the template

    You must put {{documentation}} when creating (publishing) a template. Then a documentation page is created with [view] [edit] [history] [purge] links. You can create and edit the template documentation clicking in this pane [edit]link. Template documentation subpages using {{documentation}} are named and formatted using the following general pattern, for consistency. Suppose your template is named Template:X. Edit the template and append the following at the end of the template code, or use {...

    Automatic creation

    Use [create] link at the bottom of the empty documentation box to automatically create a preloadeddocumentation subpage. Insert the documentation after the top line and categories under the appropriate comment line – leaving the comment in place, so that the layout is preserved when the page is edited in future. Related templates, policy page, projects, etc. can be linked to by adding a "See also" section. Save the subpage.

    Manual creation

    To create the documentation subpage manually, create a subpage with the name Template:X/doc. See the details at {{Documentation subpage}} or start the page by copy-pasting the following standard wikitext: The top line will display a message explaining the current page and a link to the template page. Save the subpage and follow instructions in section "Use Template:Documentation".

    To generate a blank template, which may then be copied from the documentation and pasted into another page, use: 1. {{subst:#tag:pre|{{subst:Parameters|code|base={{subst:BASEPAGENAME}}}}|style=overflow: auto;}}

    To generate an instance of the template, populated with its own property names, use: 1. {{subst:Parameters|demo|base={{subst:BASEPAGENAME}}|_base=}}

    To place the template itself into a category, add the [[Category:Category name]] code inside an ... section on the docsubpage.
    To create an interwiki link for the template itself, go to Wikidataand follow the instructions for adding links to pages.
    To place the doc subpage into a category, add the [[Category:Category name]] code inside a ... section on the docsubpage.
    To make the template place an article into a category (when the article includes the template), add the [[Category:Category name]] code inside an ... section on the templa...

    Before doing changes to a template it can be good to first copy the template code to a sandbox and run some testcases, since the template might be visible on thousands or even millions of pages. If you create subpages named exactly "/sandbox" and "/testcases" to a template then the green {{documentation}} box on the template auto-detects this and w...

    When several templates work together or are very similar then it is often clearer and easier to maintain one single documentation page that documents them together. The simplest way to do this is to make a full documentation page at one of the templates, and then make "soft redirects" from the other templates. See, for instance: {{wrap}}.

    When a documentation subpage has not been created, and the {{documentation}} template is being used with a |content= parameter on the actual template page, then to place the template itself into a category, add [[Category:Category name]]inside the documentation template, after the content. For example, for placement on the actual template page:

    When a template as displayed will link to a page that can serve as the documentation, then separate documentation is superfluous and does not need to be created. For instance, a stub template, using the {{asbox}} template as a base, will already display pre-loaded common documentation for all stub templates using that template, and will not need ad...

  5. › wiki › Wikipedia:Article_developmentWikipedia:Article development

    A PDF brochure by the Wikimedia Foundation about how articles evolve, elements of good quality articles, and signs of poor quality articles. Some of Wikipedia's articles are comprehensive right from the outset, but most start off as stubs and ideally grow into well-written, comprehensive articles with time.

  1. People also search for