Page MenuHomePhabricator

Add a link: frontend product specifications
Closed, ResolvedPublic

Description

This task is a parent task for the frontend specifications for the "add a link" structured task. It also contains some general specifications.

General specifications

  • The new "add links" task should replace the non-structured "add links" task. But we should still retain the ability to resurface the non-structured task that relies on maintenance templates, in case some wikis want it. Though it's hard to imagine a situation in which we would want both types of "add links" tasks available, we should still allow that to be possible.
  • When we deploy the new "add links" task, that should be the only task type selected for newcomers, as opposed to the current situation in which newcomers have both "add links" and "copyedit" selected, and get feeds containing both. We want to be opinionated about exactly which types of edits newcomers should start with.

Materials

We also have a flowchart for mobile, showing which elements of the mobile workflow are going to need changes, and which are complete additions. Engineers should speak up if it would be useful to have such a flowchart for desktop.

02 Flow chart.png (2×9 px, 387 KB)

Related Objects

StatusSubtypeAssignedTask
ResolvedMMiller_WMF
Resolvedkostajh
Resolved mewoph
Resolvedkostajh
Resolved mepps
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolvedkostajh
Resolved mewoph
Resolved mewoph
Resolvedkostajh
ResolvedEtonkovidova
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
DuplicateNone
Resolved mewoph
ResolvedBUG REPORTkostajh
ResolvedTgr
ResolvedBUG REPORT mewoph
ResolvedBUG REPORTEtonkovidova
DuplicateNone
ResolvedBUG REPORT mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
Resolved mewoph
ResolvedTgr
ResolvedTgr
Resolved mewoph
ResolvedTgr
Resolved mewoph
ResolvedMMiller_WMF
Declinedkostajh
Resolvedkostajh
Resolvedkostajh
DuplicateNone
Resolved mewoph

Event Timeline

@kostajh @Tgr @mepps @mewoph -- @RHo and I have finished writing the copy for this whole feature set, and I've updated the Phabricator tasks accordingly. Here's how it works:

  • From now on, the canonical copy is what's written in the task descriptions. This is going to disagree with what you see in the mockups and prototypes. If there is any disagreement, the task description wins. And if we need to make any changes going forward, I will update the task description.
  • The copy spreadsheet is where you can find recommended message names and QQQs for all the copy. We were careful with the QQQs to try help translators make high quality translations.
  • When we believed that the new features would likely reuse existing messages from our older features, those messages are not listed in the spreadsheet at all. Please let us know if you think any new messages are needed that seem to be missing.
  • There is one case on T268706: Add a link: difficulty overlay and difficulty filter where we need to edit a legacy message (and its QQQ) so that it makes sense with AI suggestions.
  • There are three cases where we need to update the QQQs for legacy messages, so that they make sense for the "AI suggestions" context. I created a new task for that: T275182: Add a link: legacy QQQs.
kostajh triaged this task as Medium priority.May 27 2021, 11:55 AM
kostajh claimed this task.

Initial release is out, further improvements are tracked in the improvements epic (T276517). cc @Rileych @MMiller_WMF