@kai.nissen told me that the current labeling suggestion would be problematic, since they are not composed of parameter name and value.
In case the current suggestions are too difficult to implement, a variant which would allow this would be:

If Graphana can create them reliably, last-4-weeks histograms would be nice for time, MB, revisions. (if people want something really fancy: Kernel density overlayed)

A colleague was pointing out that

Header: Haben Sie 3 Minuten Zeit für uns? (it really does not take longer than that)

We kindly ask you …

You're trying to import a file with the extension <extension name>. This file type is not allowed in this wiki.

Also, + 1 for active wording (e.g. "Sie können uns Ihre aktuelle Adresse auch mitteilen, wenn Sie keine Bescheinigung erhalten möchten."). Remember we want them to add their address even if they do not need a Zuwendungsbescheinigung.

I assumes it is form-language-standard, but yes, we should make this easier by getting rid of "optional".

I see two problems here:

For the person implementing it: This is the arab beta features page showing the existing right-to-left icons

Great! Were there any overall findings that could help us in future designs? (For example, it seems that repeatedly, the UIs suggested to start with a property, but users wanted to start with an item.)
Also, to roughly keep track: How many users did test the UIs?

if the line was moved to below the selection

How about we put that checkbox above the presets, in the actual expandable part? Like in the screenshots below:

If we want to keep the current UX, the prerequisite for starting this task is having browser tests for the current behavior.

There was the problem that there is nothing gained if a user activates "all" by default (since the pills are so many that any other space saving is small in comparison). However, it seems that "Articles" is the default, which means it makes sense.

Raw data of visitor logs is not available anymore. Do you agree, that this task can be closed?

We want to find out if the rollback confirmation prompt is useful.

ValueMapping is better to be done in frontend.

If we do this it should be very subtle; I looked at some other pages and did not see any highlighting in Wikipedia articles or e.g. at this handbook so it might be perceived as unusual or irritating. But we could just enable the browser defaults as on this page (I think this is the browser style; on Firefox it is black dotted outline, on chrome it is blue solid outline)

If there is a demo page, I could check from UX point of view.

@Tobias_Schumann_WMDE thanks! This might help to rename them e.g. to "Donationform_10h16_page1" or so.

For some reason they are in the city-code order, but I do not know why. Probably carelessness on my part, if possible, swap them.

It seems matomo was updated. Can I request a lot, again? Or do you want to try first and then tell me (I can't restart the crashed thing myself)

you mean a different section like section A…

I don't doubt the usefulness of opt-out for receipts.

In case it should be there nevertheless, this is what it would look like:

@Jan_Dittrich I just noticed that the donation receipt opt-out ("Ich benötige keine Spendenbescheinigung.") is missing in the design. Can you provide an updated version?

Error messages are like this:

…and the spec for the example text in case of empty fields is a 50% transparent black:

Reviewing the suggestions and what we got as suggestions, it seems to be really hard to "fix" 3 states ranks and that it is also not viable to redo the data model.

The texts you see in the mockups are not placeholders (or better worded: Examples) but actual, editable, prefilled text based on the current data. The placeholders would only apply if people delete the content in these fields.

but might on the other hand reduce their overall conversion rate.

• Title: Anschrift ändern
• Subtitle: Bitte überprüfen Sie die Änderung

Title: Anschrift ändern
Subtitle: Die bisherigen Daten sind schon eingetragen, bitte passen Sie diese an.

no specs:

@Lucas_Werkmeister_WMDE We have newly sized icons ready, we need to find out how you want them to be exported to be of use.

Should this be merged with T213155

I can imagine two flows:

What does the user get if they click on "edit", then?

I'm still in the design but here are some points that might already be of interest:

…this would also ease page analytics in Matomo (since one can distinguish page via title. Or not, as currently)

Makes sense to me:

Let's use a lightbulb icon based on the lightbulb icon from OOUI :

Also, I see we should have some behavior for breaking words to two lines if they are too long instead of just overlapping as in the second image.

That means we can report back here once done and say actually how the thing can be configured and then decide on some text.

@Ladsgroup @Addshore Thanks! Both are fine, UX will pick one.

I'm not really sure what these instructions would be, I guess that depends on how this task exactly is completed.

Yes, it would be good if it would get hover behavior. The trick is that it should not afford clicking as one does with a button, since this does not yield any useful result. Instead it needs to signify "fill-out-ability" rather than "clickability"

Based on additional feedback I would put the "Nur noch 10 Tage" with the "Es fehlen 2,5 Mio. €"

"Noch 10 Tage", previously this was inside the progress bar on the left.

Here is the mockup:

I vote for the first suggestion. No need to reduce the height of the progress bar, though.

So it is fine to make the banner one line larger?

1. We put the text out of the banner, one left aligned to it, one right aligned to it. If the banner is far to narrow they will go in different lines (as flexbox magic makes it)
   1. We also could half the size of the barometer, making space for this.
2. We choose a color for the bar that contrasts well with black (does not work with the red color scheme!)

The dirty way is to increase the space between "polish" and the gloss. The right way is to have a certain way of how language metadata is represented and have it look the same everywhere so it is easily recognized.

Suggestion: Lets use the wikibase logo, make it less opaque (like the Mediawikilogo above) and add the text with the instructions. @Addshore: What would the correct text be (since we probably need to bake it into the pixels except s.o. wants to add imagemagicmagic to the build)

Although this ticket actually conflicts with my own ideas about how the button should work.

Can the improvements be reviewed and merged back?

@GoranSMilovanovic no, I'll close it. Thanks btw, this was very useful.