Wikipedia talk:Templates for discussion/Archive 27

Archive 20

←

Archive 25

Archive 26

Archive 27

Why are new postings placed at the top?

I have noticed recently, especially with increased activity on this page, that when I go to edit a section in order to add a comment, I am sometimes given the wrong section to edit. I believe that this happens because new postings are added at the top of the page, in a sort of reverse timeline, instead of being added at the logical place: the bottom. When a new section is created at the top after an editor loads a page, the sections all get their numbers shifted, and edit links on pages loaded before the new section was added do not work as expected.

Is there a good reason for adding new posts at the top of the page, instead of at the bottom? Or is this just the way it has always been done, and nobody has bothered to fix this annoyance? Or am I doing something wrong? – Jonesey95 (talk) 23:27, 9 November 2021 (UTC)

I checked the oldest version (2011) of the bot's TFDClerk settings, and it's been adding that message since its creation. Twinkle predates the bot by four years, and to be honest I don't feel like digging through that much history.

From a chronological perspective, it does make some amount of sense: if you're reading through the TFD log, you want the newest templates at the top, and as you scroll between 10 Nov and 9 Nov it would be logical to have (for example) a nomination at 1AM followed by a nomination at 11PM the night before. If the logs were "new noms at the bottom", scrolling from 10 Nov to 9 Nov on the main page would result in an 11PM nom on 10 Nov followed by a 1AM nom on 9 Nov.

Do the aesthetics of having a "proper timeline" really matter? Probably not, as I do agree that going to edit one section only to suddenly find yourself working in another one rather problematic. Just from a quick search of a few logs, with the exception of one user (who I will ping mostly just because I'm referring to them, but I don't find anything wrong with their methods) it looks like the vast majority of users are using Twinkle, so it's very possible we could have the Twinkle devs update the coding to place new nominations at the bottom, ask Anomie to tweak the TFDClerk, and call it a day. That is, of course, if there's a consensus to make this change. Primefac (talk) 09:27, 10 November 2021 (UTC)

FYI: Looks like TFD as it is today started January 14, 2006, and the instruction was present then. Anyway, post to the bot's talk page if consensus decides to change it. Anomie⚔ 16:19, 10 November 2021 (UTC)

Per WP:SILENCE I'm going to start making inroads into this; I'll let the Twinkle devs know the order needs to be changed, and once that is done we can have the bot's code updated with a new message. Primefac (talk) 11:59, 8 December 2021 (UTC)

Admin assistance with viewing deleted template code

Can an admin check if Template:Inconsistent citations used to populate Category:Articles with inconsistent citation formats? Gonnym (talk) 13:05, 14 December 2021 (UTC)

The only content was {{main other|[[Category:Articles with inconsistent citation formats]]}}, so it would appear to the case. Primefac (talk) 13:06, 14 December 2021 (UTC)

Thanks! Gonnym (talk) 13:07, 14 December 2021 (UTC)

Can anyone carry out actions in the holding cell?

I nominated that a redundant template with an identical function be merged with another template a few months ago, and came back just to check, to see that both templates still exist with nothing having changed. I saw that on the template being merged there was a {{Being deleted}} template, directing me to the holding cell, where I saw that it sat there with nothing happening to it. I noticed the closing instructions on the top of the page and read them, to see nothing deterring non-admin users from executing these tasks. Is there some reason that no one has merged the two templates? Was it my job to merge them as I was the one who nominated it for merging, and didn't know? Thanks a lot, ― Levi_OP^Talk 21:39, 15 December 2021 (UTC)

It is unclear to me why this went into the holding cell. The functionality appears to be identical. I have redirected the template and its two subpages. – Jonesey95 (talk) 22:34, 15 December 2021 (UTC)

@Jonesey95: Thanks for clearing up my issue. But to restate my question, is preforming actions in the holding cell only something that administrators can do, or could anyone? Thanks, ― Levi_OP^Talk 00:30, 16 December 2021 (UTC)

I don't know. I have the template editor permission and feel comfortable monkeying around in template space, so I just took care of a couple easy ones. It was definitely not your responsibility to take care of it. – Jonesey95 (talk) 01:06, 16 December 2021 (UTC)

There are no mandatory minimums or requirements for working on templates listed at the holding cell, other than "has a clue" and "won't break everything". Mistakes do happen, but if you're comfortable with merging, orphaning, or otherwise modifying a template in order to enact a TFD outcome, by all means feel free. If you have questions feel free to open up a discussion either there, here, or at WT:WPT (or on the user talk pages of any of a dozen users who frequent the page, though this is pretty far down the list of potential options). Primefac (talk) 08:29, 16 December 2021 (UTC)

PEIS

Just letting you guys know that the post-expand limit has been exceeded on WP:Templates for discussion. —GMX🎄^{(on the go!)} 18:28, 21 December 2021 (UTC)

I have commented out a few template examples on the December 16 page, which helped a bit. The December 14 page is still not expanding. That page has 145 out of the 673 instances of {{Tfd links}} on the TfD page, so when it falls off in a few hours, the TfD page should be in better shape. We might need to slow down our nominations just a bit. – Jonesey95 (talk) 19:54, 21 December 2021 (UTC)

Now that December 14 is no longer transcluded, the page is currently below the PEIS, at 1908801/2097152 bytes. There are 552 {{Tfd links}} templates. Somewhere between 552 and 673 nominations appears to be the limit, depending on other templates that are also present on the TfD pages. – Jonesey95 (talk) 05:36, 22 December 2021 (UTC)

Closer needed for a template-related RfD

Resolved

Anybody fancies closing the discussion at Wikipedia:Redirects for discussion/Log/2021 November 20#Template:MCN? It's been going for almost two months, has been relisted twice, and it doesn't look like any of the regular RfD closers are willing to touch it with a 10-foot pole. It's not that complicated though! – Uanfala (talk) 04:15, 26 December 2021 (UTC)

The discussion has now been closed. – Uanfala (talk) 19:11, 27 December 2021 (UTC)

Can these be G6?

Template:Party shading/Independence/block, Template:Party shading/None/block and Template:Canadian politics/party colours/Conservative (historical) were tagged, listed and overwritten by the next template nomination it seems. Could these by speedy as G6? Gonnym (talk) 16:52, 29 December 2021 (UTC)

Done, looks like they were tagged, but not added to the discussion. Given how many discussions there have been for this type of unused template, I have deleted them. Thanks! Plastikspork _―Œ^(talk) 22:47, 1 January 2022 (UTC)

Category:Unnecessary taxonomy templates standard cleanup request

@Primefac can you clear out this category again please? Thanks! Gonnym (talk) 09:34, 10 January 2022 (UTC)

 Done. Primefac (talk) 10:05, 11 January 2022 (UTC)

{{Tfd}} and {{Tfm}} break some templates

Editor The Page Maker II has nominated {{scrapped}} for merge and {{Intentionally destroyed}} for deletion. These templates are used inside table cells, and the table syntax is sensitive to details of the template syntax. The Tfm and Tfd add syntax to the emitted source that break the tables, which annoys other editors and can lead them to remove the templates under discussion, implicitly "voting" in favor of the deletion or merger.

I request that an uninvolved editor please close the the merger and the discussion as soon as possible so we can remove the Tfd and Tfm from the templates under discussion. Alternatively, an uninvolved editor can move the Tfd and Tfm to the respective talk pages of the templates under discussion is this special case while leaving the discussions active.

More generally, I believe we need a way to prevent Tfd and Tfm from breaking the nominated templates in such cases, for example by adding a parameter to suppress the emitted notification. The notification is there in an attempt to notify editors on all pages that use the template that a discussion is underway, but the effect is to mess up these pages.

At least one uninvolved editor seems to think The Page Maker II is acting in bad faith. I have not reached this conclusion, but the effect is the same. -Arch dude (talk) 18:51, 12 January 2022 (UTC)

Jonesey95 and Alkivar are the only other editors who have so far commented on the template discussions. They may or may not wish to comment here. -Arch dude (talk) 19:32, 12 January 2022 (UTC)

Place noinclude tags around the nomination and it won't cause any problems. Gonnym (talk) 21:18, 12 January 2022 (UTC)

It also won't provide the in-article notifications that were intended. This also needs to be documented. -Arch dude (talk) 21:25, 12 January 2022 (UTC)

It is - Template:Template for discussion#Disabled. Gonnym (talk) 21:59, 12 January 2022 (UTC)

@Gonnym: This did not work. {{Tfm}} contains magic code that re-interprets the noinclude. When the {{Tfm}} is invoked within noinclude tags, it changes waht is emitted, but it emits something anyway. -Arch dude (talk) 21:58, 12 January 2022 (UTC)

I have moved noinclude tags so that excess whitespace introduced by the TfX templates is no longer present. Did that help? – Jonesey95 (talk) 23:00, 12 January 2022 (UTC)

Here is a table with one cell that contains {{scrapped}} and one with {{intentionally destroyed}}:

Scrapped

Intentionally destroyed

So yes, it helped. Thanks -Arch dude (talk) 00:20, 13 January 2022 (UTC)

Discussion at Wikipedia talk:XFDcloser § RFC: Priorities for XFDcloser development in 2022

 You are invited to join the discussion at Wikipedia talk:XFDcloser § RFC: Priorities for XFDcloser development in 2022. Evad37 [talk] 00:23, 14 January 2022 (UTC)

Discussion at Wikipedia talk:Twinkle § Twinkle placing new WP:TFD nominations at wrong location on daily page

 You are invited to join the discussion at Wikipedia talk:Twinkle § Twinkle placing new WP:TFD nominations at wrong location on daily page. –Novem Linguae (talk) 05:40, 5 February 2022 (UTC)

What about the havoc caused to editing histories by a template's deletion?

One aspect of a template's deletion that I do not see addressed is the havoc that its deletion can, and often does, cause to the revisions in the editing history of an affected page. For example, this revision does not even closely resemble the revision as it existed that day. In my opinion, the impact a template's deletion has on attributable revisions in a page's history ought to be a factor of consideration in its deletion, and some manner of mitigation should be developed. I am curious if others have thoughts to these regards. Thank you.--John Cline (talk) 05:20, 7 February 2022 (UTC)

I totally agree but have been out-voted. Johnuniq (talk) 05:49, 7 February 2022 (UTC)

John Cline, I agree that it would be quite nice if there was an elegant solution to this problem. BTW, is it irony, regret, or something else that motivates your question? – Jonesey95 (talk) 05:58, 7 February 2022 (UTC)

My question is motivated by some research I recently did and the concurrent realization that such research is hampered by deletions, re-named sections, and other modifications like discontinued template parameters for example. Until then, I assumed that a permalink rendered a permanent version of a page, as it existed at the timestamp when saved/published. I realize now, how naive that assumption was, yet all things could painstakingly be overcome except for deletions (being a non-admin). I suppose this deletion reflects the way I look at deletions now, and the outcome suggests my keep !vote carried no weight. And so I asked my question here. Best regards.--John Cline (talk) 23:19, 7 February 2022 (UTC)

This is the same "problem" that even editing any template, including every nested template, makes - history view can't show you the rendered version as if every single template was at some previous date. For example, todays featured article has 137 transclusions in it - if you wanted to know what it looked like a month ago, not only would all the templates at that time need to still exist - but would also need to fetch all of those prior versions - so this is a "hard" problem. External services like archive.org can help. — xaosflux ^Talk 16:55, 7 February 2022 (UTC)

See also meta:Community_Wishlist_Survey_2022/Archive#Time_Machine_mode. — xaosflux ^Talk 16:56, 7 February 2022 (UTC)

Thank you Xaosflux. I have one question: when performing a manual history merge or restoring a deleted revision, does either of those actions allow an opportunity to modify the revision in conjunction with it's restoration? I'm trying to ascertain how one might substitute a template transclusion in one or more editing history revisions without destroying the timeline and recorded attributions. Thank you.--John Cline (talk) 00:36, 8 February 2022 (UTC)

@John Cline: no it does not, and would open a new problem of maintaining proper attribution. Also keep in mind that pages, including templates, are deleted for a myriad of reasons - some of which is that the content is inappropriate for one reason or another. — xaosflux ^Talk 01:22, 8 February 2022 (UTC)

I understand. Thank you for your reply.--John Cline (talk) 01:52, 8 February 2022 (UTC)

Please project this page

To any admin that watches this page, IP's have been removing large amounts of text on the Tfd homepage in recent days. Can anyone of you please increase the protection level of this page? --WikiCleanerMan (talk) 21:36, 25 February 2022 (UTC)

 Not done, not enough vandalism to merit protection. It's been twice this week and nothing since the New Year. Not worth it. Primefac (talk) 21:43, 25 February 2022 (UTC)

Subscribe to discussion

Would it be possible to switch to using a level 2 header for each separate discussion? In that case, it would be possible to "subscribe" to the discussions that you are personally interested in. — Martin (MSGJ · talk) 22:48, 9 March 2022 (UTC)

Can the subscribe feature be modified to work with level 4 headers or at least level 4 headers in XfDs? Gonnym (talk) 00:15, 10 March 2022 (UTC)

There's a ticket on Phabricator for adding subscriptions to level 3 headingssubheadings (h3, h4, etc.) that you guys may be interested in leaving a token or commenting on. This would allow subscribing to all sorts of useful things such as all XFD pages, RFPP, DRV, and ITN. –Novem Linguae (talk) 03:10, 10 March 2022 (UTC)

Current individual discussions are level 4. Changing to level 2 would require a significant redesign, but it might be worth trying. Changing to level 3 would probably be pretty easy, so maybe we could defer to see if the phab ticket is resolved. I know that I don't put the individual pages on my watchlist, because with 20 to 50+ discussions on each page and with most of the diffs consisting of "Keep per nom" or similar, the signal to noise ratio is too low. I just come back to the main TFD page every few days to see if there is anything of interest. Being able to subscribe to sections of interest would be useful. – Jonesey95 (talk) 04:50, 10 March 2022 (UTC)

I say wait until the phab ticket is sorted, because that will likely make this request moot. Primefac (talk) 11:04, 10 March 2022 (UTC)

RfC: Should new nominations be placed at top or bottom of daily subpage?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Moved from Wikipedia talk:Twinkle § Survey

Discussion moved here and converted to WP:RFC around this time. Steel1943 (talk) 06:24, 8 February 2022 (UTC)

