Template:Shortcut

Template documentation[view] [edit] [history] [purge]

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 should not be used for articles in the main namespace, because the graphic produces an unavoidable self-reference.

1. Insert the shortcut template.
2. Create a redirect page. 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 REDIRECT as the top-line on your redirect page:

   #REDIRECT [[Namespace:Title of page with#Optional very long section name]]

3. Verify operation. Note that shortcut templates should display in all capitals, but operate without all capitals.

Notes
Shortcuts are used mainly 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. For example, GA:SHORT redirects to GoArch:Shortcut and therefore, GoArch:Shortcut renders a shortcut box listing GA:SHORT. 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.

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.

Parameters

{{shortcut}} takes the following parameters:

• 1, 2, 3... - the shortcut links.
• msg - an unlinked message that goes after the shortcut links.
• category - set to "no", "n", "false" or "0" to suppress error categories.

Examples

Code	Result
{{Shortcut|GA:SHORT}}
{{Shortcut|GA:MOS|GA:GUIDE|GA:POLICY}}
{{Shortcut|GA:MOS|GA:GUIDE|msg=A message}}

Anchors

These templates automatically add an HTML anchor for each shortcut name parameter. For example, if a shortcut box with the shortcut GA:SHORT is placed on the page GoArch:Shortcut, then the link GoArch:Shortcut#GA:SHORT will take you to the position in the page where that shortcut box is placed.

For instance, try this link: #GA:SHORT

This makes it easier to create a shortcut for a section of a page, because you can refer to the anchor when creating the shortcut redirect itself. Like this:

#REDIRECT [[Pagename#GA:SHORT]]

Positioning

This template is usually placed below the section header or at the top of a page.

See also

• GoArch:Shortcut – The how-to guide and guideline about how and when to create shortcuts and shortcut boxes. A must-read for anyone handling shortcuts.
• {{Anchor}} – a way to overcome the otherwise permanent fact that section titles are the only way to link to a section
• {{Ombox/shortcut}} – for embedding into message boxes
• {{Policy shortcut}} – for shortcuts to sections of policy pages
• {{R from shortcut}} – for placement on the redirect page
• {{Shortcut-l}} – for left aligned normal shortcuts
• {{Template shortcut}} – used for shortcuts/redirects to a template page