Change Details

This ticket is a collection of the requirements the Editing and Web Teams collectively defined to ensure the Sticky Header meets the needs of people who are editing Wikipedia and transitioning into and away from doing so. === Requirements |Requirement | Blocker (pilot wikis) | Status |Next step | Ticket (if any exists) | --- | --- | --- | --- | --- |Editors, across experience levels, can intuitively identify the editing mode (`source` or `visual`) the edit affordances within the sticky heady refer to, so they know what to do to open the editing interface they prefer.|Yes| Requirement not met| {T289723}|//Ticket for design spike is needed// | Editors, across experience levels, can continue to locate and access the editing tools available to them within VE's toolbar (read: the sticky header should not interfere with or obfuscate the tools within VE's editing toolbar).|Yes| Blocking requirements | No sticky header in VE | |Logged in editors who have explicitly set a preference for the Editing mode setting within `Special:Preferences#mw-prefsection-editing` will notice their preference reflected within the reading mode sticky header.|Yes|Requirement not yet met| Implement functionality|//Ticket needed// |Editors, across experience levels, can easily understand how the different modes (reading/editing) relate to one another so that they can intuitively move between the two.| Yes|//TBD//|Revisit this requirement once the prototype is updated to include the editing experience| | Editors, across experience levels, can easily identify what mode (reading/editing) they are in at all points in their reading/editing "journeys" so they can be confident in what the impact of their actions (read: keystrokes, clicks, etc.) will be.| No| //TBD// | Revisit this requirement once the prototype is updated to include the editing experience| //To be covered by forthcoming usability testing ticket// | Editors, across experience levels, are clear what to do (read: what to click) in order to edit a particular part of the page so they can efficiently navigate to the specific content they are wanting to edit/inspect.| No| //TBD//|Usability test to be run prior to scaling functionality beyond pilot wikis| //Usability testing ticket is needed// === Open questions - [x] 1. Are we trying to promote editing among logged out users? //If "yes," we need to consider displaying the edit affordances within the sticky headers to logged out users.// -- We are neither trying to promote or discourage IP editing with this intervention. Although, considering the Web Team will //not// be deploying the sticky header for logged out users at this time, we are going to pause further conversation about whether the editing affordance should included within the sticky header logged out users see. //More context in T287545#7298923.// === Done - [ ] Each of the `===Requirements` marked as blocking the initial pilot wiki deployment is are met. - [ ] In the `===Requirements` table above, it is noted whether each requirement has been met or not (read: no requirement should have a "//TBD//" status. --- === Links - Brief: [Sticky header](https://docs.google.com/presentation/d/1g7iIJySWiQZlsK6j0UlLehdYOTaF_Ok0W65lBqqaoyo/edit?usp=sharing) - Prototype: [https://di-toc-phase2.web.app/Hokusai](https://di-toc-phase2.web.app/Hokusai) - Discussion notes: [Meeting/Web ↞↠ Editing ](https://docs.google.com/document/d/13xpJsfQadPTjQY780MZ6DXIz-u8f6YvkRFDvne39y8E/edit#) - Requirements drafting doc: [Sticky Header Requirements](https://docs.google.com/document/d/1o4IcKY73gv3XlbNdoDhJUGlZiE_jsDhCrUvMLuvKxvc/edit#)

