Search results
Results from the WOW.Com Content Network
The following help topics deal with templates: m:Help:Template; m:Help:Advanced templates; This help topic deals with table design (since most templates use tables, this may be useful): Help:Table; And finally: Help:Conditional expressions
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.
See also: the {} template. The #if function selects one of two alternatives based on the truth value of a test string. {{#if: test string | value if true | value if false}} As explained above, a string is considered true if it contains at least one non-whitespace character. Any string containing only whitespace or no characters at all will be ...
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 helper template is designed to be used in other templates. It can help editors create template code that is more self documenting. A major advantage of using this template over using the construct {{#if:{{{1|}}}{{{2|}}} |…}} is that if the first parameter is not empty then the second parameter is not evaluated.
Each nested use adds 5 levels to the template expansion depth, so 7 nested if-templates would use 35 levels (5*7) of the 41-level limit. Using P-if syntax: A similar if-structure can be coded without Template:If, by using the {} and {} templates in a "P-if" structure. Template:P1 always returns parameter 1, and P2 returns the 2nd. So, a ...
This template can take any number of unnamed parameters as parameters accompanying the template link (or name); see Examples below. Examples Use the displayed value in the code column, not the underlying source code.
This template is used on approximately 6,900 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.