On November 27th, 2022, the 8,000th article was added to the SuccuWiki!
Template:Shortcut/doc: Difference between revisions
mNo edit summary |
m (→Positioning) |
||
Line 55: | Line 55: | ||
* Placing the shortcut above the section header; a bit confusing when editing | * Placing the shortcut above the section header; a bit confusing when editing | ||
* Creating the redirect to the section header, not the shortcut; this would break if the section header was renamed | * Creating the redirect to the section header, not the shortcut; this would break if the section header was renamed | ||
* Placing an | * Placing an anchor in the section header that duplicated the shortcut | ||
These fixes are no longer needed, but do not break the current implementation. | These fixes are no longer needed, but do not break the current implementation. |
Revision as of 21:43, 9 October 2012
This is a documentation subpage for Template:Shortcut. It contains usage information, categories, interlanguage links and other content that is not part of the original template page. |
This is the documentation for {{shortcut}} and its sister templates. The shortcut family of templates is put into context here, but they each have their own documentation pages, see below.
A shortcut template is similar to the anchor template, but it adds a visual box graphic to the rendered page, as well as providing an alternative name. Creating a redirect page is a requirement to fulfill the shortcut mechanism.
Usage
The characteristics of the box graphic are determined by which of the family of shortcut templates are chosen. For example, the policy shortcut box has the word policy on it for use on policy pages. The graphic alignment of the box depends on the whether it's a shortcut or a shortcut-l:
- {{shortcut}} – right-aligned box
- {{shortcut-l}} – left aligned box
- {{policy shortcut}} – shortcut that also says "policy"
- {{Ombox/shortcut}} – shortcut that embeds into message boxes
This template is not normally used for articles in the main namespace, because the graphic produces an avoidable self-reference.
- Insert the shortcut template.
- Create a redirect page with the R from shortcut template suffixed to the redirect. Name the page after your shortcut name. Include the namespace name in both the shortcut name and the redirect page name. For example, substitute your own shortcut name as the title of the page, and substitute the proper namespace, then add the following as the top-line on your redirect page:
- #REDIRECT [[Namespace:Title of page with#Optional very long section name]] {{R from shortcut}}
- Verify operation. Note that shortcut templates should display in all capitals, but operate without all capitals.
- Notes
These templates are mainly used on user pages and talk pages in reference to the Wikipedia, Help, and Portal namespaces. These templates inform about the shortcuts available to the page they are on. It is a self-reference that is normally avoided in the main article namespace.
The point of these templates is not to list every single redirect for a page (indeed, that's what "What links here" is for). Instead, they should list only one or two common and easily-remembered redirects.
The shortcut template can take up to five (5) shortcuts as parameters.
For policy pages, one can use the {{policy shortcut}} template, which takes up to ten (10) shortcuts as parameters. Be careful not to use a policy template on a guideline or essay.
Examples
Code | Result |
---|---|
{{Shortcut|WP:SHORT}}
|
|
{{Shortcut|WP:V|WP:VERIFY|WP:SOURCE}}
|
Anchors
These templates automatically add anchors.
Thus, if you make a shortcut for a section of a page, then you can use the anchor in the shortcut redirect itself. Like this:
#REDIRECT [[Pagename#WP:SHORT]] {{R from shortcut}}
Positioning
This template is usually placed below the section header or at the top of a page.
Before July 26, 2010, when the anchor was inside the box, this caused the section header to scroll above the page window. Fixes for this issue included:
- Placing the shortcut above the section header; a bit confusing when editing
- Creating the redirect to the section header, not the shortcut; this would break if the section header was renamed
- Placing an anchor in the section header that duplicated the shortcut
These fixes are no longer needed, but do not break the current implementation.