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).
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.
Toggle the table of contents. Template: HTML lists. ... This navbox is intended for use at the bottom of the documentation pages of list-generating and -formatting ...
''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.
{{List missing criteria}} for stand-alone lists {}, to indicate lists that should be converted to prose {{Expand list}} – for use where a list is too short/incomplete {{List to table}} – for use where a table would be better than a list {{Create list}} – for when a list is needed instead of prose
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 can be used to create an ordered list which generates numbered HTML anchors for every bullet point. This makes it much easier to maintain lists where anchors to individual entries are required. The generated anchors are named "1", "2", etc., so naturally there should be only one instance of {{bare anchored list}} per page.
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.