Search results
Results from the WOW.Com Content Network
If the template has a separate documentation page (usually called "Template:template name/doc"), add [[Category:Sports schedule templates]] to the <includeonly> section at the bottom of that page.
This template employs intricate features of template syntax. You are encouraged to familiarise yourself with its setup and parser functions before editing the template. If your edit causes unexpected problems, please undo it quickly, as this template may appear on a large number of pages.
[[Category:Athletics schedule templates]] to the <includeonly> section at the bottom of that page. Otherwise, add <noinclude>[[Category:Athletics schedule templates]]</noinclude> to the end of the template code, making sure it starts on the same line as the code's last character.
This template provides a legend for scheduling of athletics events at a particular long-term event (e.g. the Olympics). It allows for the user to style the pages consistently with HTML classes. See current uses and the TemplateStyles page.
This template employs intricate features of template syntax. You are encouraged to familiarise yourself with its setup and parser functions before editing the template. If your edit causes unexpected problems, please undo it quickly, as this template may appear on a large number of pages.
{{MLB Schedule Entry | number = game number | w/l = w if the game was won, l if lost, t if tie, p if postponed, blank if game hasn't occurred yet; lowercase | date = date of the game | away = 'yes' if this is an away game | opponent = the name of the opponent played | score = final score of the game; use dash (–) instead of hypen | extrainn = if the game went into extra innings (i.e. '11 ...
This template is used on approximately 28,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.
This template is used on approximately 12,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.