Wikipedia:Templates for discussion's instructions and user scripts were recently changed from placing new entries at the top, to placing new entries at the bottom. Should we revert to old way (new entries on top), or keep the new way (new entries on bottom)? Changing involves updating multiple pages and user scripts, so let's get a clear consensus. –Novem Linguae (talk) 02:29, 8 February 2022 (UTC)

Pinging every editor of the page Wikipedia:Templates for discussion/Log/2022 February 1 to get better visibility: @AlisonW, AnomieBOT, Chlod, Dhtwiki, Elli, Explicit, GiantSnowman, Gonnym, Grahamec, Hurricane Noah, HurricaneCovid, Johnson.Xia, Jonesey95, Mackensen, Miniapolis, Nigej, Oknazevad, Pegship, PhiH, Pi.1415926535, Plastikspork, Scott, Tdslk, and Useddenim:. Not pinging WikiCleanerMan since they seemed to object to pinging above. –Novem Linguae (talk) 02:57, 8 February 2022 (UTC)

• At XFD venues where all the nominations are placed on a single log page, there is no consistency. At WP:FFD, new nominations are placed at the bottom, while new nominations are placed atop at WP:CFD and WP:RFD. There should probably be consistency between these venues, regardless of which setup is ultimately chosen. Whether they should align with venues that utilize subpages, like WP:MFD and WP:AFD, may be worth considering as well.

From an "ease of scrolling" perspective, I prefer the placement of new nominations at the bottom of the page. ✗plicit 03:25, 8 February 2022 (UTC)

• No real preference. I'm used to seeing new entries at the top of the page, but I'm sure I'd get used to the opposite since I see that every day on talk pages. After all, it's only one extra key click: End. Useddenim (talk) 03:56, 8 February 2022 (UTC)
• Keep the "new posts at the bottom" method, per my frustrated note above: "Top-posting means that sometimes clicking on a section edit link results in editing the wrong section. It happens to me multiple times per week." Most other discussion-oriented pages are date-ordered from top to bottom (oldest at the top), so it is confusing to newbies to see new stuff at the top and old stuff at the bottom. – Jonesey95 (talk) 04:12, 8 February 2022 (UTC)

  In case my note is incomplete, I agree with Steel1943 below that the whole TFD page should be ordered in the usual order of discussion pages: oldest dated section at the top (excepting the permanent stuff), newest dated section at the bottom. Each TFD subpage should be ordered in the same way. – Jonesey95 (talk) 06:55, 8 February 2022 (UTC)

• List new nominations at bottom only if the daily subpages are listed in descending order on the main TFD page (oldest date higher on the list of subpage transclusions), as I did here prior to reverting myself. As long as all the nominations appear in chronological order while viewing the main TFD page, it doesn't matter to me. Steel1943 (talk) 06:50, 8 February 2022 (UTC)
• Bottom. Per Jonesey95's comment about editing the wrong section, although I can see that the main TfD page order is now in a confusing order. Nigej (talk) 07:06, 8 February 2022 (UTC)
• Replying since I was pinged. I also experienced the issues Jonesey95 mentioned. I do however find the top easier (personally, might just be because that is what I'm used to) to find what has been updated instead of having to scroll down to unknown point - in mobile it is even more difficult. But whatever people here want, I don't really care that much about this. Gonnym (talk) 07:50, 8 February 2022 (UTC)
• Place newest entries at the bottom. It should be trivial to modify associated scripts so I am considering that a non-issue. If I'm wrong and script writers convince me otherwise, I'll consider changing my !vote. Best regards.--John Cline (talk) 08:16, 8 February 2022 (UTC)
• Bottom for consistency with how new sections on talk page work, and per local custom of putting new comments at the bottom. Johnuniq (talk) 09:59, 8 February 2022 (UTC)
• New nominations on top, older on the bottom. It's just easier to see the order of how and when nominations were made and has been done for a long time this way. Going back to January 14, 2006. But a wider discussion should have happened. The "Why are new postings placed at the top?" discussion was more a general question than a discussion prompting a widescale change. And such a change from this discussion was done in haste. And I think Primefac assumed that was a discussion necessary of making a wholesale change. It wasn't. The lack of dissenting views doesn't apply to that discussion as there was no Rfc initiated. We should revert to the old way of new nomination on top. This change was done without merit or request. An Rfc like this one is a proper venue for discussing such changes. Side note: I didn't object to pinging, it's just that Steel pinged me three separate times and I explained only one time was enough. --WikiCleanerMan (talk) 16:23, 8 February 2022 (UTC)
• I'm a new TfD watcher; so, I'm not aware of how it has been done in the past. However, where I encounter chronological ordering (e.g. talk pages, AIV, RFPP), it's usually oldest first. Is the FAC page a rare exception to that? In any case, I'm used to "bottom posting" on Wikipedia but wouldn't think that it has to imposed against local consensus. Dhtwiki (talk) 06:20, 12 February 2022 (UTC)
• I am a fan of consistency with talk pages here. Reorganizing WP:TFD on the other hand feels painful in one way since we often hit the transclusion limit there, which means new pages would not be visible on WP:TFD for a day or two in some cases (or worse, depending on if we lose admins to then have more days in the backlog). That feels bad to me. --Izno (talk) 02:12, 14 February 2022 (UTC)

  Regarding hitting the WP:PEIS limit, I think that may be coincident with very heavy activity over the past couple of months by the Wikipedia:WikiProject Templates/Unused Templates Task Force. That task force has reduced the number of unused templates in the database report from something like 13,000 to under 5,000, so I anticipate many fewer nominations of dozens of templates at a time as we move forward. Perhaps something can be done to reduce the post-expand size of {{Tfd links}}, which is the main contributor to PEIS at the TFD page. Even if it can be trimmed by 10 or 20%, that would give us significant breathing room on the page. – Jonesey95 (talk) 02:56, 14 February 2022 (UTC)

  If necessary, I would be OK with the current method of new posts going to the bottom of the daily page, but daily pages being posted with the newest day at the top of the page. The new arrangement has prevented the problem I was repeatedly experiencing until recently. – Jonesey95 (talk) 02:58, 14 February 2022 (UTC)

• I thought the standard way for Wikipedia logs was to have new discussions at the top. That's how it's done at WP:RFD, the daily AfD logs (example), WP:MFD, WP:RM#C,WP:DRV, WP:MRV, WP:FACGO, WP:GAN, WP:ITN/C.. (though not at WP:DYKN or WP:CP). – Uanfala (talk) 02:39, 14 February 2022 (UTC)

  So, when one compares like with like, there's either no consistency of a consistency in favor of top-posting. Personally I see no good reason to deviate from the status quo, which is that new posts go to the top. * Pppery * _{it has begun...} 02:42, 14 February 2022 (UTC)

  MFD, at least, uses subpages for each discussion, so the problem of clicking "edit" on a section and getting the wrong section cannot occur as it does at TFD. Not that I am recommending switching TFD to that model, as it makes things like merging discussions much trickier. – Jonesey95 (talk) 02:56, 14 February 2022 (UTC)

• No real preference. I once thought "bottom, obviously" before learning that this preference is probably little more than the default for my first email program. Not asked, but the thing I really dislike about TfD and RfD is the relisting of interesting discussions by cut-paste to a new page, result in idle watchlisting losing track of the discussion entirely. If relisting must be done and by cut and paste to a new page, I think the relister should have to ping all prior participants to the new page. --SmokeyJoe (talk) 05:25, 14 February 2022 (UTC)

  Feel free to start a new discussion about that. I do not think you will be successful in seeing a change, but regardless that is offtopic for this discussion. Izno (talk) 06:50, 14 February 2022 (UTC)

  I think it is on-topic to the point that if there is a structural revamp, it’s something else that could be considered. I feel free to start the discussion, but I don’t think it’s worth the effort on its own. SmokeyJoe (talk) 09:00, 14 February 2022 (UTC)

• This is so confusing! TFD should be structured like other XFD pages with the earliest postings at the bottom of the page and the latest ones at the top. It is very confusing as an admin to scroll to the bottom of the page at AFD and to the top of the page at TFD. As far as I remember, RFD and CFD is also structured like AFD with the oldest requests at the bottom and the newest at the top. XFD pages aren't talk pages if that's why TFD does it different from other XFD pages. Liz ^{Read! Talk!} 00:31, 15 February 2022 (UTC)
• I think one should cater more for the future than the past and a bit of consistency on where to put new entries is good, so I'd go for the bottom. NadVolum (talk) 09:29, 9 March 2022 (UTC)
• New at the top please! — Martin (MSGJ · talk) 22:43, 9 March 2022 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Howdy. Just a quick note that Twinkle was just now updated to put new entries at the top again. Sorry for the delay, Twinkle changes take awhile. –Novem Linguae (talk) 18:42, 13 April 2022 (UTC)

Template query

Hello, all,

I'm not sure where to place this query so I'm just posting it here at TFD. It's about a recent problem with Template:CS1 language sources but that template doesn't have a talk page. The problem is that even though there is an "Empty Category" tag included when the template is placed on a category page, for some reason, the bots are not recognizing it and so I need to place a second Empty Cat tag on the category page so that these language categories do not show up on the Empty categories list when they become empty. See Category:CS1 Flemish-language sources (nl) as an example of an empty category with this template (and Empty Cat tag) that is showing up on the Empty categories page.

Do you know why suddenly this would be a problem? I figure that either a) it's a problem with the template, b) it's a problem with the bot putting the lanuage categories on the Empty Categories list or c) we just haven't had empty language categories like this and haven't had to face this problem before. What do you think? Liz ^{Read! Talk!} 21:22, 6 July 2022 (UTC)

I think Special:Diff/1096824142 should fix the prolem. The problem is that Template:CS1 language sources/core used some clever magic to only show {{empty category}} if the category is actually empty, but it fails due to caching of template transclusions. * Pppery * _{it has begun...} 21:33, 6 July 2022 (UTC)

Oh, that is awesome if it works, * Pppery *. We'll see when the next Empty categories list gets issued tonight. Many thanks! Liz ^{Read! Talk!} 22:26, 6 July 2022 (UTC)

Apparently we won't see, since the category was deleted by a different admin. * Pppery * _{it has begun...} 22:28, 6 July 2022 (UTC)

Personal template

I was just wondering if there was any policy on editors creating personal templates for their own use and interests. What I'm talking about is User:ChessEric/Weather events that have affected me. I was going to nominate it but it's in User space, not Template space so I didn't know whether TFD was relevant or whether it's just an original use for a User page. Thanks. Liz ^{Read! Talk!} 01:43, 14 July 2022 (UTC)

Not aware of any policy either way, but I don't see any reason this shouldn't be allowed. * Pppery * _{it has begun...} 01:47, 14 July 2022 (UTC)

