Growth/Communities/Get the Growth experiments on your wiki

The Growth team experiments with new features on a small set of "target" Wikipedias (Czech, Korean, Vietnamese, Arabic). When we believe that features likely have a positive impact, we allow other wikis who want to try new things to deploy those features. As of June 2019, the features that are included in this set are:


 * EditorJourney
 * Welcome survey
 * Help panel

The newcomer homepage is the next feature to be part of this list. This page also includes steps to configure the newcomer homepage, though the team is not yet sure it is ready to be deployed on more wikis.

Conditions
As detailed on our focus, we will work with the following wikis by order of priority:


 * 1) Wikipedias we in the set of our "target" wikis (Czech, Korean, Vietnamese, Arabic) – we address all the feedback they give us.
 * 2) Mid-sized Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.
 * 3) All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.

Bug reports will be prioritized by the Growth team.

Features will be deployed as "experiments", meaning that a portion of newcomers will receive the features (the treatment group), and a portion will not (the control group). By comparing these two groups, we will be able to measure the impact of the feature on newcomer retention.

The prerequisites to get the experiments are listed below and they are summarized in the Phabricator template.

Phabricator task template
[https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=Growth-team&subscribers=Trizek-WMF&description={{urlencode:

First
[ ] Post on Village Pump and reach consensus [ ] Have a group of people who will enroll in this project as mentors (helping on the help desk or as direct mentors)

Translations
[ ] [|Translate the privacy policy] [ ] [|Translate the interface] (on translatewiki.net, needs a specific account) [ ] Translate the documentation [ ] [first day] [ ] [first day/Newcomer homepage] [ ] [first day] [ ] [on help desk] [ ] [on help desk/Help panel] [ ] [to work with newcomers on help desks] [ ] [to introduce yourself as a mentor] [ ] Translate aliases for the interface: * "WelcomeSurvey" = * "Homepage" = * "Impact" = * "View more" =

Help panel
* Provide the URL of your help desk and the page title = * Explain how your Help desk is archived = * Provide the 5 most important help pages newcomers should have access to, and the label people will read (for instance "how to add an image"). =   *    *    *    *    *  * On which namespaces it have to be deployed = * Which namespace(s) and/or categories the Help panel search should handle (0 is mandatory) = * What is the wikilink to the main help page =

Homepage
* Provide the URL of your tutorial about editing and the page title =

Mentors
> Please introduce yourself in a short way (240 characters max) so that newcomers will know more about you. To increase focus, your message will not render wikitext or links. See examples and best practices.
 * Create if necessary or update the mentors list
 * the format is `User:Name|Description` (be careful about the position of the `|` in the example!)
 * add the following sentence at the top:
 * Provide the homepage mentors list title =

Understanding First Day

 * The list of namespaces that would be monitored (0, 1, 6, 7 are mandatory). = }} ]

Community
To get the experiments you have to:


 * 1) Develop community consensus
 * 2) * it is a discussion organized by the community
 * 3) * that discussion must explain:
 * 4) **what the features are
 * 5) **what are the conditions to get them
 * 6) *The discussion must lead to a community decision to get the features deployed
 * 7) Contact the Growth team (in English) to show your interest and inform the team about the start of the process
 * 8) Do community building
 * 9) * identify community members who the Growth team can contact with questions or needs while deploying features
 * 10) * make sure there are community members ready to help with answering questions on the help desk
 * 11) Create a Phabricator task using the template. It will include the following elements:
 * 12) *Translations: say if they are done and provide the aliases
 * 13) *Configuration: list all necessary links and language
 * 14) *Add the  Phabricator tag to the task

Please note that the Growth team may not be able to deploy some features on a given wiki. Some of the reasons can be (among others not listed):


 * if it takes too much time to implement some features on a wiki (requesting a specific deployment, or fixing something),
 * if there are not enough community members to answer newcomer questions.

Translations
Translations of the following elements are mandatory to start the deployments:


 * Translate the privacy policy on Meta
 * Translate the New User Survey Privacy Statement on a userspace sub-page
 * Translate the interface (on translatewiki.net, needs a specific account)
 * Translate the documentation
 * Growth/Personalized first day
 * Growth/Personalized first day/Newcomer homepage
 * Growth/Understanding first day
 * Growth/Focus on help desk
 * Growth/Focus on help desk/Help panel
 * Growth/Communities/How to work with newcomers on help desks
 * Translate aliases for the interface, and list them in the Phabricator task:
 * "WelcomeSurvey"
 * "Homepage"
 * "Impact"
 * "View more"

