As part of the work to make the Section Translation dashboard ready to become the default dashboard across platforms, this ticket proposes to implement the impact panel that is only available on desktop right now:
This is a panel with the "Your impact" title shows the number of translations for the user in the following ways:
The counter and bar for the current month are highlighted using Accent50 (#36c) color.
The position of the module is adjusted depending on the available window size. On wider screens it is plaed on a separate column at the end, while on narrower screens it will appear below the lists of articles.
More details in Figma
In order to properly support this feature, we need to define what qualifies as "translation" in this context. More specifically:
In T324474#8704572 , @ngkountas wrote: In order to properly support this feature, we need to define what qualifies as "translation" in this context. More specifically:
Good questions Nik, replying below:
Do draft translations qualify for these stats?
No. The idea is to represent only published translations. In this way, users are encouraged to complete their in-progress translations and publish them.
Do section translations qualify as translations? Please note that per design it's impossible to identify as "published" a section translation that has been published, then edited again (without being published again). Such a translation will be considered as "draft".
Yes. Section translations will be represented as translations once published. It is ok if the translation is no longer counting as published if the user decides to continue editing it (since it can be interpreted as a signal that it was not complete).
This approach can create a bit of an unbalance where an article translate din one go is counted as 1, while doing the same work on a section-by-section way for their 7 parts will be represented as 7. If some users are very driven by this number difference, we would be encouraging them to work on a section-by-section approach which is ok since it brings other benefits (e.g., easier for people to work on multiple parts, content less likely to become outdated, etc.). The reverse (ignoring sections translated) seems a more problematic approach : user feeling their effort is not valued by not being reflected in the stats.
Regarding the monthly stats, do we consider a translation to be done in a specific month based on its starting date or based on its latest update?
Ideally, based on their publishing date. The panel is about their impact, which only makes sense when content becomes visible to readers (i.e., when published).
Change 904494 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):
[mediawiki/extensions/ContentTranslation@master] SX: Add impact panel to dashboard
https://gerrit.wikimedia.org/r/904494
Change 904494 merged by jenkins-bot:
Change 907436 had a related patch set uploaded (by Nik Gkountas; author: Santhosh):
[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.2.0+20230410
https://gerrit.wikimedia.org/r/907436
Change 907436 merged by jenkins-bot:
This task is now completed and properly deployed in production.
Screencast from greek (el) production wiki: