This task involves the work of hiding Vector 2022's Tools and Appearance menus for a subset of people while they are editing with the visual editor (desktop).
This work is prompted by a need for two things to be true for volunteers:
- They feel like they have sufficient space (width) to make changes
- They are able to see Edit Checks in close proximity to the content they're related to without any part of the editable content being obfuscated/affected
Story
As someone who is new to editing Wikipedia and who is attempting to make a change that causes an Edit Check to activate, I need to be able to A) understand what change/content the Check I'm seeing is related to, B) continue focusing on what I had been before the Check appeared, and C) have sufficient space/width to work within so that I can make changes that are aligned with project policies in an environment I feel comfortable working within
Requirements
- For people who are i) logged out, ii) have made ≤100 cumulative edits and are editing at a Wikipedia project in a namespace where Edit Check is available:
- Hide the Tools and Appearance menus when they open the visual editor on desktop, regardless of whether they have a user preference set to show these menus in all other circumstances/contexts
- Make it impossible for people to "pin" the Tools and Appearance menus when this stte is entered
- Show the Tools and Appearance menus when people exit the visual editor, provided they have a user preference set to show these menus
- In implementing "1.A." no changes ought to be made to the user preferences people have set
Open questions
- 1. What methods of "opening the visual editor" ought to cause the Tools and Appearance menus to be hidden?
- 2. At what point during the transition from someone opening the visual editor (desktop) and the visual editor being ready are the Tools and Appearance menus meant to be hidden?
- 3. What ought to happen when someone cancels an edit session? How – if at all – should this experience vary by when people abort an edit session? E.g. before the editing interface fully loads? After someone has made some changes and before they attempt to publish them? Etc.
User experience
TBD