41,504
edits
MarioWiki:Navigation templates: Difference between revisions
no edit summary
m (Text replacement - "(\[|\|)MW:" to "$1SMW:") |
No edit summary |
||
| Line 42: | Line 42: | ||
Both styles have their pros and cons when it comes to functionality, but while horizontal headers used to be the only method used by the Super Mario Wiki, vertical headers have become the more common choice. This is mainly because they take up less space than horizontal bars, resulting in more compact templates. Unlike horizontal headers, they also lend themselves to header-subheader formatting, with subheaders nested within the column of headers, like in {{tem|LM}}. | Both styles have their pros and cons when it comes to functionality, but while horizontal headers used to be the only method used by the Super Mario Wiki, vertical headers have become the more common choice. This is mainly because they take up less space than horizontal bars, resulting in more compact templates. Unlike horizontal headers, they also lend themselves to header-subheader formatting, with subheaders nested within the column of headers, like in {{tem|LM}}. | ||
Horizontal headers generally only appear in complex templates that require an extra level of structure beyond the regular two-tier header-subheader system, such as {{tem| | Horizontal headers generally only appear in complex templates that require an extra level of structure beyond the regular two-tier header-subheader system, such as {{tem|Quotes}}, which uses one to separate the two different sets of pages it covers. Very large templates like {{tem|Galleries}} can also use the show/hide function made possible with horizontal headers to collapse individual sections and makes the overall template more manageable. Finally, as seen in the aforementioned {{tem|SM64}} and {{tem|M&SATOWG}}, horizontal headers can be repurposed to create unique footnote sections in which symbol legends or comments can be placed. | ||
===Coloration=== | ===Coloration=== | ||
{| border="0" style="float:right;text-align:center;margin: 0 1em 0.3em 1em;" cellpadding="2px" cellpadding="2px" width="280px" | {| border="0" style="float:right;text-align:center;margin: 0 1em 0.3em 1em;" cellpadding="2px" cellpadding="2px" width="280px" | ||
!colspan=1 bgcolor=#D4D4D4| Series | !colspan=1 bgcolor=#D4D4D4| Series | ||
!colspan=1 bgcolor=#D4D4D4| Footer color | !colspan=1 bgcolor=#D4D4D4| Footer color | ||
| Line 76: | Line 75: | ||
|bgcolor=#E9E9E9|Consoles | |bgcolor=#E9E9E9|Consoles | ||
|bgcolor=#C5C5C5|#C5C5C5 | |bgcolor=#C5C5C5|#C5C5C5 | ||
|} | |} | ||
Series-wide and game-specific templates are color-coded by series. When designing a new template, specify which of the predefined color schemes to use by adding the relevant class (listed in the chart below) to the template code. For example, the first line of {{tem|SMB}} would be <code><nowiki>{| class="mw-collapsible mw-collapsed navbox mario"</nowiki></code>, while {{tem|LM}} would have the class of <code><nowiki>"navbox lm"</nowiki></code>, {{tem|DKC}} would have the <code><nowiki>"navbox dk"</nowiki></code>, etc. These classes automatically color the alternating background stripes, however the banner and header colors need to be added manually using the color codes in the chart and the format: <code><nowiki>style=background:#FF2400</nowiki></code> (using the "Super Mario" banner color as an example). If no color is specified, the banner and headers will receive default grey tones. Please note that the code <code><nowiki>bgcolor=#FF2400</nowiki></code> will not override the default colors. | Series-wide and game-specific templates are color-coded by series. When designing a new template, specify which of the predefined color schemes to use by adding the relevant class (listed in the chart below) to the template code. For example, the first line of {{tem|SMB}} would be <code><nowiki>{| class="mw-collapsible mw-collapsed navbox mario"</nowiki></code>, while {{tem|LM}} would have the class of <code><nowiki>"navbox lm"</nowiki></code>, {{tem|DKC}} would have the <code><nowiki>"navbox dk"</nowiki></code>, etc. These classes automatically color the alternating background stripes, however the banner and header colors need to be added manually using the color codes in the chart and the format: <code><nowiki>style=background:#FF2400</nowiki></code> (using the "Super Mario" banner color as an example). If no color is specified, the banner and headers will receive default grey tones. Please note that the code <code><nowiki>bgcolor=#FF2400</nowiki></code> will not override the default colors. | ||
| Line 268: | Line 267: | ||
Additionally, there are a number of specialized classes of pages, most of which have (or will eventually have) corresponding navigation templates. They are as follows: | Additionally, there are a number of specialized classes of pages, most of which have (or will eventually have) corresponding navigation templates. They are as follows: | ||
*Galleries should all | *Galleries should all have {{tem|Galleries}} | ||
*"List of ... quotes" pages should have {{tem| | *"List of ... quotes" pages should have {{tem|Quotes}} | ||
*"List of ... glitches" pages should have {{tem| | *"List of ... glitches" pages should have {{tem|Glitches}} | ||
*"List of ... media" pages should have {{tem| | *"List of ... media" pages should have {{tem|Media nav}} | ||
*"List of ... in-game music" pages should have {{tem| | *"List of ... in-game music" pages should have {{tem|In-game music}} | ||
*"List of ... profiles and statistics" pages should have {{tem| | *"List of ... profiles and statistics" pages should have {{tem|Profiles and statistics}} | ||
*"List of ... pre-release and unused content" pages should have {{tem| | *"List of ... pre-release and unused content" pages should have {{tem|Pre-release and unused content}} | ||
*The references | *The references and culture lists should all have {{tem|Culture}} | ||
*Game bestiaries should have {{tem| | *Game bestiaries should have {{tem|Bestiaries}} | ||
*Staff pages should have {{tem| | *Staff pages should have {{tem|Staff}} | ||
Finally, only mainspace articles can have navigation templates. Categories, other templates, Help pages, MarioWiki pages, user pages, talk pages and PipeProject pages should not have nav templates. While The 'Shroom has templates it uses for internal navigation, these should not be categorized as actual nav templates. | Finally, only mainspace articles can have navigation templates. Categories, other templates, Help pages, MarioWiki pages, user pages, talk pages and PipeProject pages should not have nav templates. While The 'Shroom has templates it uses for internal navigation, these should not be categorized as actual nav templates. | ||