Change Details

//⚠️This is a tracker task to figure out what is needed to more "finely" instrument the mobile VE edit flow in order to better understand how contributors move "through" it.// --- We intend for the improvements we are making to the mobile VE editing toolbar and the steps within the edit flow [1] to help a greater number of people complete their edits. In order for us to be able to evaluate how effective our efforts have been, we'll need to be able to answer: //How do people "move through" the edit flow?// And for us to be able to answer this question, we'll need instrumentation to track the actual actions/steps contributors are taking within the "edit flow". Currently, **we know:** - When the editing interface starts to load: `init` - When the editing interface is ready to be interacted with: `ready` - When a contributor //tries// to save an edit: `saveAttempt` - When a contributor //successfully// saves an edit: `saveSuccess` - When a contributor //unsuccessfully// ties to save an edit: `saveFailure` - When a contributor aborts their edit: `abort` -- The conditions under which a contributor aborts. Examples: --- No changes have been made: `nochange` --- Editor has be initialised but is not yet ready: `preinit` --- User is switching from one editor to another, retaining changes: `switchwith` --- User is switching from one editor to another, discarding changes: `switchwithout` --- User is switching from one editor to another, and the content block is unchanged / transaction stack is empty: `switchnochange` --- User is exiting the editor, discarding changes: `abandon` --- User is exiting the editor, discarding changes, after a saveAttempt has been initiated but before saveSuccess/saveFailure.": `abandonMidsave` Source: [Schema:EditAttemptStep](https://meta.wikimedia.org/wiki/Schema:EditAttemptStep) After this work is complete, **we would like to know:** //⚠️This section being completed depends on this task being completed: T229030// - When a contributor "starts" an edit -- "Starts" could mean when a contributor makes any kind of change to the article - When a contributor advances to the "Save your changes" screen - When a contributors goes "back" -- From what view are they going "back" from - When a contributor taps to "Preview"/"Review" their changes -- This is likely to change considering we are planning to show the visual diff screen view by default. See the description of: T229030 This work also relates to our investigation into mobile VE's loading performance: T227930. --- 1. {T211255}

//⚠️This is a tracker task to figure out what is needed to more "finely" instrument the mobile VE edit flow in order to better understand how contributors move "through" it.// --- We intend for the improvements we are making to the mobile VE editing toolbar and the steps within the edit flow [1] to help a greater number of people complete their edits. In order for us to be able to evaluate how effective our efforts have been, we'll need to be able to answer: //How do people "move through" the edit flow?// And for us to be able to answer this question, we'll need instrumentation to track the actual actions/steps contributors are taking within the "edit flow". Currently, **we know:** - When the editing interface starts to load: `init` - When the editing interface is ready to be interacted with: `ready` - When a contributor advances to the "Save your changes" screen/dialog: `saveIntent` - When a contributor //tries// to save an edit: `saveAttempt` - When a contributor //successfully// saves an edit: `saveSuccess` - When a contributor //unsuccessfully// ties to save an edit: `saveFailure` - When a contributor aborts their edit: `abort` -- The conditions under which a contributor aborts. Examples: --- No changes have been made: `nochange` --- Editor has be initialised but is not yet ready: `preinit` --- User is switching from one editor to another, retaining changes: `switchwith` --- User is switching from one editor to another, discarding changes: `switchwithout` --- User is switching from one editor to another, and the content block is unchanged / transaction stack is empty: `switchnochange` --- User is exiting the editor, discarding changes: `abandon` --- User is exiting the editor, discarding changes, after a saveAttempt has been initiated but before saveSuccess/saveFailure.": `abandonMidsave` Source: [Schema:EditAttemptStep](https://meta.wikimedia.org/wiki/Schema:EditAttemptStep) After this work is complete, **we would like to know:** //⚠️This section being completed depends on this task being completed: T229030// - When a contributor "starts" an edit -- "Starts" could mean when a contributor makes any kind of change to the article - When a contributors goes "back" -- From what view are they going "back" from - When a contributor taps to "Preview"/"Review" their changes -- This is likely to change considering we are planning to show the visual diff screen view by default. See the description of: T229030 This work also relates to our investigation into mobile VE's loading performance: T227930. --- 1. {T211255}

//⚠️This is a tracker task to figure out what is needed to more "finely" instrument the mobile VE edit flow in order to better understand how contributors move "through" it.// --- We intend for the improvements we are making to the mobile VE editing toolbar and the steps within the edit flow [1] to help a greater number of people complete their edits. In order for us to be able to evaluate how effective our efforts have been, we'll need to be able to answer: //How do people "move through" the edit flow?// And for us to be able to answer this question, we'll need instrumentation to track the actual actions/steps contributors are taking within the "edit flow". Currently, **we know:** - When the editing interface starts to load: `init` - When the editing interface is ready to be interacted with: `ready` - When a contributor advances to the "Save your changes" screen/dialog: `saveIntent` - When a contributor //tries// to save an edit: `saveAttempt` - When a contributor //successfully// saves an edit: `saveSuccess` - When a contributor //unsuccessfully// ties to save an edit: `saveFailure` - When a contributor aborts their edit: `abort` -- The conditions under which a contributor aborts. Examples: --- No changes have been made: `nochange` --- Editor has be initialised but is not yet ready: `preinit` --- User is switching from one editor to another, retaining changes: `switchwith` --- User is switching from one editor to another, discarding changes: `switchwithout` --- User is switching from one editor to another, and the content block is unchanged / transaction stack is empty: `switchnochange` --- User is exiting the editor, discarding changes: `abandon` --- User is exiting the editor, discarding changes, after a saveAttempt has been initiated but before saveSuccess/saveFailure.": `abandonMidsave` Source: [Schema:EditAttemptStep](https://meta.wikimedia.org/wiki/Schema:EditAttemptStep) After this work is complete, **we would like to know:** //⚠️This section being completed depends on this task being completed: T229030// - When a contributor "starts" an edit -- "Starts" could mean when a contributor makes any kind of change to the article - When a contributor advances to the "Save your changes" screen - When a contributors goes "back" -- From what view are they going "back" from - When a contributor taps to "Preview"/"Review" their changes -- This is likely to change considering we are planning to show the visual diff screen view by default. See the description of: T229030 This work also relates to our investigation into mobile VE's loading performance: T227930. --- 1. {T211255}