This ticket is a collection of the requirements the Editing and Web Teams collectively defined to ensure the Sticky Header meets the needs of people who are editing Wikipedia and transitioning into and away from doing so. === Requirements |Requirement | Blocker (pilot wikis) | Status |Next step | Ticket (if any exists) | --- | --- | --- | --- | --- |Editors, across experience levels, can intuitively identify the editing mode (`source` or `visual`) the edit affordances within the sticky heady refer to, so they know what to do to open the editing interface they prefer.|Yes| Requirement not met| {T289723}|//Ticket for design spike is needed// | Editors, across experience levels, can continue to locate and access the editing tools available to them within VE's toolbar (read: the sticky header should not interfere with or obfuscate the tools within VE's editing toolbar).|Yes| Blocking requirements | No sticky header in VE | T289721 |Logged in editors who have explicitly set a preference for the Editing mode setting within `Special:Preferences#mw-prefsection-editing` will notice their preference reflected within the reading mode sticky header.|Yes|Requirement not yet met| Implement functionality|//Ticket needed// |Editors, across experience levels, can easily understand how the different modes (reading/editing) relate to one another so that they can intuitively move between the two.| Yes|//TBD//|Revisit this requirement once the prototype is updated to include the editing experience| | Editors, across experience levels, can easily identify what mode (reading/editing) they are in at all points in their reading/editing "journeys" so they can be confident in what the impact of their actions (read: keystrokes, clicks, etc.) will be.| No| //TBD// | Revisit this requirement once the prototype is updated to include the editing experience| //To be covered by forthcoming usability testing ticket// | Editors, across experience levels, are clear what to do (read: what to click) in order to edit a particular part of the page so they can efficiently navigate to the specific content they are wanting to edit/inspect.| No| //TBD//|Usability test to be run prior to scaling functionality beyond pilot wikis| //Usability testing ticket is needed// === Open questions - [x] 1. Are we trying to promote editing among logged out users? //If "yes," we need to consider displaying the edit affordances within the sticky headers to logged out users.// -- We are neither trying to promote or discourage IP editing with this intervention. Although, considering the Web Team will //not// be deploying the sticky header for logged out users at this time, we are going to pause further conversation about whether the editing affordance should included within the sticky header logged out users see. //More context in T287545#7298923.// === Done - [ ] Each of the `===Requirements` marked as blocking the initial pilot wiki deployment is are met. - [ ] In the `===Requirements` table above, it is noted whether each requirement has been met or not (read: no requirement should have a "//TBD//" status. --- === Links - Brief: [Sticky header](https://docs.google.com/presentation/d/1g7iIJySWiQZlsK6j0UlLehdYOTaF_Ok0W65lBqqaoyo/edit?usp=sharing) - Prototype: [https://di-toc-phase2.web.app/Hokusai](https://di-toc-phase2.web.app/Hokusai) - Discussion notes: [Meeting/Web ↞↠ Editing ](https://docs.google.com/document/d/13xpJsfQadPTjQY780MZ6DXIz-u8f6YvkRFDvne39y8E/edit#) - Requirements drafting doc: [Sticky Header Requirements](https://docs.google.com/document/d/1o4IcKY73gv3XlbNdoDhJUGlZiE_jsDhCrUvMLuvKxvc/edit#)

This ticket is a collection of the requirements the Editing and Web Teams collectively defined to ensure the Sticky Header meets the needs of people who are editing Wikipedia and transitioning into and away from doing so. === Requirements |Requirement | Blocker (pilot wikis) | Status |Next step | Ticket (if any exists) | --- | --- | --- | --- | --- |Editors, across experience levels, can intuitively identify the editing mode (`source` or `visual`) the edit affordances within the sticky heady refer to, so they know what to do to open the editing interface they prefer.|Yes| Requirement not met| {T289723}|//Ticket for design spike is needed// | Editors, across experience levels, can continue to locate and access the editing tools available to them within VE's toolbar (read: the sticky header should not interfere with or obfuscate the tools within VE's editing toolbar).|Yes| Blocking requirements | No sticky header in VE | T289721 |Logged in editors who have explicitly set a preference for the Editing mode setting within `Special:Preferences#mw-prefsection-editing` will notice their preference reflected within the reading mode sticky header.|Yes|Requirement not yet met| Implement functionality|//Ticket needed// |Editors, across experience levels, can easily understand how the different modes (reading/editing) relate to one another so that they can intuitively move between the two.| Yes|//TBD//|Revisit this requirement once the prototype is updated to include the editing experience| | Editors, across experience levels, can easily identify what mode (reading/editing) they are in at all points in their reading/editing "journeys" so they can be confident in what the impact of their actions (read: keystrokes, clicks, etc.) will be.| No| //TBD// | Revisit this requirement once the prototype is updated to include the editing experience| //To be covered by forthcoming usability testing ticket// | Editors, across experience levels, are clear what to do (read: what to click) in order to edit a particular part of the page so they can efficiently navigate to the specific content they are wanting to edit/inspect.| No| //TBD//|Usability test to be run prior to scaling functionality beyond pilot wikis| //Usability testing ticket is needed// === Open questions - [x] 1. Are we trying to promote editing among logged out users? //If "yes," we need to consider displaying the edit affordances within the sticky headers to logged out users.// -- We are neither trying to promote or discourage IP editing with this intervention. Although, considering the Web Team will //not// be deploying the sticky header for logged out users at this time, we are going to pause further conversation about whether the editing affordance should included within the sticky header logged out users see. //More context in T287545#7298923.// === Done - [ ] Each of the `===Requirements` marked as blocking the initial pilot wiki deployment is are met. - [ ] In the `===Requirements` table above, it is noted whether each requirement has been met or not (read: no requirement should have a "//TBD//" status. --- === Links - Brief: [Sticky header](https://docs.google.com/presentation/d/1g7iIJySWiQZlsK6j0UlLehdYOTaF_Ok0W65lBqqaoyo/edit?usp=sharing) - Prototype: [https://di-toc-phase2.web.app/Hokusai](https://di-toc-phase2.web.app/Hokusai) - Discussion notes: [Meeting/Web ↞↠ Editing ](https://docs.google.com/document/d/13xpJsfQadPTjQY780MZ6DXIz-u8f6YvkRFDvne39y8E/edit#) - Requirements drafting doc: [Sticky Header Requirements](https://docs.google.com/document/d/1o4IcKY73gv3XlbNdoDhJUGlZiE_jsDhCrUvMLuvKxvc/edit#)