Page MenuHomePhabricator

Planning: finalize and create tasks for Surfacing Structured Tasks
Closed, ResolvedPublic

Description

Main User Story:

As the Growth team, I want to tasks broken out for our WE1.2 Hypothesis, because then we can plan our Q2 work.

Underlying User Stories:

As a new Wikipedia account holder using a mobile device, I want the editing workflow to be broken into a series of simple steps, so that I can easily and successfully contribute.
As a new Wikipedia account holder using a mobile device, I want real-time editing support to be available exactly when I need it, so that I can effectively contribute.


This task includes the time needed for technical decision making and breaking out the necessary tasks for the "Read-mode, inline-tag" approach for Surfacing Structured tasks:

  • Retrieving link recommendations for a random article (solution should also scale to other structured tasks)
  • Marking text in read-mode
  • Displaying popup in read-mode


Background

Current full-page editing experiences require too much context, patience, and trial and error for many newcomers to contribute constructively. To support a new generation of volunteers, we will increase the number and availability of smaller, structured, and more task-specific editing workflows (E.g. Edit Check and Structured Tasks). The Growth team will primarily focus on Structured Tasks, while working closely with the Editing team to ensure our work integrates well with Edit Check.

This project aims to address the following user problem: Getting started editing on Wikipedia is difficult and especially frustrating on mobile devices. I want the editing interface to provide the in-the-moment policy and technical guidance I need, so my initial efforts aren't reverted.

This project aims to achieve the following user outcome: As a new Wikipedia volunteer, I feel confident and enthusiastic about contributing to the Wikimedia movement by editing Wikipedia articles. The tools provided guide me step-by-step, limit distractions, and allow me to learn progressively so I can successfully contribute on my mobile device.

As part of the Growth team 2024/2025 Annual Plan, the Growth team will explore various ways to increase constructive activation on mobile. This is part of the Wikimedia Foundation 2024-2025 Annual Plan, specifically the Wiki Experiences 1.2 Key Result

Design

Figma design file

Acceptance Criteria
  • Engineers outline the main technical tasks necessary to complete the WE1.2.6 hypothesis
  • Product creates the initial tasks in Phab
  • Tech Lead refines acceptance criteria and technical details for engineering tasks

Details

Other Assignee
Sgs

Event Timeline

@Sgs and I talked about this a bit in our 1:1, and here are our draft notes sketching out one possible approach

Drafts of Product User Stories

  • Story: As a newcomer user, when I’m reading, I want to receive edit recommendations so I can start editing in an easy way
  • Story: As a user who has clicked on a recommendation within a reading session, I want to receive structured steps to complete the edit recommendations (structured task)

Technical subtasks

  • Create a disabled-by-default feature flag for this work (name TBD)
  • Create an internal Action Api endpoint that allows getting the recommendations for the current page
    • For now, it actually only get the link-recommendations from that database
    • It should require the user to be logged in and otherwise just return empty
    • It should be disabled unless a feature flag is enabled
  • If the above new mediawiki/GE API endpoint is hit for an eligible page that does not have a recommendation, make a server API request to the recommendation-endpoint to retrieve new recommendations, storing them in the database and Cirrus search index, and then return those recommendations to the original request
  • Create an EditCheck-like popup to prompt the user to start the edit recommendation
    • If the user clicks yes on the popup, trigger the usual Add-a-Link VE interface
  • Add a copy highlight functionality to use the link-recommendation from the api. If the user interacts with that, trigger the popup
  • Define an experiment plan and instrumentation specification
    • The initial experiment would run for a short period of time (3 weeks) to gather data
  • Evaluate the impact on the homepage and existing functionality of increasing the task pool by an order of magnitude, from 20K to 200K
    • Are the suggested tasks equally distributed?
KStoller-WMF moved this task from Estimated tasks backlog to Current Sprint on the Growth-Team board.
KStoller-WMF edited projects, added: Growth-Team (Current Sprint); removed: Growth-Team.
KStoller-WMF updated Other Assignee, added: Sgs.
KStoller-WMF updated the task description. (Show Details)

I think we can consider this task resolved as we have the initial tasks created, and we can refine tasks further as we prepare to pull them into a sprint.