Change Details

T267444, and eventually T326694, will revise where and how the {nav Add Topic} button appears on talk pages. This task involves the work of instrumenting said {nav Add Topic} button so that we can evaluate who is engaging with it and what they are doing after doing so. //More details below.// === Requirements The {nav Add Topic} is instrumented such that we can know: - The account state of the people who click it (logged in / out) - The experience level (edit count) of the people who click it - The skin version being shown when the button is clicked (i.e. Vector 2010 or Vector 2022) - The editing interface that people see once they click the {nav Add Topic} button - The editing workflow that people use once they click the {nav Add Topic} button (i.e. New Topic Tool or section=new workflow) - Where within the new topic publishing flow people "get to." //Read: do they abandon the workflow before the editing interface loads? Do they abandon the workflow after entering some content into the editing interface? Do they successfully publish an edit? etc.// NOTE: Ideally, this "new" button will be instrumented in the same way(s) the existing {nav Add Topic} button. This includes the same click-logging in `DesktopWebUIActions` and the same add topic workflow instrumentation within `EditAttemptStep` === Open questions - [ ] 1. Considering we're implementing this new {nav Add Topic} button in `Vector (2010)` and `Vector (2022)` separately, does the instrumentation of both need to happen separately as well? Can it happen all in this one task? Something else?

T267444, and eventually T326694, will revise where and how the {nav Add Topic} button appears on talk pages. This task involves the work of instrumenting said {nav Add Topic} button so that we can evaluate who is engaging with it and what they are doing after doing so. //More details below.// === Requirements The {nav Add Topic} is instrumented such that we can know: - The account state of the people who click it (logged in / out) - The experience level (edit count) of the people who click it - The skin version being shown when the button is clicked (i.e. Vector 2010 or Vector 2022) - The editing interface that people see once they click the {nav Add Topic} button - The editing workflow that people use once they click the {nav Add Topic} button (i.e. New Topic Tool or section=new workflow) - Where within the new topic publishing flow people "get to." //Read: do they abandon the workflow before the editing interface loads? Do they abandon the workflow after entering some content into the editing interface? Do they successfully publish an edit? etc.// NOTE: Ideally, this "new" button will be instrumented in the same way(s) the existing {nav Add Topic} button. This includes the same click-logging in `DesktopWebUIActions` and the same add topic workflow instrumentation within `EditAttemptStep` === Open questions - [x] 1. Considering we're implementing this new {nav Add Topic} button in `Vector (2010)` and `Vector (2022)` separately, does the instrumentation of both need to happen separately as well? Can it happen all in this one task? Something else? -- The instrumentation for the {nav Add Topic} button that will appear in `Vector (2010)` and `Vector (2022)` will, ideally, happen in this task assuming the `The skin version being shown when the button is clicked (i.e. Vector 2010 or Vector 2022)` requirement can be met.

T267444, and eventually T326694, will revise where and how the {nav Add Topic} button appears on talk pages. This task involves the work of instrumenting said {nav Add Topic} button so that we can evaluate who is engaging with it and what they are doing after doing so. //More details below.// === Requirements The {nav Add Topic} is instrumented such that we can know: - The account state of the people who click it (logged in / out) - The experience level (edit count) of the people who click it - The skin version being shown when the button is clicked (i.e. Vector 2010 or Vector 2022) - The editing interface that people see once they click the {nav Add Topic} button - The editing workflow that people use once they click the {nav Add Topic} button (i.e. New Topic Tool or section=new workflow) - Where within the new topic publishing flow people "get to." //Read: do they abandon the workflow before the editing interface loads? Do they abandon the workflow after entering some content into the editing interface? Do they successfully publish an edit? etc.// NOTE: Ideally, this "new" button will be instrumented in the same way(s) the existing {nav Add Topic} button. This includes the same click-logging in `DesktopWebUIActions` and the same add topic workflow instrumentation within `EditAttemptStep` === Open questions - [ ] 1- [x] 1. Considering we're implementing this new {nav Add Topic} button in `Vector (2010)` and `Vector (2022)` separately, does the instrumentation of both need to happen separately as well? Can it happen all in this one task? Something else? -- The instrumentation for the {nav Add Topic} button that will appear in `Vector (2010)` and `Vector (2022)` will, ideally, happen in this task assuming the `The skin version being shown when the button is clicked (i.e. Vector 2010 or Vector 2022)` requirement can be met.