Page MenuHomePhabricator

Topic Subscriptions: Define copy and ensure consistent treatment across touchpoints for Notifications
Closed, ResolvedPublic

Description

Problem:

Notifications appear within the Echo dropdown, in email and as popup messages. What they say should be consistent. [i]

Requirements

  • The interface copy and QQQ messages defined in this spreadsheet are implemented.

Done

  • All possible "Touchpoints" are accounted for
  • The "Current copy" and "Revised copy" is defined for each touchpoint
  • ===Requirements are met

i.

Unusibscribe affordance + toastEcho notice
Screen Shot 2021-04-02 at 11.26.50 AM.png (349×306 px, 34 KB)
Screen Shot 2021-04-02 at 11.30.35 AM.png (266×542 px, 36 KB)

Event Timeline

iamjessklein renamed this task from Topic Subscriptions: Choose a consistent style treatment for Notifications to Topic Subscriptions: Define copy and ensure consistent treatment across touchpoints for Notifications.Apr 2 2021, 5:12 PM
iamjessklein updated the task description. (Show Details)

I updated the description card with the copy link for Echo and Email notifications.

I updated the description card with the copy link for toast messages.

13-April update
During today's team standup, we identified some additional "touchpoints" as needing to be "designed." These additional "touchpoints" are listed below.

I've also updated the task description's ===Notifications touchpoints + copy section.

  • Affordance in a section to which someone has NOT yet subscribed
  • Affordance in a section to which someone has attempted to subscribe
  • Affordance in a section to which someone has successfully subscribed
  • Affordance in a section to which someone has attempted to unsubscribe
  • Affordance in a section to which someone has successfully unsubscribed

I just want to clarify here that this ticket is about the language, and considering that this is a highly textual feature, I want us to use this ticket to gain consensus on the word choice here. If there are additional tweaks to the ux that need to be tweaked, I would prefer that we decouple them from this ticket.

Here is a first draft of the copy for Notifications.
@Esanders I have a few questions for you to answer in the "UX Notes" section.

@Esanders and I did a final review, I am moving this over to Ready for Sign Off for @ppelberg to scan.

@Esanders and I did a final review, I am moving this over to Ready for Sign Off for @ppelberg to scan.

Looks great, @iamjessklein. I posted one question for you to answer in the sheet here.

I default to you to make the final call on what I'm asking above.

Once you've arrived at a final opinion, can you please do the below?

  1. Comment it within the sheet
  2. Un-assign yourself from this task and
  3. Move this task to the "Ready to be worked on" column

Note to engineer implementing this: Let me know if you have any questions.

ppelberg updated the task description. (Show Details)

I'm re-opening this task considering the copy @iamjessklein defined in this spreadsheet has not yet been implemented.

Change 685413 had a related patch set uploaded (by Esanders; author: Esanders):

[mediawiki/extensions/DiscussionTools@master] Subscribe/unsubscribe with plain text links

https://gerrit.wikimedia.org/r/685413

Change 685413 merged by jenkins-bot:

[mediawiki/extensions/DiscussionTools@master] Subscribe/unsubscribe with plain text links

https://gerrit.wikimedia.org/r/685413

Test wiki created on Patch Demo by JKlein (WMF) using patch(es) linked to this task:

https://patchdemo.wmflabs.org/wikis/91bccd4c6b/w/

ppelberg claimed this task.

Test wiki on Patch demo by JKlein (WMF) using patch(es) linked to this task was deleted:

https://patchdemo.wmflabs.org/wikis/91bccd4c6b/w/