I recommend allowing wide latitude for pages in User space unless they are violating some guideline or policy. Plenty of editors create transcludable pages to enable a set of nice-looking user subpages. User-space pages should not be transcluded in article or Template space (I don't know exactly which guideline this is, but it must be one). – Jonesey95 (talk) 01:51, 14 July 2022 (UTC)

If there is such a guideline, it's not being enforced, as there are twelve user pages transcluded in mainspace: User:AnomieBOT/Auto-G8, User:Ben5218/Egyptian clubs in African competitions, User:RMCD bot/subject notice, User:Shaav/HPTransBloomsburyCount, User:Shaav/HPTransDoubleCount, User:Shaav/HPTransTotalCount, User:Tompw/bookshelf/volumes, User:WP 1.0 bot/Tables/OverallArticles, User:WP 1.0 bot/WikiWork, User:WP 1.0 bot/WikiWork/ta, User:WP 1.0 bot/WikiWork/ta/pri, and User:WP_1.0_bot/WikiWork/ww * Pppery * _{it has begun...} 03:00, 14 July 2022 (UTC)

... and a total of 362 userpages transcluded in template space. It appears that there was once a Wikipedia:Database reports/Transplanted user templates reporting this than went inactive in 2014. * Pppery * _{it has begun...} 03:07, 14 July 2022 (UTC)

A user page being transcluded onto other userpages, or user pages that look like templates (e.g. the ChessEric page linked by Liz) is perfectly acceptable. I agree with Jonesey that we should not be transcluding userpages into the Article space. There are some obvious caveats or changes that could be made, for example User:AnomieBOT/Auto-G8 and other bot-created pages probably should be in the template space, though they're obvious enough that they could probably stay there and most seem to be used in more maintenance-related areas. It looks like most of the user templates should be in the template space or deleted, as I question whether we really need half of them. Primefac (talk) 05:49, 14 July 2022 (UTC)

+1 - I don't see any brightline issues with otherwise constructive editors making non-content space navboxes or other templates in userspace for their own use. — xaosflux ^Talk 10:39, 14 July 2022 (UTC)

I agree that user page templates should never be transcluded in other namespaces. If it is, it should be moved to the template namespace. Gonnym (talk) 10:43, 14 July 2022 (UTC)

Just a minor note, there are cases where userpage templates can be transcluded in the Template space, for example {{Vandalism information}} is designed to pull content from the user's space, which is why things like User:Enterprisey/Wdefcon show up on the Quarry that pppery linked to above. I think our primary concern here should be user templates being transcluded in the article space. Primefac (talk) 10:49, 14 July 2022 (UTC)

I've nominated Shaav and Ben5218's templates. Tompw is a simple template which should be moved to the template name space. Anomie and RMCD are bot templates which aren't simple moves, but should really be moved to the template namespace and configured accordingly. The WP 1.0 ones I'm not sure. Gonnym (talk) 11:09, 14 July 2022 (UTC)

Tompw is a simple template, and I've copied the text into the article directly to avoid the need to transclude. Primefac (talk) 11:19, 14 July 2022 (UTC)

@Gonnym: Pages in user space should not be sent to TFD but to WP:MFD, even if they are being used as if they were templates. --Redrose64 🌹 (talk) 22:53, 14 July 2022 (UTC)

Pages that are templates, and being transcluded as templates, can very much be discussed at TfD. Primefac (talk) 07:26, 15 July 2022 (UTC)

Except for user boxes, even when they are in template space, apparently. Quirks of history are quirky. – Jonesey95 (talk) 13:10, 15 July 2022 (UTC)

WP:TFD#NOT says The majority of deletion and merger proposals concerning pages in the template namespace and module namespace should be listed on this page., it doesn't say Pages that are templates, and being transcluded as templates. TfD is specific to those two namespaces. --Redrose64 🌹 (talk) 06:55, 16 July 2022 (UTC)

If you want to go into the letter of the guideline and not the spirit of the guideline then...

1. WP:TFD#REASONS says The template violates some part of the template namespace guidelines, and can't be altered to be in compliance.
2. WP:TMP then says Although the Template namespace is used for storing most templates, it is possible to transclude and substitute from other namespaces, and so some template pages are placed in other namespaces, such as the User namespace.
3. So we then conclude that TfD covers template pages in the template namespace and pages which are transcluded as templates from other name spaces. Gonnym (talk) 07:33, 16 July 2022 (UTC)

@Jonesey95: This is Wikipedia:User pages#Userspace and mainspace: encyclopedia articles should never link to or transclude any userspace pages. --Redrose64 🌹 (talk) 22:53, 14 July 2022 (UTC)

Thanks for finding that guideline page. It looks like, aside from the obvious moves or TFD candidates, there are only three or four bot-oriented pages that are legitimately being transcluded in article space. We can either get them officially moved to Template space with the help of bot ops if we want to be strict with the guideline, or we can IAR in those cases and not worry about it. I would lean toward IAR for the bot pages, since they appear to be harmless and well-behaved. I might be persuadable in one or two individual cases.

As for transclusions of User pages into Template space, as long as they don't end up in article space, it's probably not a problem. Some of them could be moved if they are really templates and are not maintained by or needed by bots. – Jonesey95 (talk) 23:28, 14 July 2022 (UTC)

Bot behaviour when combining WikiProject banners (PrimeBOT/24)

Hi all, following the discussion at Wikipedia:Templates for discussion/Log/2022 May 16#Template:WikiProject Cell Signaling, it was decided to combine old WikiProject banners (including WP:Cell Signaling, WP:Genetics, WP:Computational Biology, etc) to mirror their transitions to taskforces of WP:Molecular Biology. This transition now seems to be underway, but I wanted to check PrimeBOT's behaviour for carrying out this task, as it seems to have lost some of the importance assessment info during the process (eg in this edit at Talk:Environmental DNA).

Potentially only cases with multiple taskforces involved, as this edit at Talk:BMC Bioinformatics (only WP:COMPBIO) looks ok, but then this edit at Talk:CRISPR seems ok. I just noticed because Environmental DNA's lost importance info had filtered through to WP:COMPBIO's assessment table.

If this isn't the place for this discussion, I'd be happy for someone to point me in the right direction. Thanks, Amkilpatrick (talk) 12:44, 17 July 2022 (UTC)

For the record, first place to check is the bot operator's talk page, then WP:BOTN and (I guess) here as well, in order. Talking to the bot op is the easiest way to resolve issues like this.

I'm a little confused as to what info has been lost, though:

• Special:Diff/1098427392: class preserved, importance info for each task force preserved
• Special:Diff/1098419332: class preserved, importance info for each task force preserved
• Special:Diff/1097936763: as above

Primefac (talk) 12:52, 17 July 2022 (UTC)

Thanks, that's useful info. My main query was for Special:Diff/1098427392, where importance info for each taskforce hasn't been preserved: the importance for Genetics has been carried over, but is missing for MCB & COMPBIO:

{{WikiProject Molecular Biology|class=B|COMPBIO=yes|COMPBIO-importance=|MCB=yes|MCB-importance=|genetics=yes |genetics-importance=Mid}}

Here the importance ratings were different for different taskforces as well. This is the only case that I've seen so far, but not sure if other articles will be affected in the same way. Amkilpatrick (talk) 13:07, 17 July 2022 (UTC)

OH! That's rather problematic. I didn't even notice (downsides of staring at diffs for three straight days). I appear to have missed a \s operator in there, so any |importance=<value> with a space after the = got skipped. Hopefully there aren't that many that have that issue, but I'd have to check the importance cats to figure that out. Primefac (talk) 13:28, 17 July 2022 (UTC)

Yep, I know that feeling of staring at code for hours too! The comp bio articles that lose importance info I guess will show up on the assessment summary table, and I expect this will be a small percentage which I can fix manually if need be -that might be less trivial for the other taskforces which have many more articles though. If different importance criteria for different taskforces were getting mixed up, that might be more complicated to unravel, but I don't think that's the case (or at least I haven't found an example of that). Amkilpatrick (talk) 15:03, 17 July 2022 (UTC)

The one thing I can guarantee (as well as anything is 100% foolproof) is that importances never got swapped -- the workflow was to change each WikiProject template, and then merge them together -- so the regex mixup will just have dropped the occasional importance rating. As far as COMPBIO goes, it looks like there is only one page that doesn't have an importance rating. Primefac (talk) 15:08, 17 July 2022 (UTC)

That's good to know. Maybe the one exception just happened to be one on my watchlist! If any more pop up the next time that table is updated, I'll just fix them manually, no problem. Thanks for helping with this transition, btw! Amkilpatrick (talk) 16:52, 17 July 2022 (UTC)

Nomination for deletion of Template:Philippine name

Template:Philippine name has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. RenRen070193 (talk) 01:18, 2 August 2022 (UTC)

My proposal on merging Template:Philippine name into Template:Family name hatnote

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Template:Philippine name

• Template:Philippine name (talk · history · transclusions · logs · subpages)
• Template:Family name hatnote (talk · history · transclusions · logs · subpages)

Propose merging Template:Philippine name with Template:Family name hatnote.
to avoid confusion regarding the differences between the Philippine and the Portuguese name templates. Also, there's an alternate template written on my User:RenRen070193/sandbox and I tried to replace the current one but I was prohibited by the administrator of this particular template.RenRen070193 (talk) 09:07, 1 August 2022 (UTC)

RenRen070193, are you trying to file a formal TFD for these templates? Primefac (talk) 09:08, 1 August 2022 (UTC)

@Primefac How's the format and example? RenRen070193 (talk) 13:47, 1 August 2022 (UTC)

Irrelevant. If you are attempting to file a TFD nomination, you have done it incorrectly. If you are not attempting to file a TFD nomination, then you are in the wrong location. I am just trying to determine how best to help you get the discussion you're looking for. Primefac (talk) 13:49, 1 August 2022 (UTC)

@Primefac Hello @Primefac. I'm sorry for my late response. I wrote a proposal to merge Template: Philippine name with Template: Family name hatnote for the reason to avoid confusion regarding the differences between the Philippine and the Template:Portuguese name templates since it appears to cover wide variations of naming customs across the world. Also, there's an alternate template written on my sandbox (User:RenRen070193/sandbox) and I tried to replace the current one but I was prohibited by the administrator of this particular form doing that particular template. ````

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Process for reassessing the deletion of a template

What is the process of contesting a previously made deletion? In context of a bulk nomination (see Wikipedia:Templates for discussion/Log/2017 September 2#Template:Knight's Cross recipients of the Fallschirmjäger), the template {{Knight's Cross recipients of JG 26}} was deleted. Since 2017, all of the referenced entries have been fully expanded, attaining a minimum B-class rating with Wikipedia:WikiProject Military history. The layout of the template follows similar templates such as {{WWII women snipers}}, {{Female HSU Partisans}}, {{Women fighter pilots WWII}}, {{Heroes of the Soviet Union 37th GRD}} or {{Heroes of the Soviet Union 46th GNBR}}, just to list a few. In consequence, I would like to discuss the deletion. Thanks MisterBee1966 (talk) 15:47, 11 August 2022 (UTC)

WP:DRV. --Redrose64 🌹 (talk) 23:21, 11 August 2022 (UTC)

Confused about the TfD nomination steps

While I was perusing the guide on how to properly nominate templates for deletion, I was befuddled at the fact the in step 1, one would tag each individual template for deletion, linking to, at that point, a non-existent discussion about said template. And opening a discussion on this page. Editors, regularly editing the nominated template, would most likely want to give their two cents, but would not be able to until the discussion has been made...which, frankly, is counter-intuitive.

I even had to add the help=off parameter when tagging the templates for deletion, because it would ask me to open an entry log for discussion here, something I had done already.

Wouldn't it be more logical to start with step 2 by starting the discussion here and THEN tag each template accordingly, thereby linking to an existing talk page in the edit summary, which makes more sense, than the proposed order of steps?

I am sure this is common practice by now to follow the current guide as is, but for me it is somewhat illogical and would make more sense if the two steps were swapped or written to better inform newcomers about Tfd nomination process.

I am inviting other editors to weigh on this matter, so I can get a better picture of this quandary of mine. Qwerty284651 (talk) 21:50, 3 October 2022 (UTC)

I'm pretty sure we all just use Wikipedia:Twinkle so that the steps are semi-automated, so we have probably ignored the instructions for a while. – Jonesey95 (talk) 00:20, 4 October 2022 (UTC)

For what it's worth, AFDHOWTO (which I suspect is what TFDHOWTO is based on) has the same order of operations - tag the page, then create the discussion. This makes a bit more sense (from an AFD perspective) because the nomination template gives a link to a dedicated discussion page, wherein the user can then follow Step 2 and create the discussion. Since TFD does not structure their nominations in the same way (sections rather than transcluded subpages) it might make sense to swap the order. However, I don't think that anyone is going to be clamouring to !vote on a TFD within minutes of the template being tagged.

In other words, I do recognise there is a bit of dissonance between "best practice" and what we currently advise folks to do, but I am mostly indifferent as to whether this is a needed change (so don't "count" my comments here as anything other than comments). Primefac (talk) 08:37, 4 October 2022 (UTC)

@Jonesey95, was gonna use Twinkle, but needed to nominate multiple templates at once, hence why I went the old-fashioned route. Writing the same TfD reason 4 via Twinkle times would have been copious. Qwerty284651 (talk) 12:46, 4 October 2022 (UTC)

For what it's worth, if you're doing multiple pages in a single nom, use Twinkle for the first page, add the other templates to the nomination, and then tag the templates manually. Primefac (talk) 12:54, 4 October 2022 (UTC)

Sort of like a combo of both Twinkle and regular template tagging. Qwerty284651 (talk) 12:58, 4 October 2022 (UTC)

I use Twinkle to nominate all of the templates in a group (I find that I need to pause for three or four seconds between them to avoid self-edit-conflicts). I use a real rationale for the first nom, then put "will merge" as the reason for the others. I then edit the TFD page to merge the noms. It's a bit clunky, but it works for me. – Jonesey95 (talk) 13:15, 4 October 2022 (UTC)

So, you are applying an AfD approach to a TfD nom with summary line "will merge" with Twinkle. Qwerty284651 (talk) 13:25, 4 October 2022 (UTC)

Yeah, I've done that before as well. Most of my batch-noms have been things like 100+ templates, so "manual" via AWB is actually how I do it! Primefac (talk) 13:17, 4 October 2022 (UTC)

@Primefac I mostly focus on tennis articles, so while it would be cool to weed out single-use templates using AWB and batch-nom them, I just don't have the know-how to set up the regex for that purpose or any other for that matter. Qwerty284651 (talk) 13:28, 4 October 2022 (UTC)

There isn't really any regex; on each template you would prepend the TFD notice (which I usually copy/paste from the first template I've nominated), changing the page name in that copied text to {{subst:PAGENAME}}. Primefac (talk) 13:33, 4 October 2022 (UTC)

Unclear wording

The following does not make sense to me:

If this is a deletion proposal involving a template and a category populated solely by templates, add this code after the Tfd2 template but before the text of your rationale:

YorkshireExpat (talk) 21:04, 30 October 2022 (UTC)

Does this mean the Catfd2 template goes inside the Tfd2 template? YorkshireExpat (talk) 21:06, 30 October 2022 (UTC)

Correct; all that {{Catfd2}} does is add a {{tfdlinks}} line for the category, with the category-specific parameters to make sure it shows up properly. After publishing changes, the cat will appear in the list along with the other template(s). That being said, I can see the issue, so I have updated the wording to make it more clear that it goes in the |text= field before the rationale. Primefac (talk) 10:36, 31 October 2022 (UTC)

Tagging categories listed at TFD

I'm looking through the instructions, and I'm not clear how to tag a category that is solely populated by templates. I see that it is clear on how to include the category in the discussion, but it does not provide any information how to tag the category itself. Steel1943 (talk) 21:08, 31 October 2022 (UTC)

Ha, looks like the section right above mine is related! Steel1943 (talk) 21:09, 31 October 2022 (UTC)

If you want to delete a category that is populated solely by templates, I believe CfD is the proper venue for that; if the discussion determines that deletion is appropriate, the cat will be removed from the templates accordingly. Of course, if you are referring to "what to do with the category if the template that populates it is deleted", that's a case for WP:G8; you don't need to tag the category during the TfD. Primefac (talk) 09:35, 1 November 2022 (UTC)

template:timeline Windows

Can someone open a discussion about that template? It is getting lengthier these days.197.244.78.225 (talk) 16:00, 7 January 2023 (UTC)

Template talk:Timeline Windows is the place for that discussion. – Jonesey95 (talk) 16:22, 7 January 2023 (UTC)

Thank U Jonesey95. I posted a discussion there months ago but nobody responded. What to do now?197.244.78.225 (talk) 16:27, 7 January 2023 (UTC)

You could try cross-posting to Talk:Microsoft Windows to garner more opinions. Primefac (talk) 16:32, 7 January 2023 (UTC)

Query

Hello, I have a general question for TFD regulars. My experience at other XFD areas is that deletion discussions run for at least 7 days. But at TFD, they frequently close early. I notice the other day, one discussion was closed just 2 days after it was started! Why is this done? Is there any good reason for not letting discussions run a full week? Thanks for any insight you can offer for why things are done different here at TFD. Liz ^{Read! Talk!} 03:36, 19 January 2023 (UTC)

@Liz: Please provide examples of a few TfDs which you believe were closed early. --Redrose64 🌹 (talk) 19:55, 19 January 2023 (UTC)

Hello, Redrose64,

Well, if you look at Wikipedia:Templates for discussion/Log/2023 January 17, you'll see nominations that were filed two days ago being closed today. Often I see them closed after 4 or 5 days open but these were closed after just 2 days. I will say that as far as I know, there are only 3 or 4 admins who patrol and close TFDs and only a few editors who participate in discussions so it could be that closers believed they had heard from all of the regulars and there would be no further input coming to a discussion so it can be safely closed. I also don't want to single out a particular closer, I regularly see this at TFD. Liz ^{Read! Talk!} 02:32, 20 January 2023 (UTC)

Have you tried asking Plastikspork (talk · contribs)? --Redrose64 🌹 (talk) 21:08, 20 January 2023 (UTC)

We have had dozens of orphaned "match convenience template" discussions all close as "uncontroversial delete". I considered these as an extension of prior discussions, but I am happy to reopen the discussion if anyone feels as though there is something to discuss there. Thanks! Plastikspork _―Œ^(talk) 01:25, 21 January 2023 (UTC)

New ATA

Tired of continual "we want the final template ready now arguments at TFD, I have created a section of AATFD, WP:NOPROTOTYPE. It could probably use feedback and potentially some copyediting, but I thought folks here would like to know it's available for use. Primefac (talk) 13:28, 25 January 2023 (UTC)

You've added that at Wikipedia:Arguments to avoid in deletion discussions, but that page is overwhelmingly geared towards AfD. You might want to move that section to the dedicated Wikipedia:Arguments to avoid in template deletion discussions. – Uanfala (talk) 14:03, 25 January 2023 (UTC)

Good shout - I didn't even know that page existed! Primefac (talk) 14:07, 25 January 2023 (UTC)

Subscribing to individual TFDs

Want the ability to hit the [subscribe] button to individual TFDs? Then this community wishlist wish might be of interest. The [subscribe] button is a feature of DiscussionTools that lets you receive a notification when someone replies to a section, which lets you take busy pages off of your watchlist since you can just wait for notifications. –Novem Linguae (talk) 07:25, 11 February 2023 (UTC)

Category:Unnecessary taxonomy templates purging

Category:Unnecessary taxonomy templates could use its routinely purging again. Can any admin help with this? Gonnym (talk) 19:21, 23 February 2023 (UTC)

Done! Thanks! Plastikspork _―Œ^(talk) 15:01, 24 February 2023 (UTC)

Reducing size of tfd links

We have been having problems with WP:PEIS recently, which is probably a temporary condition while the massive number of "convenience templates" are being discussed. However, it looks like the problem could be reduced by decreasing the size of the output of {{tfd links}}. One option would be to remove some of the lesser used links like "history" and/or "logs"? What do you think? Plastikspork _―Œ^(talk) 16:14, 26 February 2023 (UTC)

The problem occurs only on the main WP:TFD page, right? In such a case, an alternative solution is to follow the example of RFD: closed discussions transclude only the header and the closure statement onto the main RFD page, with the discussion itself (including all the log and history links) then visible only on the daily log page (example). – Uanfala (talk) 16:35, 26 February 2023 (UTC)

Yes, that would work when there are too many closed discussions. I have been closing many early since they are basically continuations a long series of "convenience template" discussions. If they weren't closed early, it wouldn't help, but I do like the idea. It would also reduce the amount you need to scroll through to see the active discussions if you don't use the little widget button to hide them. Plastikspork _―Œ^(talk) 17:27, 26 February 2023 (UTC)

TfD already uses something similar to RfD's approach, in that already closed discussions more than 7 days old are omitted from the main page entirely (even if there are other open discussions on the same day). RfD's collapsing logic only makes sense there because they only remove discussions from the base page when the entire day is closed. The fact that sufficiently many discussions are being closed early to warrant special code for handling that case is shocking, and I would oppose doing anything to address solely it. * Pppery * _{it has begun...} 17:43, 26 February 2023 (UTC)

I will cut back on the number of discussions I am adding each day which will hopefully solve the problem ... Frietjes (talk) 21:44, 26 February 2023 (UTC)

Another way of dealing with this problem is to create a subpage with the list of TFD links. We had to do that about a year ago when there was a lot of unused template cleanup happening. The PEIS limit of tfd links templates on the main page is somewhere around 600. – Jonesey95 (talk) 05:05, 27 February 2023 (UTC)

How about deleting the delete link? I believe all regular closers use XFDcloser anyway? --Trialpears (talk) 21:52, 26 February 2023 (UTC)

That's fine with me. Thanks! Plastikspork _―Œ^(talk) 00:34, 27 February 2023 (UTC)

Done. Hopefully enough for now. --Trialpears (talk) 09:54, 27 February 2023 (UTC)

Yes, that worked, at least for now! Thanks! Plastikspork _―Œ^(talk) 15:07, 27 February 2023 (UTC)

And even if we didn't, we would probably use Twinkle. Izno (talk) 20:10, 3 March 2023 (UTC)

TFD day headers

Your comment is requested at User talk:AnomieBOT#TFDClerk where I have proposed updating the current table-based TFD headers to use divs instead. Izno (talk) 20:08, 3 March 2023 (UTC)

"sure, good idea". Primefac (talk) 21:03, 7 March 2023 (UTC)

Yeah, seems like a good idea. Galobtter (pingó mió) 09:02, 10 March 2023 (UTC)

Category:User templates val + Category:User val

Babel user information
val-0 This user has no knowledge of Vehes (or understands it with considerable difficulty). val-1 This user has basic knowledge of Vehes. val-2 This user has intermediate knowledge of Vehes. val-3 This user has advanced knowledge of Vehes. val-4 This user has near native speaker knowledge of Vehes. val-5 This user has professional knowledge of Vehes. val-N This user has a native understanding of Vehes. val-N This user has a native understanding of Vehes.
Users by language

I don't know where to report this issue: all babelboxes in Category:User templates val use val as language code for Valencian language, but it's actually the language code for Vehes language. Compare the boxes I generated here using {{#Babel:val-0|val-1|val-2|val-3|val-4|val-5|val-N|val}}. After fixing this issue, we should also take care of moving Category:User val and its subcategories. Est. 2021 (talk · contribs) 14:48, 25 June 2023 (UTC)

I suspect that Valencian (talk · contribs) set up the templates and categories without realising that val was not the language code for Valencian (which is vlca apparently) but actually for Vehes. The #babel: system is supposed to use exactly the same codes across all Wikis that use the MediaWiki software - something like 1,000 Wikis or more. See mw:Extension:Babel. --Redrose64 🌹 (talk) 17:28, 25 June 2023 (UTC)

Yes. I suggest to move Category:User templates val (and its templates) as well as Category:User val (and its subcategories) – changing val into vlca – without leaving redirects; and we should use a bot to fix all the entries to the wrong categories, that's essential to start a correct category for users who actually speak Vehes. Est. 2021 (talk · contribs) 18:00, 25 June 2023 (UTC)

There are less than 20 transclusions of all of the templates, no bot needed. Primefac (talk) 08:25, 26 June 2023 (UTC)

Fine. I'll try to fix them on my own then, but – in case I make any mistake – your contribution is always welcome. Est. 2021 (talk · contribs) 10:45, 26 June 2023 (UTC)

Was away for the weekend and still catching up on things (both IRL and here) but I'll give a hand if I can. Primefac (talk) 11:08, 26 June 2023 (UTC)

 Done: I edited and moved the templates, categorized them into Category:User templates vlca and fixed their respective entries, tagging the redirects I had to leave with {{db-g6}} and a link to this talk. Est. 2021 (talk · contribs) 11:42, 26 June 2023 (UTC)

What's the point of deleting unused templates?

They aren't misleading or non-constructive, just unused. No argument based on taking up space makes sense. Nominating them for deletion (or really, hiding them, since nothing is truly "deleted") kind of seems like a waste of time and energy.
Please prove me wrong. I want to contribute to TfD but can't care enough. These kind of nominations feel pointless. Edward-Woodrow :) _[talk] 14:42, 18 July 2023 (UTC)

I like to think of it the other way? What's the point of keeping code that's not being used? No matter how obscure something seems people will eventually run into it when doing some cleanup project or other. * Pppery * _{it has begun...} 14:46, 18 July 2023 (UTC)

Hmm. It still seems like a waste of effort. If you live in an infinite house, and one day you come across some books you never read and don't plan to, you could track down a second-hand bookstore- or you could just move on and avoid the pointless hassle. Edward-Woodrow :) _[talk] 14:52, 18 July 2023 (UTC)

The above house example is a disease and it's called compulsive hoarding. Gonnym (talk) 16:07, 18 July 2023 (UTC)

But if you want a real answer then keeping around unused templates still requires work. If a template has WP:Lint errors then someone will need to fix them. If a template uses code (templates, modules, MediaWiki, css) code that has been removed or merged, it will need to be fixed. If a template gets vandalized and then used, someone will need to fix it (and unused templates usually don't have watchers). If an editor searches for a template and finds a few options and picks the unused and unmaintained one instead of the one that is maintained, then the readers will (usually) get an inferior experience. These are all real live costs to keeping around unused templates. Additionally, the editor experience is worse with multiple of similar templates, some unused and some not. It's harder to know what to use, and usually the documentation is lacking with the unused ones (unsurprisingly). And finally, while clearing out the backlog of unused templates, you can find templates that were removed (accident, vandalism, etc.) but should be used. Gonnym (talk) 16:18, 18 July 2023 (UTC)

What Gonnym said. The infinite house analogy is a good one. If you have a bunch of stuff in your infinite house, and someone needs to dust or clean the house occasionally, or all of the bookshelves need to be oiled, or some other maintenance task needs to be performed, having more stuff in the house makes those tasks take longer. It's the same here. Changes are made to the MediaWiki software every week or two, and pages are deleted or moved, and some of those changes mean that pages need to be updated to continue working properly. Humans do that work, generally, especially in Template space. (Look at this edit history for one example: one creation edit, and then ten maintenance edits.) Asking humans to do necessary updating work on pages that are never used is pointless; it's better to take the time to delete those pages. – Jonesey95 (talk) 16:32, 18 July 2023 (UTC)

Ahh, that makes sense. Maintenance remains necessary. Thanks. Edward-Woodrow :) _[talk] 16:35, 18 July 2023 (UTC)

Tagged testcases pages

The following testcases were tagged by the author in 2021 and 2022 but I guess the require hack does not work on testcases pages. Can an admin delete these?

• Module:Sandbox/DePiep/sfw/testcases
• Module:Sandbox/DePiep/cc/testcases

Gonnym (talk) 15:52, 1 August 2023 (UTC)

Done. Primefac (talk) 08:47, 2 August 2023 (UTC)

Discussion at Template talk:Rotten Tomatoes prose § RfC: Should this and similar templates be substonly?

 You are invited to join the discussion at Template talk:Rotten Tomatoes prose § RfC: Should this and similar templates be substonly?. {{u|Sdkb}} ^talk 21:00, 1 December 2023 (UTC)

Possible addition

There seems to be a consensus in-use, wrapped templates differentiating articles and sections ought to be kept . Should this be added at the top of this page (since these templates are still regularly nominated for merging)? Mach61 (talk) 17:32, 5 October 2023 (UTC)

If you're talking about a prohibition to be listed at Wikipedia:Templates for discussion § What not to propose for discussion here, I would say no, because not all of them are kept. If you are talking about suggesting not to nominate these types of pages, WP:TFDO might be the place to edit. That being said, I'm not 100% sure to what template(s) or type(s) of template you are referring. Primefac (talk) 20:04, 5 October 2023 (UTC)

Added Mach61 (talk) 21:51, 5 October 2023 (UTC)

Did I miss links to actual TFD discussions in which these templates were kept? Some examples would be nice. I have vague memories of at least one of them being merged, but I could be wrong. Either way, a statement like this added to TFDO should have a couple of TFD links backing it up, either there or here. – Jonesey95 (talk) 21:55, 5 October 2023 (UTC)

I linked the talk pages in my initial post Mach61 (talk) 21:56, 5 October 2023 (UTC)

You should really link the discussions directly. Primefac (talk) 07:38, 6 October 2023 (UTC)

Or at least clarify what people should be looking at - presumably the first boxed / {{ Old AfD multi}} section of the pages linked to that in turn links to failed delete and merge discussions. I can't tell what keep discussion the diff is supposed to highlight. RudolfoMD (talk) 00:26, 8 December 2023 (UTC)

Automatically listing old discussions

TfDs involving this template:

• 2023 December 1 – Keep
• 2023 March 1 – Merge

I've long been jealous of AfD and their box with previous discussions about a page. I've started working on a bot that can add these here and just wanted to make sure there's consensus that this would be a good thing and discuss potential implementation questions. My plan is that if a template is linked in {{Tfd links}} has been linked in {{Tfd links}} in any previous discussions said discussion will be linked in a template like {{Other TfDs}} (example included) where the date and result is included. My hope is that this functionality will both be convenient and improve decision making and hopefully be expanded to include other venues in the future. --Trialpears (talk) 14:06, 27 December 2023 (UTC)

I think I'm being dense, but are you wanting to have a bot automatically add in the Special:Prefixindex box that is automatically included in {{afd2}} (since the nomination process is different for TFDs)? In other words, if Template:Example has been nominated three times for deletion, it would have a box (as you've given as an example above) to show previous discussions. If so, I'm in favour - while old TFDs are often linked on the talk page, they're not always linked and/or easy to find. Primefac (talk) 14:26, 27 December 2023 (UTC)

Yep that's exactly what I want. --Trialpears (talk) 14:29, 27 December 2023 (UTC)

Cool. Brain is engaged today, albeit in an apparently low gear. Primefac (talk) 14:33, 27 December 2023 (UTC)

The only issue I can think of, would the bot detect templates that were listed in a sub-page because the page size was too large (like Wikipedia:Templates for discussion/Log/2020 January 10/Link language wrappers with under 100 transclusions)? Not a big issue if it can't. (I don't have an example of a list that was kept if it only checks of non-deleted templates) Gonnym (talk) 17:14, 27 December 2023 (UTC)

That has happened a handful of times ever with no consistent format so I don't plan on supporting that. Same for pre-2006 nominations because they didn't really do closing consistently. There are also 50-ish other discussions that for some reason aren't detected properly. It can be April's fools weirdness, containing = signs in the template name, a manually edited results sentence or that person who used to enclose the header in the close div messing up my section based system. I may fix some of these manually but generally I think it's fine given that only about 0.1% of discussions are in this category. I'm planning on doing a BRFA when I'm back at a computer since the code is nearing completion. Trialpears (talk) 16:26, 28 December 2023 (UTC)

BRFA filed. --Trialpears (talk) 20:12, 28 December 2023 (UTC)

Substituting a template before taking it to TfD

Hi! User:Timeshifter and I are currently debating whether it is permissible to substitute a template en masse (e.g. by adding {{always subst|auto=yes}}) when you plan on taking it to TfD immediately afterwards, in the interest of saving time. We tend to disagree on a lot (in my opinion, collegially), so rather than argue back and forth I figured I would just ask for some outside perspectives on this issue. Best, HouseBlaster^talk 14:47, 2 January 2024 (UTC)

Absolutely not. That is gaming the system, giving yourselves an excuse to claim "this template should be deleted because it is not in use". --Redrose64 🦌 (talk) 15:35, 2 January 2024 (UTC)

We had already agreed that further uses of these subtemplates would only occur via auto-substitution. So there was no gaming. And these subtemplates are breaking stuff in some cases when not substituted. So we could have auto-substituted before any TfDs. Houseblaster rushed to TfD without agreement. The other participant in the discussion wanted to auto-substitute first also. It also gives us time to change our minds on the subtemplates if we decide to keep any of them, but only after rewriting them. It would not be wise to rewrite them until the auto-substitution is done. This way we can do more tests before undeprecating any rewritten ones.--Timeshifter (talk) 00:25, 3 January 2024 (UTC)

My argument is that there is a fundamental difference between deciding to convert a template to subst-only and keeping it versus convert a template to subst-only and deleting it. I agree that if they are to be used further they should be substituted. At the talk page of the template, we can debate whether it should be substituted or not, but we can't debate whether we should delete it. To resolve which of those two paths to take—either subst-and-keep or subst-and-delete—we go to TfD before substituting it so people can get an accurate picture of where it is used. I brought the two templates I did to a discussion—namely, "templates for discussion"— D because I believed they should be merged/deleted, and wanted to discuss that point. We should not waste time on a discussion about having a discussion to delete a template. HouseBlaster^talk 00:50, 3 January 2024 (UTC)

We can debate on the overall template talk page which subtemplates should be revised, substituted, deprecated, redirected, deleted, etc.. Discussion can happen anywhere. If we decide on the talk page to delete, then we have to go to TfD to actually get it done. You are misinterpreting WP:LOCALCON. --Timeshifter (talk) 02:00, 3 January 2024 (UTC)

What I am trying to say is we could decide to delete the template at the talk page, but we would have to go to TfD anyways to get wider opinions before deletion. TfDs can be closed as keep or delete, but keep but make subst-only would be a valid outcome, too. I don't see having a discussion, deciding we should delete the template, just so we can have another discussion at TfD about potentially deleting the template to be a good use of anyone's time. HouseBlaster^talk 02:49, 3 January 2024 (UTC)

We are talking subtemplates, not templates. Nobody knows the arcane nature of their interaction better than the 3 of us currently discussing them at Template talk:Static row numbers#All subtemplates should be deprecated or auto-substituted and the following sections. And at the subtemplate talk pages before that. And one of the templates you put up for discussion can be redirected. No TfD needed for that. No TfD needed if we decide to auto-substitute and then keep a template. You should not be putting up subtemplates at TfD until the 3 of us agree that is the next step. Once we agree, there is little reason others will disagree at TfD. Because we three are currently the most knowledgeable about the intricacies of their interactions with each other and other parts of tables. So actually we save time by agreeing among the 3 of us first. --Timeshifter (talk) 03:07, 3 January 2024 (UTC)

sigh. The question asked here is not the situation that is occurring. Making a not-subst template subst-only and then sending it to TFD is not kosher. However, discussing subtemplates as they relate to the master is a perfectly acceptable talk page matter, since the subtemplates are all directly related to the main template. If no decision can be made, then it should go to TFD for further discussion. If the discussion is to delete the subtemplates, then they can just be blanked, marked historical, redirected to the main template, or (depending on the number of participants and strength of consensus) potentially deleted as a housekeeping measure. Primefac (talk) 18:55, 11 January 2024 (UTC)

Discussion at Wikipedia:Village Pump (proposals) § Bump XfD heading sizes

 You are invited to join the discussion at Wikipedia:Village Pump (proposals) § Bump XfD heading sizes about potentially increasing the header size of XfD discussions. Primefac (talk) 06:57, 9 February 2024 (UTC)

Scope

Can this page be used to discuss matters relating to a template, other than deletion or merging? For example, the use of the parameters of a template, if agreement cannot be reached on the template talk page. — Martin (MSGJ · talk) 14:47, 3 March 2024 (UTC)

Despite the name of the page, not really; it's only "for discussion" because template mergers were not deletions (according to this RM). Every once in a while someone tries to go the route of "it says discussion so let's discuss this template" but often ends up getting more backlash purely for the action than any useful feedback. If agreement can't be reached on a talk page, then I would traverse the various levels of WikiProject before maybe hitting up VPT (cross-posting to the original discussion to avoid decentralised debate, of course...). Primefac (talk) 14:54, 3 March 2024 (UTC)

Discussion at Wikipedia:Categories for discussion/Working/Manual § Other

 You are invited to join the discussion at Wikipedia:Categories for discussion/Working/Manual § Other. Specifically, please see entry on the list entitled Wikipedia:Categories for discussion/Log/2024 March 13#Category:Harold B. Lee Library-related film articles. (I am leaving this note here because it involves templates and XfD.) Thanks! HouseBlaster (talk · he/him) 18:58, 20 March 2024 (UTC)

Readability of Template:Tfd top

Template:Tfd top uses background color #e3f9df (as of Special:Permalink/1172064855). Part of the template's text is the red "Please do not modify it.", which looks like this:

... Please do not modify it. ...

This combination of colors – background #e3f9df   and foreground #ff0000   – is not very readable. It fails WCAG for normal text in a contrast checker.

In the interest of accessibility, I suggest changing the colors. For example, the foreground color can be changed to maroon (aka #800000  ):

... Please do not modify it. ...

which passes the contrast check. You can see how maroon looks with the whole text in the sandbox. —⁠andrybak (talk) 20:37, 29 April 2024 (UTC)

Other templates in Category:Deletion archival templates are also affected, but they are out of scope for WT:TFD. —⁠andrybak (talk) 20:37, 29 April 2024 (UTC)

I know you say it's not relevant, but we might as well change all of the affected templates, such as {{atop green}}, at the same time. Also, why is this thread small? Primefac (talk) 07:16, 30 April 2024 (UTC)

we might as well change all of the affected templates – sure, I'll go be BOLD. why is this thread small? – because it's out of scope. Important enough to be mentioned, but not important enough to have normal text size. —⁠andrybak (talk) 19:36, 30 April 2024 (UTC)

For reference, the brightest color for foreground which passes the contrast check with the same background is #A90000   (see also in the sandbox). —⁠andrybak (talk) 20:41, 29 April 2024 (UTC)

I'll be honest, no one is likely to care because you're improving readability, I say just go for it (for all affected templates). If people complain, point 'em here. Primefac (talk) 07:17, 30 April 2024 (UTC)

Primefac, thanks for the support :-) I'll even point my edit summaries here. —⁠andrybak (talk) 19:36, 30 April 2024 (UTC)

Bold text has an exception that your average color contrast checker will not catch that allows 3:1 (web-aware ones will note that this use is allowed). This particular line is accessible. "Accessibility" isn't a very good argument on the point.

One reason not to change it is that this is our standard red for errors and other eye-catching text of a warning nature. The closed color is not and should perhaps be reconsidered. Izno (talk) 20:27, 30 April 2024 (UTC)

The contrast checker above, webaim.org has a "Large Text" section, which is 14pt (18.6667px) and bold (font-weight: 700). For this font-size and font-weight, the red foreground color passes "WCAG AA", but doesn't pass "WCAG AAA".

In the templates, the font-size is 14px, which is 25% smaller. For me personally, the boldness only makes the readability worse for smaller text. Best way I can describe it is that because elements are thicker, the gaps between them are smaller, which makes distinguishing letters harder. I only came here, because I had been reading some TfD archives, and I have noticed that my eyes completely glossed over the the "Please do not modify it." part, because I couldn't read it.

Izno, could you please clarify what you mean by standard red for errors and other eye-catching text of a warning nature. The closed color is not? Do you mean that the chosen maroon color is not eye-catching? —⁠andrybak (talk) 20:49, 30 April 2024 (UTC)

I'm saying that red (#f00) is our standard red for such things. The background color OTOH has no standardization. Izno (talk) 20:50, 30 April 2024 (UTC)

I agree. The bold red is readable enough, and - for {{afd top}} in particular - there are more than half a million substed uses of the old color. Changing it isn't worth the inconsistency. It's certainly not worth changing them all. —Cryptic 20:59, 30 April 2024 (UTC)

All changes were reverted. —⁠andrybak (talk) 21:08, 30 April 2024 (UTC)

Considering background colors of other templates, the contrast with red of Tfd's very light green   is bad (contrast ratio 3.59:1, with needed 7:1). The worst offenders are Rfd's pale orange   (3.52:1) and {{Archive top}}'s light purple   (3.39:1). —⁠andrybak (talk) 21:08, 30 April 2024 (UTC)

@Andrybak: You may wish to read mw:Design/Archive/Wikimedia Foundation Design/Color usage. --Redrose64 🌹 (talk) 21:40, 30 April 2024 (UTC)

Discussion at WT:Deletion process § Deletion sorting should be advertised on all XFD venues

 You are invited to join the discussion at WT:Deletion process § Deletion sorting should be advertised on all XFD venues. Nickps (talk) 21:44, 17 May 2024 (UTC)

D MENA topic

{{d MENA topic}} The template was deemed delete-able mostly for not being in use, and is now on a list of things to remove from pages, this is a bit contradictory. MWQs (talk) 06:29, 17 June 2024 (UTC)

And for being an unnecessary fork. I asked for an example of where the original template wasn't working and you didn't give one. If there isn't a problem was the current one, we don't need a duplicate template. Gonnym (talk) 09:38, 17 June 2024 (UTC)

Langx

I know this isn't a discussion that many would want to jump into probably and close it, but editors are starting to bring out the pitchforks about the TfD tag, not only here (most recent) but also at other pages (like this). So either it gets closed or we disable the notice, because at this point, whoever wanted to see this discussion already saw it. Gonnym (talk) 12:26, 7 October 2024 (UTC)

Closed and updates requested. Primefac (talk) 13:16, 7 October 2024 (UTC)

Module:Tfd links

I was wondering if it is possible to add another link for an "insource" search link and not cause any significant performance issues to the TfD pages. Gonnym (talk) 11:49, 28 October 2024 (UTC)

I assume this would be for templates that may be substed or otherwise hard to tell transclusion count? Primefac (talk) 18:29, 28 October 2024 (UTC)

Yes, a lot of times when I'm not sure about a template I search with insource to make sure it's not hidden away somewhere in might-be-used scenario. Gonnym (talk) 11:45, 29 October 2024 (UTC)

Discussion at Wikipedia talk:Criteria for speedy deletion § RfC: Enacting T5 (unused template subpages)

 You are invited to join the discussion at Wikipedia talk:Criteria for speedy deletion § RfC: Enacting T5 (unused template subpages). HouseBlaster (talk • he/they) 03:02, 25 November 2024 (UTC)

Inline styles?

Moved to Template talk:Afd top § Inline styles?

 – 172.97.141.219 (talk) 07:54, 9 December 2024 (UTC)

Extended content

Right now it's

<div class="boilerplate afd vfd xfd-closed archived mw-archivedtalk" style="background-color: var(--background-color-progressive-subtle, #F3F9FF); color: var(--color-base, #000); margin: 2em 0 0 0; padding: 0 10px 0 10px; border: 1px solid var(--border-color-subtle, #AAAAAA);">

This seems to be some kind of dark mode thing? I don't really understand though -- shouldn't we be trying to use stylesheets for stuff and not inline styles? Moreover, we already have styles (e.g. afd, vfd, xfd-closed), I assume these are styled somewhere already -- why do we have inline styles in the afd-top template at all? It seems like a gigantic headache. jp×g🗯️ 05:10, 13 August 2024 (UTC)

Pinging @Sohom Datta: who was the one who made this edit. jp×g🗯️ 05:11, 13 August 2024 (UTC)

My thought process here for adding inline styles was twofold:

• I was unsure if adding templatestyles could cause the WP:PEIS limit to be breached on bigger pages
• If the {{afd top}} template was substituted, it could cause issues due to the fact that the styles might not being carried over

To my knowledge afd vfd xfd-closed don't apply any specific styles and while the inline styles do take precedence over other user-generated styles, the behaviour of the inline CSS will be analogous to it's previous behaviour if the CSS variables defined for vector-2022 are absent. Sohom (talk) 08:25, 13 August 2024 (UTC)

Tfd top dark mode

@JPxG and Sohom Datta: Related to #Inline_styles? (Template talk:Afd top § Inline styles?), can we have a similar dark mode implementation for the actual template {{tfd top}}? 172.97.141.219 (talk) 08:01, 9 December 2024 (UTC)

TFD linking discussion

There is a discussion about changing how we notify users about TFDs. Please join in the conversation. Primefac (talk) 18:45, 17 December 2024 (UTC)

Who replaced {{IPA-art}}?

I wish art had been kept. In whose contributions can I see the replacements? Nardog (talk) 12:46, 22 January 2025 (UTC)

Mine. I used {{IPA}} as the template says to do. Gonnym (talk) 12:55, 22 January 2025 (UTC)

Thanks, added specific ISO 639 codes as far as I could. You also forgot |label=—see Bertilo Wennergren, Chicxulub crater. Nardog (talk) 13:48, 22 January 2025 (UTC)

Discussion of cricket squad navboxes

There is a discussion at WT:CRIC about squad navboxes that may interest some of the editiors here. It is an attempt to gain consensus on which squads in international tournaments should have a navbox created. It does not list a specific navbox, so not sure if I should add a link to it on one of the daily pages, or if this is the correct place. It pings a number of WP:CRIC members, but seemingly no TfD regulars. Spike 'em (talk) 10:36, 25 March 2025 (UTC)

Module:Tfd links edit request: add new link

Please upgrade Module:Tfd links to add the extra "substed" link produced by {{Tfd links2}}. E.g.,:

• {{Tfd links|Uw-tpv4}} → Template:Uw-tpv4 (talk · history · transclusions · logs · subpages)
• {{Tfd links2|Uw-tpv4}} → Template:Uw-tpv4 (talk · history · transclusions · substed · logs · subpages)

Thanks, Mathglot (talk) 10:46, 14 March 2025 (UTC)

Comment: The second template uses {{Find substed}}, which is rated as "alpha", not ready for widespread deployment. – Jonesey95 (talk) 16:15, 14 March 2025 (UTC)

I also note that it assumes that the template includes a comment with the name of the template in the substed output. That's not guaranteed. Anomie⚔ 23:17, 14 March 2025 (UTC)

Yeah, I put the alpha rating there, because it involves some features of Cirrus regex that were new to me, but I doubt they will be new to Lua programmers. The point is, the concept is sound, you can test {{Tfd links2}} (or {{Find substed}}) with a ton of templates, and afaict it always brings up the correct accurate (even if not complete) results. Maybe a Lua programmer will find an even better, more robust regex than I did, but even if not, the new link is a huge boon to Tfd responders who up to now, simply cannot find real examples in the wild of templates that have been substed. (edit conflict) Mathglot (talk) 23:25, 14 March 2025 (UTC)

Not guaranteed, but there for all user warning templates currently, and could be introduced gradually to others over time. We shouldn't let the perfect be the enemy of the good: this is a clear win for Tfd responders who currently do not have a clue who is using a substed template or why, and thus have little concrete data upon which to base a decision other than general principles. It could also be used to loop in actual, substed-template users into a discussion to get their perspective; this was done here, for example. If need be, just change the link text, to 'substed (labeled)' or something. At worst, the new link could be suppressed, for those always-subst templates that do not contain the template label in the source. Mathglot (talk) 23:51, 14 March 2025 (UTC)

Actually, not suppressed but unlinked (maybe even grayed out) would be ideal, because that would tell you at a glance that you were dealing with an untagged, always-subst template, so you are basically SOL trying to find uses of it, unless you know your regexes and the message has a unique expression you can search for. But not too many responders are going to do that, even if they know how. Mathglot (talk) 01:28, 15 March 2025 (UTC)

I support the addition of this link as quite useful, as long as we trust {{Find substed}}. – Jonesey95 (talk) 13:10, 16 March 2025 (UTC)

As I've raised here, if any new link should be added it's a general insource link. Gonnym (talk) 13:35, 16 March 2025 (UTC)

That's what this is. If you have a different suggestion for different code, you can add it to the sandbox. – Jonesey95 (talk) 21:19, 17 March 2025 (UTC)

This isn't it. This searches for a hidden comment, which means that any actual usage of a template hidden in code isn't found. My oppose still stands, this code isn't good enough. Gonnym (talk) 10:42, 23 March 2025 (UTC)

Can you elaborate or explain? I do not understand what "any actual usage of a template hidden in code isn't found" means. Alternatively (or in addition), what code (or functional result of better code) would be good enough? Maybe it can be improved, if I can understand what the issue is. Mathglot (talk) 19:41, 23 March 2025 (UTC)

Still struggling with understanding the objection. One interpretation I came up with for your remark, is this: "This template does not find substed templates that have no hidden identifier, so the result set will necessarily be incomplete." That is, of course, entirely true, and I know no way of doing so, as a substed template leaves no trace. That is the whole point of having the id, to leave bread crumbs, and what this template attempts to find. If this interpretation is correct, what if we simply change the name of the template to: Template:Find hidden template id? Then, the result set would be complete, there would be no further implication about finding substed templates, and the objection would go away in that case (iiuc). Would that work for you? Mathglot (talk) 19:51, 23 March 2025 (UTC)

We could upgrade it to check whether the template contains the identifier, and by default, return empty string if it doesn't have it, which would signal Tfd links not to emit the link (unless |force=1, then it could emit a link that returns zero results). Mathglot (talk) 20:51, 23 March 2025 (UTC)

Pinging Primefac, who took part in the archived discussion you linked, who maybe can shed some light on this. Mathglot (talk) 20:18, 23 March 2025 (UTC)

I've seen this, but I also just moved so I have a bit of a backlog of things to look at. I'll remove this comment and add something more substantial when I can. Primefac (talk) 08:43, 25 March 2025 (UTC)

Didn't know this yesterday, but by pure serendipity, today I ended up at {{Uw-vaublock}} making a small wording change to satisfy an edit request – and then I noticed this edit of yours, in order to "rmv tracking template following TFD (can be tracked via commented code)", which seems eerily connected. Indeed it can be tracked that way, and this proposal hopes to democratize that and put it in the hands of everyone. Mathglot (talk) 00:32, 27 March 2025 (UTC)

Just noting that the tracking Z-number templates were removed because they were getting ridiculously large (I think at one point we had something like 300 of them) and also being re-used. Since most subst-only templates have a hidden comment giving the template name (i.e. the provenance of the message) TFD determined that the Z-numbers were unnecessary. If a subst-only template does not have a hidden comment, then it should probably have one. I'm not sure what you mean by democratisation, but anyone is welcome to edit a template to add a hidden comment (or put in a TPER if it's protected). Primefac (talk) 11:09, 5 April 2025 (UTC)

Sorry I wasn't clear; what I meant was that folks in this discussion are likely to know how to toss out a Cirrus search like User talk: insource:"Uw-tpv4" insource:/\<!-- *Template:[uU]w-tpv4 *-->/ without much trouble but most users won't (even Tfd users; even a simpler one without the hidden bit). The whole point of the template is "democratization"—i.e., to bring this squirrely search ability to everyone. Mathglot (talk) 16:35, 5 April 2025 (UTC)

• Listed at: WT:WikiProject Templates and WT:Template index. Mathglot (talk) 16:41, 25 March 2025 (UTC)
• How big are the template limit concerns these days? I removed some links a few years ago when we were hitting them like every week. Trialpears (talk) 10:41, 27 March 2025 (UTC)

  They are of much less concern today. Back in 2020 and 2021, we worked on a big project to clean out a thousands of unused template-space pages, so a perhaps over-eager group of us were crowding TFD with hundreds of nominations per week. That caused a bunch of problems with limits. That project worked through its backlog a couple of years ago, and now we are at a steady state, just picking off a few at a time. The current TFD page has just 87 nominations, which is about average and doesn't come close to hitting the limits. – Jonesey95 (talk) 23:04, 28 March 2025 (UTC)

  Deactivating edit request as there are plenty of template editors discussing this so you don't need an uninvolved template editor to implement. * Pppery * _{it has begun...} 20:31, 30 March 2025 (UTC)

• In general I am not opposed to adding an extra search function for finding subst-only templates, but I also agree with Gonnym that the proposed implementation is a bit unnecessary; we don't need to be looking for an entire commented-out template name, just the template name itself. Yes, there might be some false positives (e.g. someone just typing "uw-tpv4" like we are doing here) but the point of the tfdlinks is to show general/broad usage, not be super-specific. For example, swapping namespaces once the search is pulled up is pretty trivial, so I don't really see the need for extra params. I guess my point is that it's reduced overhead for maintenance and updating if we just add a single line of a simple URL to the main template, rather than relying on a secondary template to do so. Primefac (talk) 11:05, 5 April 2025 (UTC)

  Not opposed to adding a link directly to Module:Tfd links rather than employing a separate template, and I am okay just searching for the template name (as opposed to the longer string) if that doesn't include too many false positives in the result set (and even if so, it's probably manageable). As far as what is or isn't trivial for users to do in search, this links up with the earlier comment about "democratization": I wonder how many users even know about the namespace checkboxes, and that if they start off with a regular search for "uw-tpv4" in the search box and then click the advanced link, that they can refine the resulting zero-result search page by switching namespaces via a checkbox; my guess is pretty few. Perhaps something to look into, or maybe a user plugged into wmf research like WhatamIdoing might have some data on that. One purpose of the template is to finesse that, and give them results immediately; a module upgrade could do that as well.

Also, I had in mind to save Tfd users a wasted click by not rendering the link (or rendering it grayed out, unlinked) if there are no results but I haven't sandboxed that yet, so if we do implement the functionality in the module without a template, I would like to see that included as well, if possible; however, if that complicates implementation too much, just having a basic link there to find id-bearing, substed templates (or just any mentions, even at some cost in false +) would be a boon to Tfd users trying to make a more evidence-based decision. Mathglot (talk) 16:43, 5 April 2025 (UTC)

I have seen no research on that specifically. However, in general, if it's behind a collapsed box (and this sort of is), then most people won't know about it. That feature should be known to the typical power user but not to ordinary users (e.g., readers). WhatamIdoing (talk) 21:17, 5 April 2025 (UTC)

Is this the right place to discuss splitting templates?

There are many navboxes that are absurdly long or dense to where it would be better served as a few different navboxes, and I'd like to get some of them split up into multiple smaller navboxes, but it's unclear how this should be discussed since they affect so many articles. Thebiguglyalien (talk) 🛸 17:02, 11 April 2025 (UTC)

I believe there is a specific place to discuss merging templates, but I could not find anything when it comes to splitting them. I simply sent messages to those I believed to be most familiar with the topic. Hotdog with ketchup (talk) 21:16, 11 April 2025 (UTC)

The first place to discuss a split is on the template's talk page. If there is little/no discussion, and/or no consensus can be reached, then TFD would be an appropriate venue for wider discussion. Primefac (talk) 00:12, 12 April 2025 (UTC)

For starters, imho it always helps a discussion if you link a few examples at the outset, especially when you OP starts out, "There are many <Wikipedia thingies> that are <undesirable attribute>...", as it's hard to know if you have something specific in mind or it's just a general gripe, and also it helps tune responders tune into the same wavelength you are on.

Additionally, you pose one problematic attribute (long/dense) and one solution (split them) whereas in reality, there may be many other solutions you have not considered (better group/label hierarchy, child navboxes, selective collapse, compound navboxes, create and/or link to list page or outline page) and so on. You increase the likelihood of getting a satisfactory response for your situation if you describe the underlying issue that prompted your question, rather than your suggested fix (split), because that tends to limit responses to "How do I split this" rather than whatever the underlying issue is.

Is it that it is hard to find a link in the box? Is the organization or order of the many links non-intuitive or arbitrary? Does it take too much vertical space and makes scrolling past it annoying? Does it take too long to load the page? Do you prefer succinct lists as one tends to see in a sidebar on the right side of the page rather than in a navbox? Do you hate navboxes and wish they would all be suppressed when you look at a page? Are you trying to track down where a particular source string resides using Advanced search, and the voluminous navboxes give you too many search results to pages that only transclude the string but do not contain it? Is the font too small and your eyes glaze over when there are more than a few links?

All of these are legitimate issues and might all be [overly] summarized as, "navbox too long", but they all have different focus and a different range of solutions that may apply. Describing your pain points regarding navboxes might help you get to a solution easier and faster. Mathglot (talk) 00:23, 13 April 2025 (UTC)

I want to split them. I want this because they are too long. Examples: {{United States topics}}, {{Fascism}}, {{Russian invasion of Ukraine}}. Thebiguglyalien (talk) 🛸 00:35, 13 April 2025 (UTC)

At the risk of repetition, what does "too long" feel like to you, or where does it impede usage of the encyclopedia, or make some article worse by including the navbox, or cause some other negative effect? Personally, I do not think they are "too long" but I suspect we mean different things by that expression. As one approach, I am the kind of person that occasionally likes to browse or read a printed dictionary (or an online one) stopping at some of the unfamiliar terms to read them in detail. A bunch of editors spent considerable thought and effort into designing {{Russian invasion of Ukraine}}, and it's a great one-stop shop of topics with comprehensive coverage of the issue; I don't know where else one could find a list like that to quickly access almost any aspect of the invasion; a tremendous time-saver for someone interested in a deep dive. Finding a navbox such as that one or the others you linked feels to me like hitting the jackpot, with all those yummy unfamiliar topics to learn about, and maybe improve, as well. So to me, they are a boon. It takes a little longer to scroll past, but that is a minor inconvenience to me. Knowing where your discomfort lies with the length of {{United States topics}} might lead to a solution you didn't expect. Mathglot (talk) 00:48, 13 April 2025 (UTC)

The following discussions need to be closed

It's been a long time since many of the discussions have been abandoned. Here are the discussions that I think we should close immediately:

• Template:Country data Cabinda
• Template:Interwiki link
• Template:Highway detail hatnote
• Template:Aubrey Plaza
• Template:Michael B. Jordan
• Template:Wikicite

2600:1700:6180:6290:28F7:14C:F72F:9A57 (talk) 09:43, 11 July 2025 (UTC)

We have WP:TFD/O; they will get looked at in due time. DEADLINE and suchlike. That being said, it is on my list of things to do this weekend. Primefac (talk) 12:51, 12 July 2025 (UTC)

Something missing

Wikipedia:Templates_for_discussion/Log/2025_June_19#Template:Controversial This discussion is closed, but is has no "The result of the discussion was". Gråbergs Gråa Sång (talk) 09:08, 6 August 2025 (UTC)

For some reason an IP closed it. No idea how that is ok. Gonnym (talk) 09:16, 6 August 2025 (UTC)

It's not, I've reverted. Granted, it might still get closed with no consensus (I've not managed to close it yet due to time issues) but it should be done by someone with demonstrable experience in this field. Primefac (talk) 09:20, 6 August 2025 (UTC)

Thanks! Gråbergs Gråa Sång (talk) 09:23, 6 August 2025 (UTC)

Need helping constructing a TFD

So I want to tag 2 templates into a 3rd one. But don't know the exact options in twinkle to tag which templates to merge into navdoc. The merge option in beffudling me. Don't want to accidentally start TFD on the same thing. That's why I am asking here first.

This is what I have thus far: "{{Navdoc}} contains information about both {{check completeness of transclusions}} and {{collapsible option}}. Proposing to merge the latter two into navdoc. ~~~~ 8rz (talk) 18:07, 27 September 2025 (UTC)

For the sake of clarity I will call the templates nominated for deletion/merging the "nominated" templates, and the target/end template the "target" template. There are a few ways to nominate multiple pages for merging:

1. Use Twinkle on one nominated template (selecting the target as the target) and manually add the TFD tags to the other nominated template(s)
2. Use Twinkle to nominate each nominated template and then manually merge the sections on the TFD log page. The target template will need cleanup for the multiple TFD tags
3. Manually nominate all templates and manually create the log entry.

I have used both #1 and #2 about equally, though if I am doing a dozen or so similar templates I'll usually go for #1 via AWB to avoid too much clutter on the Log page. #2 is really best if you're only nominating two or three templates. Primefac (talk) 13:21, 28 September 2025 (UTC)

I'd've used AWB too for #1 but I am awaiting for my perm rights approved at WP:PERM/AWB. 8rz (talk) 14:23, 28 September 2025 (UTC)

If you're only nominating two templates, AWB would be rather useless. Primefac (talk) 23:54, 28 September 2025 (UTC)

Comments repeatedly refusing to meet nominator arguments

I'm getting frustrated by the inability of this process to actually generate discussion.

Have a look at Wikipedia:Templates for discussion/Log/2025 October 13#Template:Uw-archive. To me, the comments basically boil down to "I like it, so I !vote keep" with zero attempt to meet my argument: since specific numbers are no longer part of the guideline, and indeed, the guideline leaves user talk size entirely up to the discretion of the user, it is inappropriate to have a user warning template: the user have not done anything wrong by having a large user talk page.

We can still politely ask them to reduce the size of their user page, and indeed we have a template for that. This TfD is making the point that there should be no user warning template (which implies "officialness" or that the user has done something inappropriate or against guidelines).

But no responder have actually engaged with this point. What is the value of a !vote if they don't even try to base their comment on the actual circumstances? I could absolutely respect a comment that provided compelling arguments against any or all parts of the above chain of logic. A commenter that engages with my above line of reasoning and tells us where or how they think it is wrong, sure. But no, nothing.

If this TfD doesn't generate any discussion of substance and yet is closed as keep, I don't know what I'm doing, except I'm doing it wrong. Why do I feel like my arguments as nom are completely and utterly ignored? Any advice appreciated. CapnZapp (talk) 20:37, 13 October 2025 (UTC)

Speaking as a TFD closer, I weigh the arguments in a discussion against our policies, guidelines, and norms. I have certainly closed discussions against the majority when their arguments were not as sound as those of the minority, though that is fairly rare and usually only in really lengthy TFDs. That being said, overruling unanimous opposition would mean very weak arguments against the nomination (e.g. every !vote was something found in WP:ATA). I don't think a nominator has done anything "wrong" if their nomination fails, just that their opinions differ from the majority. Primefac (talk) 23:29, 13 October 2025 (UTC)

Unless I'm blind the basic "arguing something not relevant to the nomination at hand" isn't in WP:ATA. I'm baffled by this. How does it benefit Wikipedia if comments aren't discounted when arguments are based on misunderstanding the rationale for a nomination? Or when arguments are clearly made by someone who dislikes a settled and stable guideline change (and that change is specifically the impetus for the nomination)? CapnZapp (talk) 21:31, 18 October 2025 (UTC)

Ignore the bit about ATA, I was trying to give an example. I did say that poor arguments are often discounted (though that does not mean "ignored completely"). Primefac (talk) 12:29, 19 October 2025 (UTC)

Okay, fair enuff'. Awaiting the outcome of the discussion (it's three days overdue). CapnZapp (talk) 10:02, 23 October 2025 (UTC)

Template:Pelé series recreated yet again

Template:Pelé series was deleted at TfD, was then deleted again at TfD, and was recreated yet again. Can an admin do something here? Gonnym (talk) 07:48, 11 November 2025 (UTC)

@Gonnym: I have tagged the page for CSD and SALTING. Also reverted the various edits by the creator that re-added it to articles. I would suggest you WP:ANI the user though... If you do, ping me and I'll endorse. --Zackmann (^{Talk to me}/_{What I been doing}) 08:11, 11 November 2025 (UTC)

Page has been deleted and salted. Primefac (talk) 09:42, 11 November 2025 (UTC)

Amendment proposal

As mentioned here, I would like to propose an amendment to the third point of our rules. The current text reads:

The template is not used, either directly or by template substitution (the latter cannot be concluded from the absence of backlinks), and has no likelihood of being used.

I would like to change it to (addition in yellow):

After at least six months since its creation, the template is not used, either directly or by template substitution (the latter cannot be concluded from the absence of backlinks), and has no likelihood of being used.

--Grufo (talk) 08:10, 23 November 2025 (UTC)

No. If you can't use a template the moment you created it, then why did you create it? A template (and module) should be created to fill a need. If you want to practice template and lua code, do that in your own sandbox. Gonnym (talk) 11:17, 23 November 2025 (UTC)

Hi Gonnym. The amendment does not contrast what you think should be a good reason for creating a template; it only says that you can judge whether a template meets your criteria not before six months since its creation. There can be many reasons why a template has few transclusions the moment is created: it might come from another Wikipedia (in another language), where it is used massively although here older (and less efficient) habits have their own inertia, or it might come from a need expressed in a talk page, and so on. In any case, the time window we set has nothing to do with the criteria we then follow. --Grufo (talk) 01:46, 24 November 2025 (UTC)

None of your examples above are valid in my opinion. I completely oppose editors importing templates from other wikis and not doing anything with them. en.wiki isn't a code repository. If you think it is useful, use it. If you can't find a use for it, then it isn't useful. Gonnym (talk) 07:00, 24 November 2025 (UTC)

Again, this proposal is not about what we consider to be valid reasons delete a template; this proposal only concerns the minimal time window we request before enforcing point #3. --Grufo (talk) 14:51, 24 November 2025 (UTC)

No, this is only unnecessary delay. The Banner talk 01:52, 24 November 2025 (UTC)

Well, there is a necessity, which is that of not impeding, by nominating a template for deletion prematurely, potential large usage, simply because the template is not yet visible, or has to fight with old albeit less efficient habits, and so on. On the other hand, I don't see the necessity for not keeping a template, even if it will never be used, for six months more: What damage does that do exactly? And “a delay” towards what goal? --Grufo (talk) 01:58, 24 November 2025 (UTC)

Oppose this is clearly an editor who is unhappy that their work is being challenged for deletion and wants to make that process harder. This barely dignifies a response but I will voice my emphatic opposition to this. Zackmann (^{Talk to me}/_{What I been doing}) 07:41, 24 November 2025 (UTC)

Not sure what you mean by “my work”, but the context that inspired this proposal is not hidden (and in general it is a good thing when a dysfunctional aspect of a process is discovered in action). A good proposal, however, can be inspired even by a rolling stone. What is your opinion on the amendment's content and on what grounds do you oppose it? --Grufo (talk) 14:44, 24 November 2025 (UTC)

You have dumped dozens of templates that are used on other wikis into the english wiki. Most of those templates are unused, unhelpful and unneeded. Now that there are being deleted, you are very clearly upset and are trying to impose new rules to make it harder to delete those templates that you claim will someday be useful. As I pretty clearly stated, I 100% oppose the amendment's content. Zackmann (^{Talk to me}/_{What I been doing}) 15:58, 24 November 2025 (UTC)

I am not sure why you keep mentioning your taste concerning the templates I created. Here we are discussing an amendment to the rules. On what ground do you oppose the amendment? What makes you think that a time window of six months is a bad idea? --Grufo (talk) 16:44, 24 November 2025 (UTC)

I wouldn't be opposed to a one-month period for reasonable-looking templates to avoid being bitey toward template creators, but anything longer clutters up unused template reports and ties the hands of editors working to eliminate unused cruft from the encyclopedia. The speedy criteria for test pages would still apply, of course, so a template with the content of "Bill Wilson is stupid" would not be subject to any such time-related generosity. Six months is far too long, though. If you're going to create something in Template space (rather than your User space or Draft space), put it to use. – Jonesey95 (talk) 16:57, 24 November 2025 (UTC)

One month is definitely better than nothing. It would also discourage people from following newly-created templates only for the sake of nominating them for deletion. I still think that six months would be a better period for lowering down any rush though. --Grufo (talk) 18:03, 24 November 2025 (UTC)

That is a hefty accusation... Do you have actual instances of that happening? Zackmann (^{Talk to me}/_{What I been doing}) 18:05, 24 November 2025 (UTC)

Funny you see an accusation there. --Grufo (talk) 18:21, 24 November 2025 (UTC)

I oppose any period. I've seen admins revert your speedy "test pages" on the grounds that they aren't test pages more than once. I can only talk about myself here, but my thought process when I look at newly unused templates is this ->

Does it look like it duplicates an existing template? Is it a navbox full of red links? Does it violates guidelines or policies? Is it a single-use template? Is it article content in a template? And finally, a more opinion-based one, would I never want it being used anywhere? -> if the answer to one of these is yes, I send it to TfD. I don't see anyway that a one month period would change my opinion, which is why we have TfD and I don't decide what stays or not (as clearly not everything I nominated was deleted).

On the other hand, I don't nominate templates right away where I see some kind of potential to them. There are unused templates such as Template:Flag football men's national team flag which were created a year and a half ago and has not been sent. Gonnym (talk) 12:28, 25 November 2025 (UTC)

@Gonnym: I have read this only now: What are Jonesey95's “speedy ‘test pages’”? --Grufo (talk) 05:38, 26 November 2025 (UTC)

Templates that they tagged under WP:G2 but were declined. Some templates aren't exactly a test, but they are basically one minor step above. Some admins find that enough of a distinction. TfD usually does not. Gonnym (talk) 09:50, 26 November 2025 (UTC)

Thank you for the explanation. --Grufo (talk) 12:02, 26 November 2025 (UTC)

@Gonnym: “On the other hand, I don't nominate templates right away where I see some kind of potential to them”: This point opens an interesting reflection, I think. Imagine you see a template and you don't know anything about it, except for what it does. Now there are two possibilities:

1. You see a potential for it
2. You don't see a potential for it

In the first case you cannot nominate it for deletion, point #3 already discourages you to do so. In the second scenario you check if it has transclusions; in our ideal example you see it has many, and you realize that you were wrong, you hadn't thought about that. This means that we can be wrong, in general, when we assess whether something can have use cases. Don't you think then that a time window of six months can only be a useful check against our subjective judgement? Especially given the fact that some templates, if the author did not link them around enough, take ages even just to be discovered? --Grufo (talk) 11:36, 27 November 2025 (UTC)

(edit conflict) We already have and has no likelyhood of being used. We do not need to add a six month time limit. As Gonnym stated, If you can't use a template the moment you created it, then why did you create it.

As for Jonesey95's idea of a 1 month, I just don't think it is necessary. We seldom see nominations of brand new templates that have a likelyhood of being used. Just because a template is only 2 weeks old, shouldn't prevent us from taking it to TFD if it is a terrible template. This recent example comes to mind.

If a relatively new template DOES end up at TFD, there is nothing to stop a creator (or another editor) from saying "Hold up, I'm still working on this and plan to use it". I have NEVER seen that be an issue that would require a rule barring nominating templates under 30 days old.

I will also point out again that the only reason we are discussing this is because Grufo has bulk imported templates from other wikis that have been sitting unused (in some cases) for months. Now those templates are being taken to TFD and they want to prevent that from happening by imposing a 6 month restriction. Zackmann (^{Talk to me}/_{What I been doing}) 17:04, 24 November 2025 (UTC)

Maybe a little refresh will be helpful. The cause (not the reason) we are discussing this is because a template I created has been nominated for deletion only two weeks after being created, without any argument concerning its code, its usability, its benefits, and so on, and only mentioning that after two weeks it had few transclusions. That appeared to be intrinsically flawed, and a general rule had to be introduced. After I proposed such a rule—I don't know exactly why—you decided to go after every template I created. --Grufo (talk) 18:15, 24 November 2025 (UTC)

Because those tempaltes do not have likely hood of being used, are redundant to other templates and are generally not useful or helpful. You are bulk importing templates from other wikis (see, for example, the edit summary for the creation of Template:Purge icon where you specifically stated Import template from Latin Wikipedia). Then you are disappointed when those templates are nominated for deletion. Additionally you are reporting other FAR more experienced users such as Gonnym for made up policy violations when you don't get your way.

I have said all I intend to say on this mater. If consensus is to impose a 1 month (or other timeframe) restriction on deleting new templates, I will of course abide by it. But so far all I see is an editor throwing a temper tantrum because they are not getting their way. Lashing out at other editors by threatening to report them (as you did to me when I called you out on your talk page), filing bogus ANI reports (as you did to Gonnym and generally acting in very bad faith towards other editors.

Final statement I will make on this is that I think it is unnecessary to impose such a restriction, would allow the propagation of bad code and prevent the removal of badly designed templates based on some arbitrary timeframe. Zackmann (^{Talk to me}/_{What I been doing}) 18:30, 24 November 2025 (UTC)

This proposal is not going to be accepted. People create articles which are quickly removed all the time. There won't be an exception for templates. If someone identifies a reason for what they are doing—a reason related to improving enwiki—and if that reason is accepted, then deletions either won't occur or deletion attempts won't succeed. However, if an editor cannot identify a reason for creating Template:Whatever, before creating the template, it should be deleted. The community has seen many cases where someone tries to change the rules when they don't get a result they want. Such attempts never work. Johnuniq (talk) 01:04, 25 November 2025 (UTC)

This is not a valid argument. Our point #3 does not apply to articles; articles are not deleted because “they are not used, or have no likelihood of being used”. Articles are deleted for a bunch of reasons, which would also apply to templates (as Jonesey95 mentioned, if a template wrote “Bill Wilson is stupid”, it would be deleted immediately). As for the fatalistic part, I am not sure what you mean. I am pretty sure though that most of us here on Wikipedia did get very often what we wanted when we were right. --Grufo (talk) 03:14, 25 November 2025 (UTC)

Telling an admin their argument is invalid... yea that seems like a good strategy... Zackmann (^{Talk to me}/_{What I been doing}) 03:15, 25 November 2025 (UTC)

@Zackmann08: Strategy to what end? --Grufo (talk) 03:18, 25 November 2025 (UTC)

Your policy just isn't gonna happen. Everyone who has commented opposes you pushing your ideas, here, at TFD and on policy pages. Just let it go and quit BLUDGEONING the process. It is just exhausting. Zackmann (^{Talk to me}/_{What I been doing}) 03:28, 25 November 2025 (UTC)

The essence of templates is that they are used often (or at least multiple times). Therefore unused templates can be deleted. The Banner talk 14:20, 25 November 2025 (UTC)

Not really. The essence of templates is placing some wikitext elsewhere. Single-transclusion templates are perfectly fine, as long as there are good reasons to place that wikitext elsewere. Even zero-transclusion templates can be fine in some cases (a {{Delete this page}} ideal template is a perfect example). In any case, I repeat this again and again, this discussion does not affect the criteria we follow to judge whether a template qualifies for deletion or not, it only proposes a time window that must be granted before enforcing point #3. --Grufo (talk) 03:53, 26 November 2025 (UTC)

So far you have failed to reach consensus for your proposal. The Banner talk 14:04, 26 November 2025 (UTC)

Hoping to move this discussion forward, I want to present a concrete example. The {{Show SVG}} template was created on 19th October; on 24th November it was already nominated for deletion (then relisted, then preserved). From day one it had transclusions, but they were considered insufficient. Yet some templates might require non-trivial skills to be used in their full potential. We got very lucky to have a user who did a very complex job with {{Chemical reaction/arrow}} in such a short time (27th November)—which was the reason the template was preserved. But do we always want to rely on good luck? --Grufo (talk) 15:36, 19 December 2025 (UTC)

We don't need luck. We need template creators to know what they create and for what purpose. Oppose any change you suggest. Gonnym (talk) 18:51, 19 December 2025 (UTC)

“Oppose any change you suggest”: What if I proposed that you oppose any change I suggest? --Grufo (talk) 20:28, 19 December 2025 (UTC)

Let's try to stay on-track. Sarcasm and snark aren't helping things. I think you've both said largely what you want to say. Primefac (talk) 23:30, 19 December 2025 (UTC)

Alright. Back on track then. Gonnym said “We need template creators to know what they create and for what purpose.”. Grufo answers: Or maybe, instead, we need nominators and voters who understand what they have in front, and by default have the humility to presume that template creators might have had everything clear from day one? Or maybe, when we lack that, we could try to reduce these mistakes by exploiting a time window of six months? In my short time at TfD I have seen quite surreal things, like the nomination of {{Not a forum}}—to be clear: I never had anything to do with that template—on the ground that it would allegedly duplicate {{Talk header}} in warning that talk pages are not forums: even after CapnZapp's comment showed that such a premise was false, people kept writing “Delete per nom” or “Delete very redundant with talk header”. That is simply crazy. The proposed time window will not affect {{Not a forum}} (that template is very old); yet maybe—just maybe—by discouraging people from paying attention to our recent changes in search for templates to nominate per point #3, it will improve the quality of these discussions overall. Once again: if someone creates a broken template, that will still be deleted on day one per this proposal (so there will always be good reasons to monitor our recent changes). --Grufo (talk) 03:16, 20 December 2025 (UTC)

Promote new template

Hi all, how do I promote a new template (temporary name) {{User:The Equalizer/sandbox/Template:Capital Distance3}} and get discussion, suggestions etc. Regs, The Equalizer (talk) 17:20, 23 December 2025 (UTC)

First identify where the template would be used. If it's missing, then you should ask yourself why was it missing. Sometimes a functionally is missing because no one thought of adding it, other times, it's missing because the community does not want it. If you think this is wanted, then post on the talk pages of the pages where this could be used (template talk pages, project talk pages, article talk page, etc.) Gonnym (talk) 18:19, 23 December 2025 (UTC)

@Gonnym: I suspect this relates to Template talk:Infobox UK place#Conversion to use Infobox settlement as a wrapper and Template talk:Infobox settlement#Capital distance measure, also Template talk:Infobox settlement#wrapping of Infobox UK place (where you commented). --Redrose64 🦌 (talk) 17:17, 25 December 2025 (UTC)

Category:Editnotices whose targets are redirects

Small maintenance category (~200 pages). I've started cleaning up the PIA notices, some of it is post move cleanup, others are from merges/deletions leaving excess notices effectively. I've upcycled some of these to re-target them, but I've run out of accessible room :)

As far as I understand G8 doesn't cover this as the pages the templates target aren't non-existent (they remain redirects), which is ironic as I've been cleaning this up by suppressing redirects, as is the done etiquette to avoid contributing to this maintenance category. There are others I have tagged as |redirect=yes where there is significant history and page protection, in order to remove them from this maintenance category. This is also something that could do with clarification. Either way, I'm hoping we don't need a WP:T6 to clean these up do we? It looks like a waste of time taking these to WP:TfD as ideally they could just be deleted as G6/G8? Pinging a few admins, @Extraordinary Writ (cat editor) @SilverLocust @Asilvering (I moved some of your templates so thought you might have some insight) CNC (talk) 16:07, 24 December 2025 (UTC)

I've occasionally fixed some of the pages in the category. ProcBot unfortunately hasn't been moving them since March (see also notices on inactive bot operator's talk page). Redirect suppression is per WP:PMRC#8 (as WP:G6) rather than just etiquette. When an editnotice can't be resynced to the right page because it already has an identical editnotice added after a move, I would tend to think one of them can be G6'd by analogy to PMRC#8 (if the newer one, deleting it to make way for the move), but I think that would likely seem weird or unnecessary to an admin reviewing a {{db-g6}} request. When you can't delete the editnotice yourself, it might be easier to just use redirect=yes (assuming the editnotice can apply to the redirect, which is the case for PIA editnotices). On that clarification point, I think "instances that should not be cleaned up" mainly refers to the following sentence's "editnotice meant specifically for a redirect page" that should instead be removed from the tracking category via redirect=yes. ~ Jenson (SilverLocust 💬) 17:07, 24 December 2025 (UTC)

Thanks for the context, the lack of ProcBot explains a lot of it I imagine. I've made this edit in an attempt to clarify things, someone can revert if they disagree with that interpretation. In hindsight I think it makes sense to tag as redirect to remove from category in cases where there is an editnotice where intended already, as part of the sorting process. Although eligble for G6 on the face of it, I'm not really seeing much benefit of nominating these for deletion even if it applies. The important aspect of the category is identifying where editnotices need moving to that have been left behind, unless I'm mistaken? CNC (talk) 17:34, 24 December 2025 (UTC)

Courtesy ping: LaundryPizza03 as you appear to be active with nominations in or around that category? Either way I'm not sure these templates need full discussions, G6 or removed from category would be easier. CNC (talk) 19:39, 24 December 2025 (UTC)

It's not clear if CSD applies, and most of the nominated editnotices are identical to their targets' editnotices. –LaundryPizza03 (dc̄) 19:45, 24 December 2025 (UTC)

(edit conflict) You might get pushback on using G6 from the people who support Wikipedia:What G6 is not. The justification for WP:PMRC#8 linking to WP:CSD#G6 is presumably that the left-behind redirect would be "redirects created by moving away from a title that was obviously unintended", although I could see them pushing back on that too 🤷. Anomie⚔ 19:47, 24 December 2025 (UTC)

Sorry, no insight from me I'm afraid. -- asilvering (talk) 20:00, 24 December 2025 (UTC)

I think your best options here are probably something like this:

• Add |redirect=yes if the notice still makes sense for the redirect, and wouldn't for the redirect's target.
• If the redirect target doesn't have an editnotice, move it and apply WP:PMRC#8.
• If the redirect target has an editnotice, but it's a copy-and-paste "move" of the redirect's notice, you could do a few things:
  • G6 the target's notice (per "Deleting redirects or other pages which prevent page moves") and then move as above.
  • WP:HISTMERGE, and then delete the left-behind redirect per WP:PMRC#8 (and probably cite that directly, not G6).
  • Just redirect the redirect's editnotice, and leave it there for history.
• For other cases, you might still justify a G6 of the target's notice (per "Deleting redirects or other pages which prevent page moves") and then move as above, if the old notice is better.
• Failing that, you might just redirect the redirect's editnotice to the target's and leave it for history.
• Failing that, TFD is probably the way to go. No CSD really applies. Or I supposed you could IAR-delete it if you really want.

HTH. Anomie⚔ 20:04, 24 December 2025 (UTC)

Maybe comment on the actual TfD's opened to date? –LaundryPizza03 (dc̄) 20:16, 24 December 2025 (UTC)

Thanks, that's a good guide. Though as a WP:Page mover without WP:Page deleter rights it's somewhat lacking. Aside from WP:PMRC#8 and upcycling when possible, I'm left with TfD by looks of it? CNC (talk) 20:28, 24 December 2025 (UTC)

You could WP:RMT the ones that would need G6ing. Anomie⚔ 20:33, 24 December 2025 (UTC)

Interesting idea. You mean as overwriting or something? For example with Template:Editnotices/Page/Israeli airstrikes on the Gaza Strip as an RMTR to Template:Editnotices/Page/Israeli bombing of the Gaza Strip or am I misunderstanding? Duplicate notices are most of the PIA ones left now if not mistaken. CNC (talk) 20:42, 24 December 2025 (UTC)

Yes. Although that particular example might be hard to justify as needing a move, since both were created at the same time with identical content rather than it being a copy-paste move of the edit notice after the article was renamed. Too bad no one noticed that one on 2025-11-29 when G8 would have clearly applied, before the redirect was created on the 30th. Now, depending on the admin who reviews it, you might get away with a post-hoc G8 or you might not. Anomie⚔ 20:57, 24 December 2025 (UTC)

In all honesty RMTR doesn't sound much better. CNC (talk) 22:15, 24 December 2025 (UTC)

Can you help me condense all the TfD's? Most of them are just an editnotice on a redirect that is identical to one on the redirect target, and a user on my talk page recommended merging most of them. –LaundryPizza03 (dc̄) 00:13, 25 December 2025 (UTC)

Yeah, two seconds. Primefac (talk) 01:10, 25 December 2025 (UTC)

I could only combine the ones that were identical and didn't have any responses, so there are a bunch that aren't merged. Primefac (talk) 01:23, 25 December 2025 (UTC)

@LaundryPizza03: For future ref, WP:TFDHOWTO step 2, the part about multiple templates. --Redrose64 🦌 (talk) 10:53, 26 December 2025 (UTC)

Are the three TFD steps out of order?

I have never noticed this before, since I always use Twinkle, which does all three steps at WP:TFDHOWTO at essentially the same time. An editor asked me to do Step 1 (tag the template with the TFD notice), but I balked, because I knew that the TFD notice links to the TFD discussion section. The TFD discussion section is created in Step 2. Why should we tag the template, which creates a link to the TFD discussion section, before the TFD discussion section exists? What am I missing? – Jonesey95 (talk) 05:52, 13 January 2026 (UTC)

Based on my read, it looks like it often is not a problem as the header is template name so it tips automatically generated. But that is not always the case. So I agree this should be changed... Zackmann (^{Talk to me}/_{What I been doing}) 06:16, 13 January 2026 (UTC)

All of the WP:XFD processes follow the same order: tag the page that is to be deleted/discussed first, then create the discussion, then notify others. --Redrose64 🌹 (talk) 06:51, 14 January 2026 (UTC)

Concur with Redrose64 about matching other processes. I will note that AFD (the "primary" deletion route) has the deletion discussion on its own page, meaning it is a bit more awkward to create the deletion discussion first (since the AFD notification automatically creates a redlink and prompts to create said page). However, I do not think this discrepancy (i.e. TFD has a daily log of all discussions) is enough to merit flipping the order. If a template is tagged without being nominated, the tag can always be removed until such time that there is one. Primefac (talk) 11:04, 14 January 2026 (UTC)

I would also note that if a user is able to perform Step 1 themselves, Step 2 is not going to be performed instantaneously anyway since they still have to navigate to the log, edit the page, add text etc. A slight delay in Step 2 is to be expected for manual nominations. Primefac (talk) 11:10, 14 January 2026 (UTC)

The AFD instructions make a bit more sense, since there is preloaded text behind the link that helps you create the AFD page. TFD has no such preloaded text. – Jonesey95 (talk) 14:47, 14 January 2026 (UTC)

If you have never nominated a template for deletion or used Twinkle before, you might want to do it manually to avoid making mistakes. For more experienced editors, using Twinkle is recommended, as it automates some of these steps. I know this is kinda off topix but I think this is completly backwards at this point. Twinkle is reliable and easy to use as well as a gadget making installation trivial. I would 100% recommend that over manual nominations assuming you are auto confirmed. Trialpears (talk) 12:41, 14 January 2026 (UTC)

I definitely agree with this view. Using Twinkle is the way to avoid making mistakes. – Jonesey95 (talk) 14:47, 14 January 2026 (UTC)

Agreed; even for complex nominations it's often easier to start with Twinkle (e.g. nominate the first template in a batch) and then edit the log page to add additional template(s). Primefac (talk) 17:14, 14 January 2026 (UTC)

Category:Microformat (uF) message templates

Couldn't think of a good place to start this discussion so thought I'd try here... Considering TFDing this entire category. These seem like a slew of templates that were once helpful when they were created in 2008, but no longer are helpful with the upgrades that have happened in the last 15+ tears. They just clutter documentation pages and are used very inconsistently. Before I nominate them, am I missing something? Do these serve some purpose that I'm not seeing? Zackmann (^{Talk to me}/_{What I been doing}) 20:39, 18 January 2026 (UTC)

I think Pigsonthewing was the microformats guy and probably have insights in if this is a good idea. To be honest I still don't really know what a microformat is but that might just be a testament to my ignorance. Trialpears (talk) 01:15, 19 January 2026 (UTC)

@Pigsonthewing: would love to hear your thoughts! Are these templates still useful in someway that I don't know/understand? Zackmann (^{Talk to me}/_{What I been doing}) 02:34, 19 January 2026 (UTC)

Thank you for the ping. For background, please see Wikipedia:WikiProject Microformats and Microformat.

So long as our templates include markup (in the form of HTML classes) to make their contents machine readable as microformats (and a great many templates do), these documentation templates are needed to advise people about those microformat classes and prevent their inadvertent removal, renaming or relocation, which will break those microformats.

The claim "no longer are helpful with the upgrades that have happened in the last 15+ tears [sic; but funny ;-) ]" seems to be made without justification or basis in fact.

I occasionally see people break our microformats in the manners described above, through not having read, or ignoring, these templates. This requires work to fix them. If these templates are not used, then the frequency of damage and the work required to remedy it will obviously increase considerably.

If there is an issue that these templates "are used very inconsistently", this can be and should be fixed by making their usage consistent. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:59, 19 January 2026 (UTC)

Andy, thanks for the explanation. Sorry for my dumb typo ( Facepalm ) but glad it gave you a laugh.

I guess i just misunderstood what microformats were! I won't pursue this further. Zackmann (^{Talk to me}/_{What I been doing}) 07:00, 20 January 2026 (UTC)

Backlog at "Old discussions"

Some of the entries in "Old discussions" need to either be relisted or closed. Gonnym (talk) 11:01, 4 February 2026 (UTC)

Been travelling. Will get to them this weekend. Primefac (talk) 17:43, 6 February 2026 (UTC)