Overall

 * Provide the help desk title

Help panel

 * What is the URL of your help desk?
 * Is your help desk a traditional page or a Flow page?
 * How is your help desk archived? By bot? Manually? Weekly? Yearly? Does it has a special configuration, like subpages  or a template like  ?
 * What are the 5 most important help pages newcomers should have access to, and what are the labels for those links.
 * We advise you to review those pages and enrich them. For instance, check if the page is well illustrated, if it presents the different steps needed to achieve something or if it explains how to edit using the visual editor.
 * We recommend including a link to a step-by-step tutorial.
 * We recommend including a link about how to add images to articles. It is a popular request.
 * Those pages can be changed after the deployment. We can provide you some data about how popular they are.
 * Which namespace(s) and/or categories the help panel search should look in, e.g. the "Wikipedia" and "Help" namespaces, or any pages with "Category:Help document".
 * What is the wikilink to the main help page

Homepage

 * Everything that is done for the Help panel, plus:
 * What is the wikilink to the tutorial about editing
 * What is the wikilink to the list of newcomers
 * Mentors:
 * Create a page where experienced users can sign up to be mentors.
 * The format of the page is a list of mentors, using wikilinks (format is
 * Protect that page, so that only experienced users can sign-up
 * We recommend having one mentor for every 500 new accounts per month, i.e. if your wiki has 5,000 new accounts per month, you should have 10 mentors signed up in order to handle the volume of incoming questions. Have more mentors than the recommended threshold will decrease the effort needed.

Understanding First Day

 * The list of namespaces that contain sensitive behavior that we don't want to record (0, 1, 6, 7 are mandatory).

Configuration values
As information, these are all the configuration values we set when deploying to a new wiki ( in the sample below): 'wmgUseGrowthExperiments' => [ 'default' => false, 'newwiki' => true ], 'wgWelcomeSurveyEnabled' => [ 'default' => false, 'newwiki' => true, ], 'wgWelcomeSurveyPrivacyPolicyUrl' => [ 'newwiki' => ' https://foundation.wikimedia.org/wiki/{needs to be obtained per wiki}', ], 'wgWelcomeSurveyExperimentalGroups' => [ 'newwiki' => [ 'exp2_target_specialpage' => [ 'range' => '0-9' ], 'exp2_target_popup' => [ 'range' => 'x' ] ], ], 'wgGEHelpPanelEnabled' => [ 'default' => false, 'newwiki' => true, ], 'wgGEHelpPanelSearchEnabled' => [ 'default' => false, 'newwiki' => true, ], 'wgGEHelpPanelNewAccountEnablePercentage' => [ 'default' => 0, 'newwiki' => 50, ], 'wgGEHelpPanelReadingModeNamespaces' => [ 'default' => [ 2, 4, 12 ] ], 'wgGEHelpPanelHelpDeskTitle' => [ 'default' => '' , 'newwiki' => '{MW Help desk title. Can use a template, e.g. 위키백과:질문방/ ', ], 'wgGEHelpPanelViewMoreTitle' => [ 'default' => '' , 'newwiki' => '{MW Title for help contents}', ], 'wgGEHelpPanelLinks' => [ 'default' => [], 'newwiki' => [ [ 			'title' => '{MW Title}', 'text' => 'Display text', 'id' => 'unique-identifier-for-event-logging', ],               // 4 more of the above ], ], 'wgGEHomepageEnabled' => [ 'default' => false, 'newwiki' => true, ], 'wgGEHomepageNewAccountEnablePercentage' => [ 'default' => 0, 'newwiki' => 50, ], 'wgGEHomepageTutorialTitle' => [ 'default' => '' , 'newwiki' => '{MW title for the homepage tutorial}', ], 'wgGEHomepageMentorsList' => [ 'default' => '' , 'newwiki' => '{MW title with list of mentors for homepage feature}', ], Additionally, for UnderstandingFirstDay, we need: 'wgWMEUnderstandingFirstDay' => [ 'default' => false, 'newwiki' => true, ], 'wgWMEUnderstandingFirstDaySensitiveNamespaces' => [ 'default' => [ 0, 1, 6, 7 ], 'newwiki' => [ 0, 1, 6, 7, 118, 119 ], ], Finally, we need to define Special page aliases: $specialPageAliases['newwiki'] = [ 'WelcomeSurvey' => [ '' ], 'Homepage' => [ '' ], 'Impact' => [ '' ], ];