Search results
Results From The WOW.Com Content Network
For lists of up to 30 items (may increase later) without bullets, use a {} or {{Unbulleted list}} template. Typical uses are in infobox fields, and to replace pseudo-lists of lines separated with <br />. The templates emit the correct HTML markup, and hide the bullets with CSS (see Template:Plainlist § Technical details).
''Title of list:'' example 1, example 2, example 3 Title of list: example 1, example 2, example 3 This style requires less space on the page, and is preferred if there are only a few entries in the list, it can be read easily, and a direct edit point is not required. The list items should start with a lowercase letter unless they are proper nouns.
Template:Columns-list turns a list into a list with columns. It is a wrapper for {{ div col }} , except it wraps the template by allowing for the content to be in the template rather than above and below.
This template is used on approximately 650,000 pages, or roughly 1% of all pages. To avoid major disruption and server load, any changes should be tested in the template's /sandbox or /testcases subpages, or in your own user subpage.
Ahnentafel style trees can be can be displayed using this template, but usually for fewer than six generations the customised ahnentafel templates are clearer (see Template:Ahnentafel/doc). There is also an ahnentafel template ({{Ahnentafel-tree}}), that is based on this one, that makes construction this tree simpler.
This navbox is intended for use at the bottom of the documentation pages of list-generating and -formatting templates. It takes no parameters. The above documentation is transcluded from Template:HTML lists/doc .
This template provides a WCAG/ISO standards–compliant accessible alternative to <br />-separated lists, per WP:UBLIST and WP:PLIST. It uses proper HTML list markup, which is more standards-compliant and more accessible than separating list items with <br />. Detailed reasons for using this template can be found at WP:UBLIST.
This template is used on approximately 75,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage . Consider discussing changes on the talk page before implementing them.