Growth/Newsletters/14

Welcome to the fourteenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Success with guidance

edit
 
The star on this image is the week we deployed "guidance".

We deployed the "Guidance" feature on June 15.

This feature uses the help panel to explain what to do after selecting a suggested edit. For instance, if a newcomer selects a copyedit task, they are guided on what sorts of errors to look for. They can see examples of how to rewrite the text. You can try this feature on test.wikipedia.org. First enable the homepage and the help panel in your preferences there.

Since we launched "Guidance", the data we collected show good results (see image). Now, we see more users completing suggested edits than before Guidance was deployed.

Structured tasks

edit
 
Design concept for the "add a link" structured task

Structured tasks is a project that aims to break down editing workflows into a series of steps. We hope newcomers can accomplish these tasks easily.

In the previous newsletter, we asked for feedback from community members on the idea. We had a good discussion in six languages with 35 community members (summary here). We have now posted new design mockups. We hope community members can check the mockups out and react to them (in any language). They are posted along with some of the main questions we are thinking about as we continue to refine our plans.

Other technical updates

edit
 
Mockup of Variant D of the homepage on desktop.
  • We are currently working on Variants C and D (adjacent image) of the homepage. The goal is to increase the number of newcomers who start the newcomer tasks workflow. This is the team's main project at the moment.
  • We've made it easier to hide the help panel when not needed. [1]
  • The welcome survey has a new question for people who created their account: language skills. The goal is to find out how many newcomers know multiple languages, so that we can learn whether it is a good idea to integrate Content Translation as a newcomer task. To make room for this question, we removed one that is not being used. [2]

Community outreach

edit

Growth team's newsletter prepared by the Growth team and posted by botGive feedbackSubscribe or unsubscribe.