This is the
talk page for discussing improvements to the
High-use template. |
|
Archives:
1Auto-archiving period: 120 days
![]() |
![]() | To help centralise discussions and keep related topics together, Template talk:High-risk redirects here. |
![]() | Text has been copied to or from this page; see the list below. The source pages now serve to
provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below.
|
![]() |
Template:High-use is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
I think it might lead to less confusion if the wording of {{ high-use}} were slightly different on the /sandbox page. Here's how it reads today at {{ Citation needed}}:
This template is used on approximately 516,000 pages, or roughly 1% of all pages.
To avoid major disruption and server load, any changes should be tested in the template's /sandbox or /testcases subpages, or in your own user subpage. The tested changes can be added to this page in a single edit. Consider discussing changes on the talk page before implementing them.
I propose changing it to read like this on the sandbox page (I have included a couple of copy edits in green that should apply to both versions):
ThisThe live version of this template is used on approximately 516,000 pages, or roughly 1% of all pages.
To avoid major disruption and server load, any changes should be tested here in the template's /sandbox, and on theor/testcases subpages, or in your own user subpage. The tested changes can then be added tothis pagethe live template in a single edit. Consider discussing changes on the talk page before implementing them.
It might be best to move this portion of the discussion to the template's talk page for future reference. – Jonesey95 ( talk) 13:50, 11 November 2022 (UTC)
any changes should be tested here in the template's /sandbox, and on the /testcases ...warning (or some variant thereof). Then, because repeating the warning in the
{{
high use}}
~/sandbox page rendering is rather redundant, the {{high use}}
~/sandbox rendering reduces to something like this:
any changes should be tested here in the template's /sandbox, and on the /testcases ...message
The live version of this template sandbox is used on approximately <number> pages.
alter the sandbox notice. Are you suggesting making the text that only displays on the sandbox page to suggest using said sandbox? If so, this feels a little excessive, and like an unnecessary re-iteration of {{ High-use}}. If I'm missing something here I'm sorry, but I don't see what I'm meant to change in that regard. Aidan9382 ( talk) 11:34, 26 November 2022 (UTC)
{{
documentation}}
I was thinking of something like this to replace the ombox that currently appears on sandbox pages above the green documentation:![]() | This is the
template sandbox page for
Template:Cite book (
diff). To avoid major disruption and server load, any changes should be developed here in the template's /sandbox and tested on the /testcases subpage or in your own user subpage. |
{{
high-use}}
when it is rendered on sandbox pages, something like this:![]() | The live version of this template is used on 1,510,000+ pages. |
{{
high-use}}
mockup wording – forgot to mention that the count applies to the live template, not the sandbox template
{{
documentation}}
always renders an ombox above the documentation when the reader is looking at Template:<whatever>/sandbox (
sandboxNotice()) – also Module:<whatever>/sandbox. That should not change so here is no reason to bother with transclusion count criteria.use the damn testcaseswarning has been moved to the sandboxNotice() ombox, all that is needed for
{{
high-use}}
is as I've illustrated above (and <rant>
no percent of all pages; that is just meaningless</rant>
).![]() | This is the
template sandbox page for
Template:Sandbox (
diff). To avoid major disruption and server load, any changes should be developed here in the template's /sandbox and tested on the /testcases subpage ( create) or in your own user subpage. |
(Sorry, lost track of indents) Have to agree with DePiep; it just isn't necessary to distinguish "live" and the template page itself because of who gets to edit it. And I say this as a template editor who frequently uses <noinclude> and <includeonly> to provide users (mostly) and template editors (less so) with a view of how a template would look in real use, instead of displaying some square bracket/pipe/curly-brace/param-number grawlix at the top of the page. (Example: {{ Further ill}}; would look like complete crap without it). However in this case, it's just not needed; and it could even hurt, slightly, as the template editor would have to verify their intuition about what the "Live" was doing there. This is unnecessary, and doesn't clarify the situation for anyone, afaict, so I'm opposed to the change. Mathglot ( talk) 01:03, 4 December 2022 (UTC)
Will editors who have subscribed to this section please express any concerns so they may be addressed and we can perhaps go forward? Thank you all for your continued improvements! P.I. Ellsworth , ed. put'r there 12:40, 23 January 2023 (UTC)
Apparently I have to discuss this per WP:BRD. I was planning on making the % round to nearest tenth for months when I was reverted :(
I figured a way how to do this but someone disagreed with my change.
This meant my change was CONTROVERSIAL (I have to discuss this as an OOPS defense). I was planning to discuss this but I decided to be bold and do it.
So I was wondering, "should we change the % to round to the nearest tenth or add a parameter where you can set the number of decimal places to round to?" Sheep ( talk • he/him) 15:26, 23 February 2023 (UTC)
should we change the % to round to the nearest tenth or add a parameter where you can set the number of decimal places to round to?No.
count
value in the
percentage calculation that you modified comes from one of the modules listed at
Special:PrefixIndex/Module:Transclusion count/data/. If you look in any of those modules you will see that the values are listed as some multiple of 100. When the percentage is rendered by {{
high-use}}
, the percentage is qualified with the term 'roughly'. Rendering the percentage more precise than 1% is more-or-less meaningless.{{NUMBEROFPAGES}}
with {{NUMBEROFARTICLES}}
in the percentage calculation. I have said before that we should abandon the percentage calculation. My opinion on that score has not changed.![]() | This
edit request to
Module:High-use has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change:
Add the fragment #transclusions
to the link to
https://linkcount.toolforge.org. Adding the fragment highlights the row with transclusions when the link counts page is loaded, making it easier to identity the relevant numbers.
Diff: Sandbox edit
− | https://linkcount.toolforge. | + | https://linkcount.toolforge.org/?project=%s&page=%s#transclusions |
Example:
![]() | This template is used on approximately 12,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
– BrandonXLF ( talk) 09:32, 25 April 2024 (UTC)
{{High-use|demo=High-use}}
: ![]() | This template is used on approximately 12,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
When updating the documentation of {{citation needed}}, I realized that Template:Documentation doesn't have a link to Help:Template, which answers the question of 'what is a "template"?'. Wikilinking the word "Template" in the header "Template documentation" at the very top seems too disruptive (see Special:Diff/1231335346 and Template:Documentation/testcases#Documentation/sandbox). Template:Documentation does link to Wikipedia:Template documentation and Help:Transclusion, but at the very bottom, which is often not visible below the fold.
Newbies not familiar with templates are more likely to end up seeing documentation pages of high use templates. What if Template:High use linked to Help:Template and Wikipedia:Lua, as implemented in Special:Diff/1231332038? However, the banner text of Template:High use is aimed at implementors/editors of templates, who ought to be familiar with templates. — andrybak ( talk) 19:52, 27 June 2024 (UTC)
if
for "inline" vs "/doc subpage", which makes the separation of concerns between functions makeStartBoxLinksData
and renderStartBoxLinks
awkward. —
andrybak (
talk)
22:12, 27 June 2024 (UTC)This is the
talk page for discussing improvements to the
High-use template. |
|
Archives:
1Auto-archiving period: 120 days
![]() |
![]() | To help centralise discussions and keep related topics together, Template talk:High-risk redirects here. |
![]() | Text has been copied to or from this page; see the list below. The source pages now serve to
provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below.
|
![]() |
Template:High-use is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
I think it might lead to less confusion if the wording of {{ high-use}} were slightly different on the /sandbox page. Here's how it reads today at {{ Citation needed}}:
This template is used on approximately 516,000 pages, or roughly 1% of all pages.
To avoid major disruption and server load, any changes should be tested in the template's /sandbox or /testcases subpages, or in your own user subpage. The tested changes can be added to this page in a single edit. Consider discussing changes on the talk page before implementing them.
I propose changing it to read like this on the sandbox page (I have included a couple of copy edits in green that should apply to both versions):
ThisThe live version of this template is used on approximately 516,000 pages, or roughly 1% of all pages.
To avoid major disruption and server load, any changes should be tested here in the template's /sandbox, and on theor/testcases subpages, or in your own user subpage. The tested changes can then be added tothis pagethe live template in a single edit. Consider discussing changes on the talk page before implementing them.
It might be best to move this portion of the discussion to the template's talk page for future reference. – Jonesey95 ( talk) 13:50, 11 November 2022 (UTC)
any changes should be tested here in the template's /sandbox, and on the /testcases ...warning (or some variant thereof). Then, because repeating the warning in the
{{
high use}}
~/sandbox page rendering is rather redundant, the {{high use}}
~/sandbox rendering reduces to something like this:
any changes should be tested here in the template's /sandbox, and on the /testcases ...message
The live version of this template sandbox is used on approximately <number> pages.
alter the sandbox notice. Are you suggesting making the text that only displays on the sandbox page to suggest using said sandbox? If so, this feels a little excessive, and like an unnecessary re-iteration of {{ High-use}}. If I'm missing something here I'm sorry, but I don't see what I'm meant to change in that regard. Aidan9382 ( talk) 11:34, 26 November 2022 (UTC)
{{
documentation}}
I was thinking of something like this to replace the ombox that currently appears on sandbox pages above the green documentation:![]() | This is the
template sandbox page for
Template:Cite book (
diff). To avoid major disruption and server load, any changes should be developed here in the template's /sandbox and tested on the /testcases subpage or in your own user subpage. |
{{
high-use}}
when it is rendered on sandbox pages, something like this:![]() | The live version of this template is used on 1,510,000+ pages. |
{{
high-use}}
mockup wording – forgot to mention that the count applies to the live template, not the sandbox template
{{
documentation}}
always renders an ombox above the documentation when the reader is looking at Template:<whatever>/sandbox (
sandboxNotice()) – also Module:<whatever>/sandbox. That should not change so here is no reason to bother with transclusion count criteria.use the damn testcaseswarning has been moved to the sandboxNotice() ombox, all that is needed for
{{
high-use}}
is as I've illustrated above (and <rant>
no percent of all pages; that is just meaningless</rant>
).![]() | This is the
template sandbox page for
Template:Sandbox (
diff). To avoid major disruption and server load, any changes should be developed here in the template's /sandbox and tested on the /testcases subpage ( create) or in your own user subpage. |
(Sorry, lost track of indents) Have to agree with DePiep; it just isn't necessary to distinguish "live" and the template page itself because of who gets to edit it. And I say this as a template editor who frequently uses <noinclude> and <includeonly> to provide users (mostly) and template editors (less so) with a view of how a template would look in real use, instead of displaying some square bracket/pipe/curly-brace/param-number grawlix at the top of the page. (Example: {{ Further ill}}; would look like complete crap without it). However in this case, it's just not needed; and it could even hurt, slightly, as the template editor would have to verify their intuition about what the "Live" was doing there. This is unnecessary, and doesn't clarify the situation for anyone, afaict, so I'm opposed to the change. Mathglot ( talk) 01:03, 4 December 2022 (UTC)
Will editors who have subscribed to this section please express any concerns so they may be addressed and we can perhaps go forward? Thank you all for your continued improvements! P.I. Ellsworth , ed. put'r there 12:40, 23 January 2023 (UTC)
Apparently I have to discuss this per WP:BRD. I was planning on making the % round to nearest tenth for months when I was reverted :(
I figured a way how to do this but someone disagreed with my change.
This meant my change was CONTROVERSIAL (I have to discuss this as an OOPS defense). I was planning to discuss this but I decided to be bold and do it.
So I was wondering, "should we change the % to round to the nearest tenth or add a parameter where you can set the number of decimal places to round to?" Sheep ( talk • he/him) 15:26, 23 February 2023 (UTC)
should we change the % to round to the nearest tenth or add a parameter where you can set the number of decimal places to round to?No.
count
value in the
percentage calculation that you modified comes from one of the modules listed at
Special:PrefixIndex/Module:Transclusion count/data/. If you look in any of those modules you will see that the values are listed as some multiple of 100. When the percentage is rendered by {{
high-use}}
, the percentage is qualified with the term 'roughly'. Rendering the percentage more precise than 1% is more-or-less meaningless.{{NUMBEROFPAGES}}
with {{NUMBEROFARTICLES}}
in the percentage calculation. I have said before that we should abandon the percentage calculation. My opinion on that score has not changed.![]() | This
edit request to
Module:High-use has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change:
Add the fragment #transclusions
to the link to
https://linkcount.toolforge.org. Adding the fragment highlights the row with transclusions when the link counts page is loaded, making it easier to identity the relevant numbers.
Diff: Sandbox edit
− | https://linkcount.toolforge. | + | https://linkcount.toolforge.org/?project=%s&page=%s#transclusions |
Example:
![]() | This template is used on approximately 12,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
– BrandonXLF ( talk) 09:32, 25 April 2024 (UTC)
{{High-use|demo=High-use}}
: ![]() | This template is used on approximately 12,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
When updating the documentation of {{citation needed}}, I realized that Template:Documentation doesn't have a link to Help:Template, which answers the question of 'what is a "template"?'. Wikilinking the word "Template" in the header "Template documentation" at the very top seems too disruptive (see Special:Diff/1231335346 and Template:Documentation/testcases#Documentation/sandbox). Template:Documentation does link to Wikipedia:Template documentation and Help:Transclusion, but at the very bottom, which is often not visible below the fold.
Newbies not familiar with templates are more likely to end up seeing documentation pages of high use templates. What if Template:High use linked to Help:Template and Wikipedia:Lua, as implemented in Special:Diff/1231332038? However, the banner text of Template:High use is aimed at implementors/editors of templates, who ought to be familiar with templates. — andrybak ( talk) 19:52, 27 June 2024 (UTC)
if
for "inline" vs "/doc subpage", which makes the separation of concerns between functions makeStartBoxLinksData
and renderStartBoxLinks
awkward. —
andrybak (
talk)
22:12, 27 June 2024 (UTC)