===Goal:
Increase the percentage of newcomers activating via Suggested editsinteracting with the and choosing articles from the suggested edits module, and ultimately increase the percentage of newcomers saving edits via the workflow. This distinction is important because it is theoretically possible for us to come up with designs that grab more people into the workflow, but don't give them context to know how to complete the workflow.
===Background
When Suggested editsnewcomer tasks was first introduced to the newcomer homepage, an experiment waswe conducted around how newcomers were introduced to the feature.
our first variant test: {T238888}
* **Variant A **** newcomers had to "initiate" the Ssuggested edits module on their homepage by selecting a call to action in the Start module and proceeding through two onboarding overlays that introduced them to the content.
* **Variant B** saw the Ssuggested edits module right from the starttheir arrival ('pre-initiated') and didn't see the onboarding overlays.
===Hypothesis
OThe first variant test taught us that a more prominent module can attract more interaction. But we also think it showed that onboarding (introducing the concept of "S"suggested edits") is an important part of converting newcomers who interact with Ssuggested edits, to saving a suggested edit task.
By combining the best of the two previous variants where users are both taken through onboarding (groupVariant A) **and** have prominent Ssuggested edits content by default (group BVariant B), more newcomers will activate via Suse suggested edits.
==== Proposal
Test two new variants, **Variant C** and **Variant D**, to see whether the emphasis on 'onboarding' content or prominence of the SE call to action leads to higher edit activation.
**Mocks:** https://wikimedia.invisionapp.com/overview/Variants-C-G-SE-top-of-funnel-tests-ck77r3arw00ea012a8bk1bh0v/screens?v=jXSLq0KIm0I3Xnr7YR5nPw%3D%3D
//Redlined versions will be shared in the Growth Zeplin board (tagged with `Variant-Pre-initiatedSE`)//
> **Takeaways from Var A vs B that inform this Var C vs D test:**
> **1. More prominent SE module increases interaction.**
> This finding applied as best practice in variants C and D. Both focus on driving editing as the core goal of the newcomer experience. As part of this, the Start module will be removed to center onboarding and orientation on Suggested edits instead.
> **2. Onboarding is also important.**
> Despite variant B causing interactions to double, navigating only went up by 60%, and clicking only went up by 30%. It is inferred that whilst people seeing the pre-initated feature try it out, these ‘uninformed’ interactions cause more drop outs. This is where the onboarding info in variant A seems to play an important role in user engagement. This interpretation is supported by indicative results (i.e., not measured for statistical relevance) further down the funnel (edit attempts and completed edits are higher on var A).
> **3. Mobile SE preview design should be more actionable.**
> Mobile variant B performed slightly worse than variant A, meaning the SE preview card design isn’t encouraging discovery.
==== Proposal
Test two new variants, **Variant C** and **Variant D**, to see whether the emphasis on 'onboarding' content or prominence of the SE call to action leads to higher interaction and editing.
**Mocks:** https://wikimedia.invisionapp.com/overview/Variants-C-G-SE-top-of-funnel-tests-ck77r3arw00ea012a8bk1bh0v/screens?v=jXSLq0KIm0I3Xnr7YR5nPw%3D%3D
//Redlined versions will be shared in the Growth Zeplin board (tagged with `Variant-Pre-initiatedSE`)//
Note: the variants for mobile and desktop are not strictly comparable. They are similar in spirit, but can be essentially thought of as four different variants. This Phab task will refer to them as "Variant C-desktop", "Variant D-desktop", "Variant C-mobile", and "Variant D-mobile".
**WORK IN PROGRESS**
=== Specifications for desktop
* **Both variants**
** Start module reduced to only the email submodule (with same business rules from the collapsible start module detailed on T219391)
** The initialized suggested edits module will be large-sized, on left side of homepage. It will display the card feed once it's initialized.
* **Variant C-desktop**
** Suggested edits module
*** The initiated suggested edits module is just present on the page upon arrival, including the pulsing blue dot on the topic filter.
*** The module has an "i" icon in the upper right, which opens up the "Onboarding" sequence described below.
** Popup
*** When the user first arrives on their homepage, they will see a popup on top of the page that is pointing to the "Hello, [USERNAME]!" header.
*** Header: TBD
*** Body: TBD
*** The popup is dismissable with an "X" in the upper right and also by clicking on the screen outside of it.
*** In the lower right, it has a blue arrow button, which initiates the onboarding.
** Onboarding
*** When the user clicks the blue arrow button on the popup, they see the first of two onboarding overlays. The first one is an intro overlay with exact content TBD. It does not have topic selection inside the overlay like in Variant A.
*** They can dismiss the overlay by clicking away.
*** They can click "Continue" to go to the next overlay.
*** The second overlay is the exact same difficult overlay as implemented in T235723 for Variant A. Its back button returns to the previous overlay.
*** When the user clicks "Done", the overlays and popup are gone, and the user is just on their homepage.
** Instrumentation
*** TBD
* **Variant D-desktop**
** Welcome message
*** At the top of the homepage is a banner welcoming the user to the homepage.
*** Header: TBD
*** Body: TBD
*** The banner is dismissable with an "X". After it is dismissed, it can never be resurrected.
**WORK IN PROGRESS**
=== Tasks****
*** The user arrives to see the "topic overlay" content inside the suggested edit module's large slot, as opposed to in any sort of overlay.
* Variant C
** Create read-only topic onboarding overlay for Desktop and Mobile
** Desktop - Add a general homepage welcome pop-up for Desktop which initiates onboarding overlays
** Mobile - Add a mobile drawer/peep welcome drawer which initiates onboarding
** Add a "i" icon on the Suggested edits module
* Variant D
**Add a dismissible Welcome message above the homepage content (Desktop and Mobile)
**Create a pre-initiated version of the SE module that integrates the topic and task type overlays
**Create a Mobile SE preview card for the pre-initiated version of Suggested Edits
* Apply UI changes that apply to both variants C and D
** Desktop SE module - wider column layout
** Mobile SE preview card after it has been initiated
** Start module reduced to only the email submodule (with same business rules from the collapsible start module detailed on T219391)
** Style updates to the Impact module when there are 0 edits
*Instrumentation for variant tests