Hi @Sarai-WMDE, thank you for your update! Based on the description, the "pulsating onboarding dot" would be always active. This seems a bit much, don't you think? My preference would be something like it is now described in the BDD (a help icon that you need to interact with). What do you think?

Thanks for the feedback, @Manuel! I was actually planning to reach out to you about this. With "always active", are you referring to the pulsating animation? We can define how many iterations we want the animation to have. For example, it could only pulsate twice, then become idle. The popover is only displayed on hover. It's very similar to the icon in that sense, but if you're concerned about potentially creating a distraction (very valid point) we could definitely go for the static icon.

There are a couple of things that I'm still trying to figure out (reached out to WMF) and would love to hear your opinion about:

1. I'm assuming that the icon will be visible in the termbox on edit mode for all users regardless of their log in status: is that correct?

2. Which factor(s) do you think should determine the disappearance of the icon? External time (e.g. display the onboarding icon consistently for a predetermined duration), number of visualizations (e.g. logged-in users only see the icon after enabling edit mode once), user preference (offer users the option to dismiss the onboarding icon permanently through a "don't show this again" checkbox inside the popover)? I might be inclined to combine external time (display the icon to every one for a number of weeks) with user preference (users can still dismiss the onboarding element at any point), but would like to know your thoughts.

Thank you!

Thank you again for the explanations and our discussion today, @Sarai-WMDE! Convincing and looks great! Is it easy to also update the png or should I just add a screenshot?

Sprint Planning Notes:

• There is some system to keep user preferences reagrding UI (e.g. The collpase state of the termbox itself and the copyright notice. See: https://gerrit.wikimedia.org/g/mediawiki/extensions/Wikibase/+/8009f2f93f06f35f0bed41008fdf7e546818dc07/repo/resources/wikibase.ui.entityViewInit.js#274)
• The final copy of the message might change, continue with the current copy, but make sure to verify with product before merging
• The reasoning to keep the help URL as an interface message, and thus also a localizable string, is to enable on wiki editors to determine the end URL for their own wiki (e.g. wikidata editors could decide where the wikidata help page goes).
• @Manuel will confirm with the other PMs whether this is needed for Wikidata alone (in which case we don't necessarily need to take extra care about the HELP URL and other configurable elements, since we will remove the code at the end of this onboarding period)

Task breakdown notes:

• We only want to add this on the JS side, not the PHP side (no-JS users couldn’t do anything with the pulsating dot anyways).
• To find the code responsible for the language name field in the termbox, codesearch for wikibase-entitytermsforlanguageview-language (the CSS class name).
• To find out how to use the pulsatingdot styles linked in the task description, codesearch pulsatingdot
• For some existing Wikibase-ish code adding a similar popup, see WikibaseQualityConstraints and maybe also Tainted References. (But Tainted References is implemented using Vue, and we probably want jQuery / OOUI here, so WikibaseQualityConstraints might be more useful.)
• See the sprint planning notes (T316769#8927033) for how to implement the option to remember “don’t know this again”.
• The default value of the link target (to be customized via the MediaWiki: namespace on Wikidata) should not be in en.json, but rather in the PHP or JS code, so that the language fallback works how we want – see T313599 (especially T313599#8224887), where we had issues with another thing that we also wanted to be configurable via i18n messages.
• To limit the number of iterations of the pulsating dot, we probably override the animation-iteration-count: infinite; via CSS.
• We’re first implementing the popup (T340643), then the “don’t show this again” option (T340644).

Change 939729 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Don’t add multiple pulsating dots

https://gerrit.wikimedia.org/r/939729

Change 939729 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Don’t add multiple pulsating dots

https://gerrit.wikimedia.org/r/939729