Operator: Bsherr ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 22:50, Monday, October 29, 2018 ( UTC)
Function overview: Ad hoc template orphaning and transclusion replacement, including pursuant to WP:TFD.
Automatic, Supervised, or Manual: Supervised
Programming language(s): AutoWikiBrowser
Source code available: AutoWikiBrowser
Links to relevant discussions (where appropriate):
Edit period(s): One time runs as needed by particular task
Estimated number of pages affected: Usually between 100 and 1000 pages.
Namespace(s): All
Exclusion compliant (Yes/No): No
Function details: This is a reapproaval after the bot was deflagged for inactivity only. Following its original approval, there were no runs needed. First task is replacing Template:User x/doc with Template:User x in pages having that as the first parameter in Template:Documentation, the purpose of which is to merge redundant pages Template:User x/doc with Template:User x and allow Template:User x a normal documentation page.
Good, I can strike this from my to-do list. But, as I suggested at that
other conversation, I would choose different template names. I believe that templates, as much as possible, should be named to reflect the work that they are actually doing. The names of {{
user x}}
and {{
user x/doc}}
are mighty vague about what it is that they actually do or what their names mean. I proposed in that other conversation that the single documentation template should be called {{
user x doc}}
which name sort of describes what it is that the template does. It then gets its own documentation page,
Template:user x doc/doc. These two pages can be created and tested without disrupting the existing template structures. When tests with templates that use {{user x}}
and {{user x/doc}}
show that the new template and its documentation works as expected, then all instances of {{user x}}
and {{user x/doc}}
can be replaced with {{user x doc}}
.
What I think might be a better long-term solution would be to create a single parameterized template, perhaps {{
user lang box}}
, then we have no need to create and maintain a mess of however many individual templates we have now. Were we starting afresh today, this is likely how we would handle this task: use language codes from
Module:Lang or
Module:ISO 639 name, create another module that keeps a large data table of all of the appropriate non-English text that is rendered when the user box is rendered. This solution is really beyond the scope of this brfa, but it is offered as a suggestion for later consideration.
— Trappist the monk ( talk) 16:54, 1 November 2018 (UTC) reply