Thu, Feb 14
ValueMapping is better to be done in frontend.
Sun, Feb 10
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. 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)
Wed, Feb 6
Tue, Feb 5
If there is a demo page, I could check from UX point of view.
Mon, Feb 4
@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.
Fri, Feb 1
Thu, Jan 31
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)
Tue, Jan 29
Fri, Jan 25
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?
Thu, Jan 24
Jan 17 2019
Error messages are like this:
…and the spec for the example text in case of empty fields is a 50% transparent black:
Jan 16 2019
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.
Jan 15 2019
- 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.
Jan 14 2019
@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?
Jan 10 2019
I'm still in the design but here are some points that might already be of interest:
Jan 8 2019
Jan 7 2019
…this would also ease page analytics in Matomo (since one can distinguish page via title. Or not, as currently)
Makes sense to me:
Jan 2 2019
Let's use a lightbulb icon based on the lightbulb icon from OOUI :
Dec 19 2018
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.
Dec 18 2018
That means we can report back here once done and say actually how the thing can be configured and then decide on some text.
I'm not really sure what these instructions would be, I guess that depends on how this task exactly is completed.
Dec 17 2018
Dec 15 2018
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"
Dec 14 2018
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:
Dec 13 2018
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?
- 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)
- We also could half the size of the barometer, making space for this.
- We choose a color for the bar that contrasts well with black (does not work with the red color scheme!)
Dec 12 2018
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.
Dec 10 2018
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?
Nov 20 2018
Nov 19 2018
@GoranSMilovanovic no, I'll close it. Thanks btw, this was very useful.
Nov 13 2018
Nov 5 2018
Yes, what @kai.nissen said: The links are merely static links to the plans, they do not interact with page content (the most simple reason: it is easier to build, and probably easier to use)
Nov 1 2018
@gabriel-wmde : I like the idea. I think it would create too much overhead, to create this – I do not consider the sidebar interaction wise essential, here.
Oct 30 2018
Since the color changes are an easy fix for issues with our last-years best performing banner and has a rationale: Is this on any TODO-list? @kai.nissen
Oct 29 2018
How is this imagined to work for our users ? e.g. imagine, a donor moved to a new place. When/Why would they change the address? Where would they go? How would they know this has been successful?
Oct 26 2018
@tmletzko: This would be in a "text component" for me. After MVP state, it might make sense to give it some sort of style-class to e.g. make it "fine print" (aka a bit smaller and/or lighter) or so.
Oct 24 2018
Briefly talked to @kai.nissen – here clarifications:
Oct 23 2018
Oct 22 2018
2.1 Q2.x are like 1.x, but only for september 2018.
Yes. Initially, you asked for an overview of the last 30 days or so. However, the wmf.mediawiki_history Hadoop table, where the data for this analysis is found, …
Oct 19 2018
Oct 18 2018
Wikibase and help people find all the tools and documentation around it.
People need to better understand what Wikibase is, why they'd want to use it and get answers to questions about how to install/use it.