T203151 introduced an affordance that enables people to edit an entire page on mobile using the Visual Editor (see below), as opposed to editing one section at a time.
This task involves the work of making this affordance/ability easier for people to discover
Stories
As someone motivated to make a change to the article I’m reading on mobile web, I want to be able to edit any part of the page — regardless of which Edit button I tapped — so that I can easily locate the part of the article I'm seeking to change and maintain a sense of forward momentum that could be "blunted" by needing to navigate back out of the editor if/when I come to find the content I'm trying to change is located in a section that's different from the one the Edit button I tapped is associated with.
Hypothesis
What follows is *DRAFT* language that will be finalized in Q2 experiments addressing mobile web editing experience and eventually published on-wiki.
If we enable people on mobile web to edit any article section, regardless of which edit icon they first tap, then mobile edit abandonment (for newer editors) will decrease by ##% because they will be able to more more easily reach and modify the content they tapped edit intending to change.
Current state
Considerations
- The current app behavior opens section editing when selecting each edit button in the article. We need to decide if we want consistency between web and app.
- Another consideration is whether we want this behavior to be consistent between visual and source modes. There’s different trade-offs there from visual:
- Source has far less of a performance concern to load the entire page
- Scrolling through huge amounts of wikitext on a small screen is much more unfriendly
- Automatically scrolling to the start-of-a-section isn’t really possible in source
Potential approaches
- Approach #1: By default, only load section you tapped edit button for and sections immediately before and after, load rest of article in the background. If someone scrolls to section that's not yet loaded, we can approach this by one of the following:
- a) Using a skeleton while loading non-loaded sections
- b) Expose an affordance that would enable them to load the next section while scrolling (e.g. a button to load next section)
Approach #2: only load the section related to the edit button someone tapped. When they scroll/reach the boundaries of sections loaded, load subsequent sections.Approach #3: when someone taps "Edit", use a dropdown menu to let them choose editing the full-page or just that single section.