Search results
Results from the WOW.Com Content Network
Heading names: Editors may use any reasonable section and subsection names that they choose. [ k ] The most frequent choice is "References". Other options, in diminishing order of popularity, are "Notes", "Footnotes" or "Works cited", although these are more often used to distinguish between multiple end-matter sections or subsections.
Headings are styled through CSS and add an [edit] link. See this section for the relevant CSS. Four or more headings cause a table of contents to be generated automatically. Do not use any markup after the final heading markup – this will either break the heading, or will cause the heading to not be included in an edit summary.
The MediaWiki software, which drives Wikipedia, allows the use of a subset of HTML 5 elements, or tags and their attributes, for presentation formatting. [1] However, most HTML functionality can be replicated using equivalent wiki markup or templates. These alternatives are generally preferred within articles because they are often simpler for ...
They must be nested sequentially—beginning at level 2 (==) for the main headings, then level 3 (===), and so on. Level 1 headings, automatically reserved for the article title, should not appear within the article's body text. Skipping heading levels for emphasis disrupts the logical hierarchy and should be avoided.
A collapsible element contains a toggle a reader can use to show or hide the element's content. Elements are made collapsible by adding the mw-collapsible class, or alternatively by using the {} template, or its variants {{Collapse top}} and {{Collapse bottom}}.
Avoid using smaller font sizes within page elements that already use a smaller font size, such as most text within infoboxes, navboxes, and references sections. [g] This means that <small>...</small> tags, and templates such as {} and {}, should not be applied to plain text within those elements. In no case should the resulting font size of any ...
reStructuredText (RST, ReST, or reST) is a file format for textual data used primarily in the Python programming language community for technical documentation.. It is part of the Docutils project of the Python Doc-SIG (Documentation Special Interest Group), aimed at creating a set of tools for Python similar to Javadoc for Java or Plain Old Documentation (POD) for Perl.
The basic concept here is to use the div element within a Wiki article's markup code to identify certain content (which we'll call the "details" here) that we want the user to be able to "show" or "hide".