Change Details

== CONTEXT This ticket fleshes out the set of data-driven questions that can help us to understand both how to: - Measure the new tool's impact on the edit metrics ecosystem - Optimize tool design == DATA QUESTIONS - How often are users opening and closing the Preview window inside the Wikitext code editor? - How often are users being defaulted to the Manual Reload experience rather than the auto-load experience? - Which method are users opting for previewing their edits, shortcut or button? - What's the average load time for a refresh? - How often are users encountering the error view? === Downstream impact: Analysis that can come after - How many people successfully publish an unreverted edit after they use realtime preview? === IMPLEMENTATION PLAN TO BE FLESHED OUT BASED ON QUESTIONS To come <- Task can be edited by engineer

== CONTEXT This ticket fleshes out the set of data-driven questions that can help us to understand both how to: - Measure the new tool's impact on the edit metrics ecosystem - Optimize tool design == DATA QUESTIONS - How often are users opening and closing the Preview window inside the Wikitext code editor? - How often are users being defaulted to the Manual Reload experience rather than the auto-load experience? - Which method are users opting for previewing their edits, shortcut or button? - What's the average load time for a refresh? - How often are users encountering the error view? === Downstream impact: Analysis that can come after - How many people successfully publish an unreverted edit after they use realtime preview? === IMPLEMENTATION PLAN TO BE FLESHED OUT BASED ON QUESTIONS To come <- Task can be edited by engineer === New Instrumentation |Proposed new event name|Action that will trigger new event|Schema where event will be logged |---|---|--- |//TBD//|//TBD//|//TBD// === Implementation Process |Step | People/Team Responsible|Description|Status |---|---|---|--- |1. | #community-tech | File ticket requesting instrumentation | ✅ Done in T306176 |2. | #community-tech | Populate the `===New instrumentation` section with proposed changes, once defined | |3. | @mneisler + @dlynch | Review the `===New instrumentation` Community Tech is proposing to introduce| |4. | #community-tech | Implement the instrumentation changes defined in `===New instrumentation` | |5. | #editing-team | Code review the instrumentation changes Community Tech will have implemented | |6. | #community-tech | Verify newly instrumented events are being emitted as expected by clients | |7. | #product-analytics | Verify newly instrumented events are being logged in database as expected, once the new instrumentation has landed in production. | |8. | #community-tech | Update schema documentation with the events spec'd in this task once they have been verified to be implemented as expected. //Read: clients are emitting events as expected and said events are being logged in the database as expected as well.//|

== CONTEXT This ticket fleshes out the set of data-driven questions that can help us to understand both how to: - Measure the new tool's impact on the edit metrics ecosystem - Optimize tool design == DATA QUESTIONS - How often are users opening and closing the Preview window inside the Wikitext code editor? - How often are users being defaulted to the Manual Reload experience rather than the auto-load experience? - Which method are users opting for previewing their edits, shortcut or button? - What's the average load time for a refresh? - How often are users encountering the error view? === Downstream impact: Analysis that can come after - How many people successfully publish an unreverted edit after they use realtime preview? === IMPLEMENTATION PLAN TO BE FLESHED OUT BASED ON QUESTIONS To come <- Task can be edited by engineer === New Instrumentation |Proposed new event name|Action that will trigger new event|Schema where event will be logged |---|---|--- |//TBD//|//TBD//|//TBD// === Implementation Process |Step | People/Team Responsible|Description|Status |---|---|---|--- |1. | #community-tech | File ticket requesting instrumentation | ✅ Done in T306176 |2. | #community-tech | Populate the `===New instrumentation` section with proposed changes, once defined | |3. | @mneisler + @dlynch | Review the `===New instrumentation` Community Tech is proposing to introduce| |4. | #community-tech | Implement the instrumentation changes defined in `===New instrumentation` | |5. | #editing-team | Code review the instrumentation changes Community Tech will have implemented | |6. | #community-tech | Verify newly instrumented events are being emitted as expected by clients | |7. | #product-analytics | Verify newly instrumented events are being logged in database as expected, once the new instrumentation has landed in production. | |8. | #community-tech | Update schema documentation with the events spec'd in this task once they have been verified to be implemented as expected. //Read: clients are emitting events as expected and said events are being logged in the database as expected as well.//|