Just a reminder from user research: Participants love a sharing option; the problem with storing state in URLs is that the data that the URL can carry was, at least for some the handwritten requests, rather limited and people started to code-golf their queries.

Again, please: did we resolve this one?

I calculated the hoover index for some contribution metrics recently and it was rather easy to do using a table with the columns edit count | count of accounts with this edit count which has somewhat between 100 and 1000 rows. Hoover also seems to be rather easy to understand, working without area-under-the-curve and varies between 0 (all equal) and 1 (maximum unequal).

See related T217233 (Implement Model Items on Wikidata)

See related T205014 (Data input: Forms for Item Entry)

On this issue, the research with GLAM partners might be interesting, as many voiced problems with data modeling. See the Report, Chapter "There is no obvious way to get your data into Wikidata 'the right way'", page 11ff.

I'd still be interested in case resources are allocated to this.

What you mean is clear but any concrete example exhibits the problem that it would showcase (and thus, arguably, favor) the use of one particular technology

It always was assumption that the "Show code" link…

…I did write the original issue on github, in case anyone has questions.

I assume that you if you use it with an RTL language you would have it all right-aligned (including checkboxes), correct?

Do you have a solution for that?

Update: We use a GDPR compliant Mailchimp

Icon: It is the same way of displaying as on constraint violations, so I would for now leave it this way.

Seems fine to me – mockup above, screenshot below.

I'll just ask you – I guess it won't fluctuate widely from month to month.

Thanks! This is what I needed. In case I need precise numbers for area-under-curve or so, I’ll create another task (I "integrated" via cumulative sums in Excel by now, so I might be off a measurement or so, but it is still enough as estimates)

a column where each particular editor is represented by one row while the (pseudonymous) user column refers to some ID value which thus anonymizes the real user ID/username? I guess (2)?

"Heute ist der letzte Tag unserer Spendenkampagne" breaks the above definitions.

Depends… I guess this is still relevant and unresolved as long as the target groups have not been defined somewhere, yet.

What is also in vue’s favor but something that is not highlighted in the RFC is that the documentation is very good. This does not only mean comprehensive and not wrong, but also that there are different types of documentation for different usecases (Onboarding, General Learning, Reference). This was one of the key points when some colleagues and me were thinking about a new framework at WMDE. A lot of people come from PHP or OOUI rather than from other MVVM-frameworks. Thus, a good documentation which quickly shows people what the framework is about, is important. Since the js file of vue is sufficient, people can quickly try it out what the documentation tells them (there are also embedded examples, but maybe you want to try in a mediawiki-context or whatever)

{M290/985}

The usual color for this is #808080, the opacity is set to 50%. Hovering over it now changes the color to #747474, leaving the opacity as is. If you don't know that there is a hover effect, you just don't see it.

It could also be always in the center of the remaining area or at the 3/4part of the remaining area. It just is easier to build when it has a fixed position. Devs can also take this apart and estimate pointer position adjustment separately.

proposed solution in ticket.

I cant reproduce this. When I go to spenden… click "5€" and press ENTER, it does nothing.

thanks. updated…

It seems that keeping the value in the field is the standard, thus I would suggest also keeping the numbers. (or in general: Do whatever the standard input-for-numbers behavior on the device is)
The larger problem might be that we attach a €-Character directly to the input, which leads to confusing appearances and disappearances of the € and makes hitting the right spot with your cursor harder (since "after the number" needs to be in the small spot "before the €"). Biggest gain for the field is getting rid of overwriting the value and showing the € via CSS.

Text for message: "Die E-Mail-Adresse scheint nicht korrekt zu sein. Eine E-Mail-Addresse kann z.B. so aussehen: max@example.com"

@Jan_Dittrich I did not properly get the hover colors. Should all of them share the same hover color?

The radio buttons on "Spenden als..." should be vertically arranged

Calculations:

Is that intentional or an oversight?

The form should be responsive (e.g. label goes to the top of input fields) - This variant might also be used for the email campaign in the first week of Nov

See issue at https://phabricator.wikimedia.org/T236465
Different sizes (at least on Firefox)

Just for the sake of not loosing the information: I noted that there seems to be something like a standard pattern of how other web-tech-based projects deal with this, namely the pattern of:

final figma mockup is pasted in the ticket. It is to be found where the previous mockup has been.

it gets a bit cramped in this grey box with the 4 question columns.

We (WMDE SWE FUN Tech) do not know what our actions should be here. If this is a task for us, please speak with someone from the team @Christine_Domgoergen_WMDE

@JanJaquemot Thanks for the test – we found out that Safari for Windows is not updated 2012 and we do not support it (also the share of visitors is 0,…% on Wikipedia.de)