Page MenuHomePhabricator

Encourage editors to make a follow-up contribution after publishing a previous one
Open, LowestPublic

Description

Currently, when editors save an edit, they are redirected to the "read" view of the article, which is not encouraging them to continue editing. Right after publishing an edit seems a good time to propose a relevant follow-up contribution for the user to make. For example, after contributing a new paragraph of content, the system can propose to add a reference or an image to improve the quality of the contribution as a next step.

A possible execution of the idea is illustrated below:

Picking a follow-up action allows for the system to provide additional guidance on how o do such activity and why it is important for the project. This will help to educate new editors about key concepts that make a good contribution, reducing their chances of being reverted and abandoning.

Considerations

  • Focus on new editors. We may want to show only the follow-up suggestions to new editors. More experienced editors may just get a more general "continue editing" call to action or nothing at all if it is considere distracting.
  • Suggested tasks should be relevant. For example, we should not suggest to add a reference if the user already did so.
  • Messaging should be positive. Follow-up activities should be presented as ways to improve the previous contribution, even if they represent improvement that reflect something missing that makes the contribution likely to be reverted.

Impact
Research (including New-Editor-Experiences research) shows that new editors have issues understanding key contribution principles (verifiability, copyright, etc.) and that they learn iteratively. As opposed to reading the manual in advance, proposing specific ways to improve their contributions can be an applied way to learn these concepts one at a time.

It would be great to measure the impact at both short and long terms, measuring (a) how many new contributions are made because of this new suggestion, and (b) the effects in retention for these users.

Event Timeline

kostajh added a subscriber: kostajh.

Growth-Team discussed in triage today, we like this idea but can't take it on in the short-to-medium term. We will revisit it.

Which code base is this task supposed to be about?

@Aklapper in theory it would be done in GrowthExperiments but we are not planning on doing anything with this right now.

That said, those interested in this task would probably be interested in T245790: Newcomer tasks: post-edit dialog too.

Aklapper triaged this task as Lowest priority.Mar 20 2020, 1:49 PM
Aklapper added a project: GrowthExperiments.

Thanks! In that case I'll boldly add GrowthExperiments. :)

RHo added a subscriber: RHo.

Tagging with Growth Design to track this idea for revising the "post-edit" dialog as an in-page prompt instead of an overlay