VisualEditor on mobile/Section editing

In late 2018, the Editing team conducted user research to understand editors' experiences using the visual editor on the mobile site. The research showed several disruptive workflows and unclear features. These problems make it hard for editors to focus while improving and/or creating an article. Based on this research, the Editing team developed several ideas for improving the visual editor. The goal is to help editors focus on content editing, by reducing distractions and confusion about how to edit on the mobile site.

March 29, 2019
As of yesterday, 28-March, Section Editing is now live for contributors to an additional 10 wikis: Albanian, Arabic, Azerbaijani, Hindi, Indonesian, Malay, Malayalam, Marathi, Persian and Thai. As part of this next phase of the rollout, we began an A/B test in an effort to better understand how Section Editing affects editing behavior.

Q: "How does it work?"

A: "The A/B tests works such that 50% of contributors to the wikis above will not – for now – experience Section Editing, while the other 50%of contributors to the wikis above will experience Section Editing. You can see the technical details of how the experiment is being implemented in this ticket: T218851."

March 19, 2019
Section Editing is now live on Bengali, Hebrew and Cantonese wikis for contributors editing on mobile, using VE. Increasingly larger rollouts are planned for the next several weeks.

March 15, 2019
The user test that began on February 25 is now closed. As you begin to experience Section Editing in the wild (spoiler), please know your comments, questions, challenges and critiques will continue to be welcomed and listened for on the Discussion page.

March 13, 2019
Quick update here: ~2 days from now, on Friday, March 15, we will be “concluding” the comparative Section Editing test that’s been running over the past two weeks (see above).

“Concluding," in this context, means removing the "Test Instructions" section above and, in its place, sharing the outcomes of this test.

February 25, 2019
Updated instructions to now include an A/B test format.

January 11, 2019
Added instructions for first section editing prototype. This works on mobile and desktop. Please follow the instructions and then add your feedback.

Section editing
After collecting community feedback on our ideas and conducting a usability test, the Editing team chose to fix section editing.

Existing workflow:


 * 1) Decide what you want to change, while reading the article on a mobile device.
 * 2) Then, scroll around the page to find the button that opens the editing screen.  Sometimes, editors have to scroll through many screenfuls of an article to find the button.
 * 3) Once the editing screen is open, scroll back down to find the part of the article that you want to change.  Sometimes, editors can't find the place that they wanted to change.

We believe scrolling a long distance to find the edit button is distracting. Instead, once you know what change you want to make, you should automatically be guided to the edit command function for the part of the article you want to change. This approach is called Section Editing.

The Section Editing feature for mobile will let you change any section of an article by tapping a contextual edit button. When you tap the contextual button, you will be transported from reading to editing, in the same part of the article that you were reading. You will not need to scroll as much and potentially lose your place.

User testing
Between February 25 and March 15, we invited contributors, new and experienced, to test two interactive section editing prototypes, each populated with the same test article.

Participants were instructed to navigate to a particular section within the test article, initiate the editor, complete an edit and compare their experiences with both prototypes.

The entire test was unmoderated and intended to gauge how Section Editing impacted contributors’ experience:


 * 1) Starting an edit
 * 2) Locating the content they intended to edit within the editing interface
 * 3) Completing their edit

Over the course of these ~2 weeks, 10 people participated. The feedback that surfaced can be found on this discussion page.

Feedback
We are interested in your thoughts on the prototype. Is this a better experience? Was it easier for you to stay focused on where you were within your edit? Was this expected behavior? Any and all comments are appreciated! Feedback will be summarized on the main project page.