Change Details

This task is about designing what the user experiences in the editing context. This will evolve even as engineers begin to prototype the experience. At first, we only need to design the desktop experience. We will roll out a mobile experience after looking at the initial results from desktop. An information source that could be useful in the design is our translations of portions of the Czech and Korean help desks done in T197190. @RHo will own and drive this task, potentially making sub-tasks and mock-ups. Below are notes from previous conversations with the team around design. * How prominent should the call to action be, and where on the page should it be located? * How should the call to action be different (if at all) between the visual and wikitext editor experiences? * After clicking on the new feature, what options should the user be presented with? * Should the user be directed to the help desk, or should they be allowed to type and submit their question right from the editing experience? * What should the exact language be inside the feature? * Can a user dismiss this feature for good?

== Background + Hypothesis The Growth team will be adding a prompt allowing users to ask for help when they are in the context of editing an article, with the hypothesis that: (A) Users are more likely to seek help when presented with an easy way to submit their questions; and (B) Users are more likely to successfully complete an edit by knowing where to seek help. == User job story **When** I am editing an article and am unsure about how to proceed... **...I want to** get help while I am doing the editing task... **...so that I** can confidently complete the edit. == Prep tasks - {T206713} - {T206714} == Proposed design TBC after prep tasks are completed. === Sub-tasks - Conduct user testing of initial in-context help UI designs - Create copy document for the in-context help UI copy to be reviewed and ready for translation on TWN -------- ==== Notes from previous conversations with the team around design. * At first, we only need to design the desktop experience. We will roll out a mobile experience after looking at the initial results from desktop. * How prominent should the call to action be, and where on the page should it be located? * How should the call to action be different (if at all) between the visual and wikitext editor experiences? * After clicking on the new feature, what options should the user be presented with? * Should the user be directed to the help desk, or should they be allowed to type and submit their question right from the editing experience? * What should the exact language be inside the feature? * Can a user dismiss this feature for good? -------- ==== Relevant links - T197190 - translations of top new users questions on CS and KO Help Desk

This task is about designing what the user experiences in the editing context.== Background + Hypothesis The Growth team will be adding a prompt allowing users to ask for help when they are in the context of editing an article, with the hypothesis that: (A) Users are more likely to seek help when presented with an easy way to submit their questions; This will evolve even as engineers begin to prototype the experienceand (B) Users are more likely to successfully complete an edit by knowing where to seek help. At first, we only need to design the desktop experience. We will roll out a mobile experience after looking at the initial results from desktop.== User job story **When** I am editing an article and am unsure about how to proceed... **...I want to** get help while I am doing the editing task... **...so that I** can confidently complete the edit. == Prep tasks - {T206713} - {T206714} An information source that could be useful in the design is our translations of portions of the Czech and Korean help desks done in T197190== Proposed design TBC after prep tasks are completed. @RHo will own and drive this task, potentially making sub-tasks and mock-ups. Below are notes from previous conversations with the team around design.=== Sub-tasks - Conduct user testing of initial in-context help UI designs - Create copy document for the in-context help UI copy to be reviewed and ready for translation on TWN -------- ==== Notes from previous conversations with the team around design. * At first, we only need to design the desktop experience. We will roll out a mobile experience after looking at the initial results from desktop. * How prominent should the call to action be, and where on the page should it be located? * How should the call to action be different (if at all) between the visual and wikitext editor experiences? * After clicking on the new feature, what options should the user be presented with? * Should the user be directed to the help desk, or should they be allowed to type and submit their question right from the editing experience? * What should the exact language be inside the feature? * Can a user dismiss this feature for good? -------- ==== Relevant links - T197190 - translations of top new users questions on CS and KO Help Desk