Jump to content

Template talk:Redirect category

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Default categorisation

[edit]

There's a proposal to stop this template from automatically placing the category it's used on in Category:All redirect categories. The discussion is at Category talk:All redirect categories#Too many subcategories. Uanfala (talk) 20:45, 17 June 2016 (UTC)[reply]

Instructions

[edit]

@Paine Ellsworth: This template currently displays instructions to place, for example,

{{Rcat shell|{{R from fictional character|Star Wars}}}}

on a redirect, whereas simply

{{R from fictional character|Star Wars}}

would suffice in that case (Category:Star Wars character redirects to lists).

Please can this be simplified? – Fayenatic London 12:31, 2 July 2019 (UTC)[reply]

To editor Fayenatic london: yes, as the documentations for all the rcats show, any rcat can be used in the {{Redirect category shell}} or by itself without the shell. It's up to editors which way they want to categorize redirects. As the shell's documentation shows, there are definite advantages to using it for one or more rcats, and that is why templates like this recommend to use the shell. Paine Ellsworthed. put'r there  09:37, 3 July 2019 (UTC)[reply]
Thanks... but it is rather hard to understand. After multiple links to various templates, even "For more information, follow the template link" is cryptic. Can we change it along the lines of Special:Diff/904619235, i.e. to display the simple alternative usage, and link to a specific template for more info? – Fayenatic London 10:20, 3 July 2019 (UTC)[reply]
Well, I don't see why not. I just clarified (hopefully) some of the text, to include the "follow the template link" dimness. Also, consider that the change you want to make is already part of each and every redirect category (rcat) template's documentation, so I'm not sure how much good it does to include it on a category page that is seldom visited. Paine Ellsworthed. put'r there  10:54, 3 July 2019 (UTC)[reply]