m (→Styling: spacing fix) |
m (+ __NOEDITSECTION__ in template to prevent section editing, which'll cause user confusion if clicked) |
||
| Line 53: | Line 53: | ||
<ul> | <ul> | ||
{{#fornumargs: number|value|<li>[[{{#var:value}}]]</li>}} | {{#fornumargs: number|value|<li>[[{{#var:value}}]]</li>}} | ||
</ul> | </ul>__NOEDITSECTION__ | ||
</includeonly> | </includeonly> | ||
Revision as of 00:43, 9 January 2023
This is a user interface aid for integration of subjects with the same name over different articles, i.e. Celestra, thus allowing any user to go between them without needing to click through multiple different pages.
Documentation
{{DisambigTab|article|article2|article3}}
This template supports multiple article arguments, but please limit the number 10 for performance reasons.
Example
{{DisambigTab|Celestra (TOS)|Celestra (RDM)|Celestra (TOS-RH)}}
Will generate this example (linked separately for demonstration reasons).
Notes and Caveats
Styling
By default, the organization of each link should be thus:
- Original Series article
- Re-imagined Series article
- Caprica article
- Blood and Chrome article
- Separate continuity articles, in the above order.
For the Celestra disambiguation example, the organization is thus:
- Celestra (TOS) - Original Series article
- Celestra (RDM) - Re-imagined Series article
- Celestra (TOS-RH) - Separate continuity article from the Richard Hatch series, ergo the initialism "(TOS-RH)" suffix.
Redirects
Should you point to a redirect within this template call, it will show the page the redirect points to, instead of the redirect page itself.
Further, if the redirect has an anchor to it, e.g. The Fleet (TOS-RH)#Celestra, browsers will probably not "jump" you to that anchor when the tab is selected.
When used on a disambiguation page, the footer of this template prints out a list of links that are called. This may be helpful to those who have older and outdated browsers, or perhaps are on mobile devices with smaller screens.
Categorization
Due to MediaWiki technical limitations, categories from each page called within the template are reproduced on the page that this template is deployed on. Thus, it will also list the disambiguation page within those categories... there's no way around it, presently. C'est la vie.