[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Page MenuHomePhabricator

Determine language/i18n for Article Reminder notifications
Open, MediumPublic

Description

Capture.PNG (740×1 px, 142 KB)

"echo-category-title-article-reminder" (Label in preferences): "Page {{PLURAL:$1|reminder|reminders}}",
"echo-pref-tooltip-article-reminder" (Tooltip for preferences): "Notify me about this article when I asked.",
"echo-reminder-popup-main-title" (Title for the page reminder popup): "Set a reminder about this page",
"echo-reminder-comment-input-placeholder" (Placeholder for the page reminder comment input): "Review this page...",
"echo-reminder-timestamp-title" (Label for the page reminder chosen timestamp): "When",
"echo-reminder-timestamp-input-placeholder" (Placeholder for the page reminder timestamp input): "Pick a date",
"echo-reminder-tomorrow" (Label for one of the suggested timestamp for the page reminder): "Tomorrow",
"echo-reminder-next-week" (Label for one of the suggested timestamp for the page reminder): "Next week",
"echo-reminder-next-month" (Label for one of the suggested timestamp for the page reminder): "Next month",
"echo-reminder-cancel" (Label for cancel button in the page reminder popup): "Cancel",
"echo-reminder-approve" (Label for approve and create an page reminder): "Create reminder"

Wording of notification itself

For a single message
  • Header: (Message for page-reminder notification. Parameters:\n* $1 - the formatted username of the user who requested the reminder. \n* $2 - the username for GENDER\n* $3 - the formatted page title of the article the user requested) [notification-header-article-reminder]: "Scheduled reminder: '''$3'''",
  • Body: (Body of page-reminder notification): <User's comment>
For Bundled Messages (To Be Determined if we do bundling)
  • Main, bundling message:
  • Subsidiary, bundled message:
Links
  • Primary link label (for email display only): (Label for the link to the article the user requested to be reminded about) [notification-link-article-reminder]: "View page",

We'll also put the notification type on Beta Cluster soon ( T169354: Enable Article Reminders feature flag on Beta ) which should help with this.

Event Timeline

What are the choices about this text?

Mattflaschen-WMF renamed this task from make a decision about the text in the notification to Determine language/i18n for Article Reminder notifications.Jun 20 2017, 6:03 PM

We'd like @jmatazzoni to come up with text for this.

@Eee888 Can you put the current placeholder text from the commit in the description (explaining where each message is used), as well as any messages without placeholder text?

@Eee888 Can you put the current placeholder text from the commit in the description (explaining where each message is used), as well as any messages without placeholder text?

Thanks. For each message, please also explain briefly where it's used/the purpose. You can base this on qqq.

I think @Eee888, @Mooeypoo and I can handle the API parameters (used by developers, not user-facing) in code/code review, so the product people can focus on the others. So I'll remove the API ones from here.

Notify me about this article when I asked.

I know the global task has been named Article reminder, but I think many people would like to have it for all pages. So I would advice to use "page" instead of "article" in messages. Use "page" will make all messages consistant.

You also have a typo: Cancle -> Cancel :)

echo-reminder-comment-input-placeholder

I'm not sure to understand the purpose of this message. It it where users can leave a note about the reminder? I don't see the label for this field.

Thanks @Trizek-WMF , I'll fix the "article"->"page" and the tipo of course :)

If you'll look at the attachment I've just added, I'm sure you'll understand the comment placeholder thing.

If you'll look at the attachment I've just added, I'm sure you'll understand the comment placeholder thing.

Thanks, I see now. I don't know if the label is clear enough. Maybe something like "add your note" or "What I have to review" may be more understandable. @Pginer-WMF, any idea?

Based on what I read in T2582, here's my suggestion for language:

Header: Scheduled reminder: Pagename
Body: UserComment

Or, if we think the header will be too long:

Header: Reminder: Pagename
Body: UserComment

Do we know all the other elements of this notification? The icon, etc. It is usually very helpful if developers/proposers fill out the Notification Request Form, as part of their primary ticket .See below.

New Notification Request Form

Filling out this form will help developers and product people understand your idea and will provide the information required to implement it. To see examples of the types of answers required, have a look at this sample form. To understand unfamiliar terms, visit the glossary. 

Basic information

  - Purpose of the notification:  
  - Notification name:  
  - What triggers notification?: 
  - "Notice" or "Alert"?:  
  - Notification type (standard, bundled, expandable bundle):  

Wording

For a single message

  • Header: 
  • Body:  

For Bundled Messages

  • Main, bundling message:
  • Subsidiary, bundled message:

Links

  - Primary link target:
  - Primary link label (for email display only):

  - #1 secondary link target: 
  - #1 secondary link label:

  - #2 secondary link target:
  - #2 secondary link label:

Icon

  - Icon name:  
  - Link to graphic/example: 

Do we know all the other elements of this notification? The icon, etc.

There is no icon yet. It's tracked at T170517: Icon for Article Reminder.

Thanks, I see now. I don't know if the label is clear enough. Maybe something like "add your note" or "What I have to review" may be more understandable.

I like "What I have to review" or "What to remind me about". What do you think?

Do we know all the other elements of this notification?

Thanks for reminding us about this. Most of these are already decided, and I've documented them at T165754: create new notification type for the article reminder.

The remaining open spec issues for the notification itself are:

I don't believe we need secondary links, but correct me if I'm wrong.

What about having a link to the page history?

I'm not firm on it, but it seems likely that reminders might want to be bundled. Here is a possible main bundling message:

  • You've received X scheduled reminders. [where X is the number received]

I don't think the bundled messages need to change.

  • You've received X scheduled reminders. [where X is the number received]

"You have X reminders." is enough, don't you think? "received" and "scheduled" are obvious and can be skipped.