Feb 12 2019
Feb 11 2019
Feb 10 2019
Feb 9 2019
+1 to this idea since this dialog already exists when a user taps to unsave an article on multiple reading lists from the Explore feed:
Feb 8 2019
The feature graphic had been updated to use the globe logo in late June 2018's release.
Feb 5 2019
hi @MMiller_WMF - LGTM now on desktop and mobile web (caveat: not tested on iOS)
Thanks @revi for the taking the time to capture these examples.
@Marshall - the examples do share a lot of characteristics captured in the main task (short messages with usually only a single CTA), and the verification ones may be particularly relevant for verbiage to consider in the Korean version of the verification email. Generally speaking these examples will be useful to have available to review against once our own email campaigns are translated to KO and CS.
Feb 4 2019
Feb 2 2019
Jan 30 2019
Jan 25 2019
Yes, sorry this was just what was in the original mock since I've not had a chance to update the help panel with search.
@SBisson – can we update the text to say "Search for help" on English, with CZ and KO to translate according to whatever is suitable in their respective languages.
That button is based on the same idea as the "Open article in a new tab" button when contents of a search result link appear inside the help panel filed on T211513. The idea is to enable the user to open a Help contents page in a new tab instead of continuing to search inside the help panel. We don't need it for day 1 though, esp. since it's less clear where this would go on KO and CS (whereas in EN it'd go to the Help:Contents page).
Per comments on T209301 - do we want to put this task on hold until after deploying search in the help panel?
I'm thinking that if we see a high number of users abandoning the edit after clicking on a link inside the help panel, that would be a sign for a need to have help article content appear within the help panel instead and we can re-prioritize then.
Adding @nettrom_WMF in case he has more thoughts on what we can look out for...
Jan 23 2019
Jan 21 2019
Hi @Urbanecm - you can see some of the email samples on later slides in this *work in progress* presentation here:
Jan 18 2019
Jan 17 2019
More comments inline....
Thanks @Etonkovidova - please see responses inline.
Jan 16 2019
Jan 15 2019
Jan 14 2019
Thanks @Etonkovidova - I think it is acceptable to have the visible checkboxes on Chrome, and per @Volker_E 's the "selected button" using Accent10 is expected (an oversight on my part earlier). LGTM to sign-off.
Jan 13 2019
Hi Robin , thanks for going through the proto again, just have a couple comments inline below.
Jan 11 2019
- Sure, I'd just request the specific Alpha version is clearly marked and uploaded for testing across all participants.
Hey @Volker - looks like both the updated references and existing reference icons were omitted in the export. Here are the updated icons as SVGs - thanks for your vigilance :)
Jan 10 2019
LGTM as well (tested on Chrome mobile browser on Pixel, Android OS 9)
LGTM too!(Nexus 5)
- Yes, that's fine. The main thing is that the message is intended to start on the same line as the icon. The message wrapping to a second line is bound to occur in some language translations and smaller device widths anyway.
- How many people turned on polling out of all those who saw Notifications?
- Interactions with different notification types - how many Milestone, Welcome and Thank notifications were sent vs viewed?
- Was there a particular notification type that shifted contribution/edit rate more than others?
Jan 8 2019
I think we don't need to mention this one exception case
LGTM, and not resizing to the standard view after opening when the window was >1366px is fine.
Hiya - animations LGTM for desktop and mobile:
(open fullscreen to view animated gifs)
Jan 7 2019
Relevant to this are some old designs for the same issue on iOS: