//馃尡This task is still a seedling on the floor of the forest is Phabricator. You can expect more context here once the thinking becomes more stable. In the meantime, thinking is happening in docs like [Editing Platform Strategy (Spring 2021)](https://docs.google.com/document/d/1lZCIZL-UzqSOf91hD_sRdaG6_Z0zIxfFAVDVYOgeC48/edit#heading=h.97oiei8frcli) (limited access for now).//
---
This task represents the work involved with defining the impact(s) the Editing System will have and the strategy we will use as our guide for bringing about said impact(s).
=== Use cases
//An emerging-list of use cases/needs//
- **As a WMF Product Team** who is developing an editing experience that depends on VE, **I want** to know who and how VE is available at each Wikimedia project, **so that** we can know which of the editors we are building for will be able to access it.
- **As a WMF Product Team** who is developing an editing experience for newcomers that depends on VE, **I want** said newcomers to be able to easily and intuitively access VE, **so that** we can maximize the number of newcomers that can use the experience we are building.
-- Example: Growth Team and zh.wiki (T287884#7267549).
- **As a WMF Product Team** who is seeking to improve a particular part of VE's experience, I would like to know what data is available about how people use VE, so that we can decide what intervention might be most impactful to implement.
-- Example: CommTech and thinking about how they might leverage edit notices and the `Review your changes` view to make volunteers aware when they've done something that may defy the project's policies. In this case, adding wikilinks to disambiguation pages. //More in: [Warn when linking to disambiguation pages](https://meta.wikimedia.org/wiki/Community_Tech/Warn_when_linking_to_disambiguation_pages) and T285508.//
- **As a WMF Product Team** who is seeking to improve a particular part of VE's experience, I would like to know what events are currently being tracked within the VisualEditor, so that we can decide whether new instrumentation is needed to measure a particular part of the experience.
- **As a WMF Product Team** who is adding new instrumentation to VE, I would like to know what is required to do so, so that we can ensure the changes we are making align with best practices.
-- Example: {T265101}
- **As a volunteer developer** who maintains a gadget that introduces new functionality to wikitext talk pages, I want to be able to leverage #DiscussionTools capabilities to improve the experience for people who depend on the gadget I maintain.
-- Example: T284836#7306168 [via @Jack_who_built_the_house]
- **As a WMDE Product Team** who is making changes to an existing workflow(s) within the VisualEditor, I want to know when and how to update [VisualEditor's technical documentation](https://www.mediawiki.org/wiki/VisualEditor), so that people needing to use these new workflows can independently learn how to do so.
-- Example: WMDE seeking guidance on when and how to update VisualEditor's technical documentation to reflect the changes they are introducing through the work they are doing on templates: [WMDE/Technical Wishes/Templates](https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Templates). [via @Lena_WMDE]
- **As a WMF Product Team** who is wanting to evaluate the impact of a change they are making to the visual editor, I want to know how to go about designing, implementing, running, and reporting on an A/B or multivariate test, so that we, and others, can depend on this information to make decisions.