The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
The {{shortcut}} template places a notice on pages that there is a shortcut available. This may make it easier for people to easily link to pages (especially in the Appropedia and Help namespaces).
It may be appropriate for a bot to update piped links from time to time, in order to provide clearer results in search engines, if someone is using a search engine to look for a page. However, this is less of an issue with pages in the Appropedia and Help namespaces
Capital letters are preferred for shortcut names. This is so that links to policy and help pages stand out clearly in discussions, e.g. Appropedia:BOLD. All-uppercase shortcut names also distinguish them from ordinary page names, and make shortcuts more legible when the {{Shortcut}} template displays them in a small font. This reflects the standard usageW in Wikipedia's help and project namespaces.
Internals
A shortcut is a type of redirectW,W page. Its content is very simple, for example the Appropedia:BOLD shortcut contains:
#REDIRECT [[Appropedia:Be bold!]]
where {{R from shortcut}} is a template that adds the shortcut to the Category:Redirects from shortcuts category.
Prefixes
Shortcut prefixes resemble namespace prefixes, but they do not correspond to literal namespaces on Appropedia. All the shortcut pages are actually pages in the main (article) namespace.
Ideally, shortcut prefixes should reflect the namespaces that the linked-to pages are in:
but some shortcuts on Appropedia do not follow this rule.
Note that "A:" is an alias - that is, it will automatically direct the link to the "Appropedia:" prefix. It is impossible (and unnecessary) to edit a page starting with "A:". For any page in this namespace (e.g. Appropedia:Portfolios) the "A:" prefix link will also work (Appropedia:Portfolios).
Shortcut
|
Full name
|
Maintenance and request pages
|
Appropedia:ADMIN, Appropedia:Admin, Appropedia:admin, Appropedia:admins
|
Appropedia:Administrators
|
Appropedia:BT
|
Appropedia:Bot tasks
|
Appropedia:TD
|
Appropedia:To do
|
Appropedia:M
|
Appropedia:Maintenance
|
Appropedia:DEV
|
Appropedia:Site development
|
Appropedia:AT, Appropedia:at
|
Appropedia:Site development/archive (Admin tasks)
|
Appropedia:GT
|
Appropedia:Gnome tasks
|
Policies and guidelines
|
Appropedia:BOLD
|
Appropedia:Be bold!
|
Appropedia:Trau dich
|
German version of Appropedia:Be bold!, not a shortcut, in article space
|
Appropedia:C
|
Appropedia:Copyrights
|
Appropedia:NPOV, Appropedia:npov
|
Appropedia:Neutral point of view
|
Appropedia:OC, Appropedia:ORIG, Appropedia:orig
|
Appropedia:Original content
|
Appropedia:OR
|
Appropedia:Original research
|
Appropedia:P, Appropedia:POL, Appropedia:RS
|
Appropedia:Policies
|
Appropedia:RW, Appropedia:G
|
Appropedia:Grundsätze
|
Appropedia:PERM
|
Appropedia:Page permissions
|
Appropedia:W
|
Appropedia:Encyclopedic material
|
Appropedia:DIFF, Appropedia:diff, Appropedia:wikipedia, Appropedia:wp
|
Appropedia:Appropedia is different from Wikipedia
|
Appropedia:NOT, Appropedia:not
|
Appropedia:What Appropedia is not
|
Appropedia:NRFC, Appropedia:nrfc
|
Appropedia:No redirects for categories
|
Appropedia:RIGOR, Appropedia:rigor
|
Appropedia:Rigor
|
Project pages
|
Appropedia:CP
|
Appropedia:Community portal
|
Appropedia:CT
|
Appropedia:Content types
|
Appropedia:HIC, Appropedia:hic
|
Appropedia:High impact content
|
Appropedia:HIST
|
Appropedia:A history of collaboration
|
Appropedia:LANG
|
Appropedia:Languages
|
Appropedia:N
|
Appropedia:Networking
|
Appropedia:PORT
|
Appropedia:Porting
|
Appropedia:S
|
Appropedia:Scratchpad
|
Appropedia:SC
|
Appropedia:Shortcuts
|
Appropedia:SV, Appropedia:stable
|
Appropedia:Stable versions
|
Appropedia:TW
|
Appropedia:Transwikiing
|
Appropedia:UX
|
Appropedia:User experience
|
Appropedia:NAME, Appropedia:name
|
Appropedia:Name
|
Appropedia:PART, Appropedia:part, Appropedia:partners
|
Appropedia:Partners
|
Appropedia:PROMO, Appropedia:promo
|
Appropedia:Publicity
|
Help pages
|
Help:AIT
|
Help:Add image tutorial
|
Help:CAT, Appropedia:CAT
|
Help:Categories
|
Help:CREATE, Appropedia:CREATE
|
Help:Creating a page
|
Help:MC
|
Help:Monitoring changes
|
Help:SKIN, Appropedia:skin, Appropedia:skins, Help:skin, Help:skins
|
Help:Skins
|
Help:SRD, Appropedia:SRD
|
Help:Soft redirect
|
Help:U
|
Help:Userboxes
|
Discussion pages
|
Appropedia:PD
|
Appropedia talk:Appropedia policy discussion
|
Appropedia:VP
|
Appropedia talk:Village pump
|
Appropedia:TQ
|
Appropedia talk:Technical questions
|
Categories
|
, Appropedia:ASD, Appropedia:SD
|
Category:Appropedia site development
|
Miscellaneous
|
Portals
|
User pages
|
User:TTASKS, User:TT
|
User:Teratornis/Tasks
|
User:TTPORTING
|
User:Teratornis/Template porting: theory and practice
|
Articles
|
IWM, iwm
|
Interwiki map (should be a project page instead)
|
PDS
|
Public Domain Search
|
WN, wn
|
Wikis for sustainable development
|
Shortcut links are useful in edit summaries, particularly when making formal edits. A formal edit is an edit which does not appreciably change the content of a page, but brings its form, layout, naming, etc. into better compliance with Appropedia's policies and guidelines. Edit summaries can contain wikilinks, but the limited space in an edit summary leaves little room for links to long page names. Linking to shortcuts saves space and is informative to other editors who may not be familiar with the policy or guideline that motivated an edit.
Page dataAuthors |
Teratornis, Chris Watkins |
---|
License |
CC-BY-SA-3.0 |
---|
Language |
English (en) |
---|
Related |
0 subpages, 41 pages link here |
---|
Aliases |
Appropedia:SC |
---|
Impact |
911 page views |
---|
Created |
April 24, 2007 by Chris Watkins |
---|
Modified |
May 25, 2023 by Felipe Schenone |
---|
Cite as |
Teratornis, Chris Watkins (2007–2023). "Appropedia:Shortcuts". Appropedia. Retrieved March 28, 2024. |
---|
API queries |
basic, semantic, html, files, more |
---|
Cookies help us deliver our services. By using our services, you agree to our use of cookies.