Wikidata talk:Tools/Enhance user interface

request?

Dunno if this is the place for this but if someone is willing to help me figure out what to put in my common.css to get the following (floating action button (Q110949494)-style), I'd be very appreciative:

https://cdn.discordapp.com/attachments/864701767866384424/931842786850902026/plusQL.png

Thanks, Arlo Barnes (talk) 09:34, 15 January 2022 (UTC)

"What links here" at Wikidata needs to show usage as "structured data" at Commons

"What links here" at Wikidata needs to show usage as "structured data" at Commons. I brought this up before, but I can't find the place it was posted. We often delete entries in Wikidata because we do not realize they are in use at Commons because we do not link to them unless they are in a Category. If there is only one item, usually a category is not created. Currently, when we are at Commons, I can see at "structured data" what Wikidata entries are linked, but I cannot see the reverse. For instance I can see that this file at Commons: File:Gabriel Reynart (1915-1988) Brazilian immigration card for 1958.jpg links to Wikidata through the category and "structured data", but from Wikidata I would not be aware of the links at Commons if the Category did not exist. I want to click on "What links here" at Wikidata at the entry for Gabriel Reynart and see the use as "structured data" at Commons. RAN (talk) 00:30, 21 September 2022 (UTC)

Renaming the page to Wikidata:Tools/User scripts

@Ameisenigel: could you rename the page to Wikidata:Tools/User scripts? This page is specifically about user scripts, so naming it that makes more sense than "Enhance user interface", especially because there are many ways to enhance the UI other than user scripts, such as browser extensions or user styles.

Note that Wikidata:Tools/User scripts previously existed, so you'd probably have to move it out of the way first.

--Push-f (talk) 00:17, 19 November 2022 (UTC)

Let's see if there are any objections and wait a few days. If there are no objections, I will take care about this. --Ameisenigel (talk) 08:42, 19 November 2022 (UTC)

I don’t feel very strongly about it, but I’m somewhat unconvinced: the organization of Wikidata:Tools is by “what” you want to achieve, not “how”. Why should it matter if I want to enhance my interface in xyz fashion, whether that’s achieved through a user-script or a browser extension or a gadget or else? What is a user-script anyway? (I do know, but not everyone might). I also don’t think the existence of Wikidata:Tools/Browser extensions justifies the move, given how it was created just today − if anything, that page could/should be folded back into the respective pages of what these tools seek to achieve. Jean-Fred (talk) 14:57, 19 November 2022 (UTC)

Thanks for the feedback :) I agree that userscripts and browser extensions are similar enough that they should be listed on the same page, especially because as you mention there right now are only 2 browser extensions listed, so I have merged Wikidata:Tools/Browser extensions into this article.

I however still think that the page should be renamed to "User scripts" because:

1. I think browser extensions should be listed separately from user scripts, so that we can show a disclaimer that you should be particularly careful with installing them, since browser extensions can access any website (as opposed to MediaWiki userscripts/gadgets which can only access pages on the wiki where you install/enable them).
2. This requires the sections that are purely meant for userscripts to somehow be recognizable as such. Currently I do this by having "userscripts" in every section title, which I dislike because it is redundant. While we could introduce a page structure such as:
   1. Userscripts
      1. For editing
      2. To enhance the display of values
      3. To link wikidata frontends
      4. For lexemes
      5. Others
   2. Web extensions

I am reluctant to do so since this would hurt the user experience on mobile because Minerva Neue (Q22713032) only makes <h2> tags collapsible but not <h3> tags.

The only alternative to repetitive section names and a poor mobile experience that I see is renaming the page to "User scripts", which would then allow the page structure:

1. For editing
2. To enhance the display of values
3. To link wikidata frontends
4. For lexemes
5. Others
6. Web extensions

The Wikidata:Tools/User scripts#Web extensions section in this case would function as a "See also" section, since the page is mostly about user scripts (the page currently contains 68 user scripts and only two 2 browser extensions).

I hope that made some sense to you.

Note that I think we should merge Wikidata:Tools/Edit items#Userscripts for wikidata.org into this page because it makes sense to list all MediaWiki userscripts/gadgets on one page, so that this page can be linked from Special:Preferences#mw-prefsection-gadgets. The text on that preference page can be customized via MediaWiki:Gadgets-prefstext and currently only links Wikidata:Tools. If we move this page to Wikidata:Tools/User scripts we could update MediaWiki:Gadgets-prefstext to link Wikidata:Tools/User scripts directly, making it easier for users to find the page.

--Push-f (talk) 13:15, 20 November 2022 (UTC)

To be honest this seems the wrong way around to me as @Jean-Frédéric explains. Why not use the page for these other things you mention as well? Renaming it to user scripts makes it less accessible for new people. LydiaPintscher (talk) 15:26, 21 November 2022 (UTC)

Fair enough. I am happy as long as we have all userscripts on one page, which we now do, since I have merged Wikidata:Tools/Edit items#Userscripts for wikidata.org. --Push-f (talk) 15:31, 21 November 2022 (UTC)

What gets added here

Is there a procedure or I can just list a script of my own here? (this one). --Base (talk) 07:08, 27 February 2023 (UTC)

I went ahead and added it. In an awkward manner though because it seems that the template does not handle scripts hosted on another wiki well. --Base (talk) 07:26, 27 February 2023 (UTC)