Change Details

**Request Status:** New Request **Request Type:** project support request **Related OKRs:** **Request Title:** Copyedit structured task API -- - **Request Description:** Structured tasks are meant to break down editing tasks into step-by-step workflows that make sense for newcomers and make sense on mobile devices. The Growth team believes that introducing these new kinds of editing workflows will allow more new people to begin participating on Wikipedia, some of whom will learn to do more substantial edits and get involved with their communities. We have built two: link suggestions and image suggestions. Even as we built those, communities repeatedly have explained that the task they desire most is around copyediting -- something related to spelling, grammar, punctuation, tone, etc. The [[ https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task/Literature_review | Research team has surveyed the state of the art ]] in terms of open source resources and APIs that we could use to identify simple spelling suggestions in many languages. The end product for the Growth team would be a service that suggests spelling changes for Wikipedia articles across dozens of languages, which incorporates Wikipedia-specific logic (e.g. suggestions are only given for appropriate parts of the articles content). A more general product might also make such suggestions available in the Visual Editor while the user is working on an article, so that they can incorporate them before saving their edit. We will have support from the Research team in identifying, validating, and adapting the spelling solution. - **Indicate Priority Level:** Medium - **Main Requestors:** Growth and Editing teams - **Ideal Delivery Date:** November 2022 - **Stakeholders:** Marshall Miller and Peter Pelberg **Request Documentation** -- |**Document Type**| **Required?** | **Document/Link** | | **Related PHAB Tickets** | Yes | <add link here> | | **Product One Pager** | Yes |<add link here> | | **Product Requirements Document (PRD)** | Yes | <add link here> | | **Product Roadmap** | No | <add link here> | | **Product Planning/Business Case** | No |<add link here> | | **Product Brief** | No | <add link here> | | **Other Links** | No |[[https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Structured_tasks/Copyedit | project page]] |

**Request Status:** New Request **Request Type:** project support request **Related OKRs:** **Request Title:** Copyedit structured task API -- - **Request Description:** Structured tasks are meant to break down editing tasks into step-by-step workflows that make sense for newcomers and make sense on mobile devices. The Growth team believes that introducing these new kinds of editing workflows will allow more new people to begin participating on Wikipedia, some of whom will learn to do more substantial edits and get involved with their communities. We have built two: link suggestions and image suggestions. Even as we built those, communities repeatedly have explained that the task they desire most is around copyediting -- something related to spelling, grammar, punctuation, tone, etc. The [[ https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task/Literature_review | Research team has surveyed the state of the art ]] in terms of open source resources and APIs that we could use to identify simple spelling suggestions in many languages. The end product for the Growth team would be a service that suggests spelling changes for Wikipedia articles across dozens of languages, which incorporates Wikipedia-specific logic (e.g. suggestions are only given for appropriate parts of the articles content). A more general product might also make such suggestions available in the Visual Editor while the user is working on an article, so that they can incorporate them before saving their edit. We will have support from the Research team in identifying, validating, and adapting the spelling solution. - **Indicate Priority Level:** Medium - **Main Requestors:** Growth - **Ideal Delivery Date:** TBD - **Stakeholders:** Kirsten Stoller **Request Documentation** -- |**Document Type**| **Required?** | **Document/Link** | | **Related PHAB Tickets** | Yes | <add link here> | | **Product One Pager** | Yes |<add link here> | | **Product Requirements Document (PRD)** | Yes | <add link here> | | **Product Roadmap** | No | <add link here> | | **Product Planning/Business Case** | No |<add link here> | | **Product Brief** | No | <add link here> | | **Growth Project Page** | - |[[https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Structured_tasks/Copyedit | Copyedit Structured Task project page]]| | **Early Research ** | - | [[ https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task | Research:Copyediting as a structured task ]]|

**Request Status:** New Request **Request Type:** project support request **Related OKRs:** **Request Title:** Copyedit structured task API -- - **Request Description:** Structured tasks are meant to break down editing tasks into step-by-step workflows that make sense for newcomers and make sense on mobile devices. The Growth team believes that introducing these new kinds of editing workflows will allow more new people to begin participating on Wikipedia, some of whom will learn to do more substantial edits and get involved with their communities. We have built two: link suggestions and image suggestions. Even as we built those, communities repeatedly have explained that the task they desire most is around copyediting -- something related to spelling, grammar, punctuation, tone, etc. The [[ https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task/Literature_review | Research team has surveyed the state of the art ]] in terms of open source resources and APIs that we could use to identify simple spelling suggestions in many languages. The end product for the Growth team would be a service that suggests spelling changes for Wikipedia articles across dozens of languages, which incorporates Wikipedia-specific logic (e.g. suggestions are only given for appropriate parts of the articles content). A more general product might also make such suggestions available in the Visual Editor while the user is working on an article, so that they can incorporate them before saving their edit. We will have support from the Research team in identifying, validating, and adapting the spelling solution. - **Indicate Priority Level:** Medium - **Main Requestors:** Growth and Editing teams - **Ideal Delivery Date:** November 2022TBD - **Stakeholders:** Marshall Miller and Peter PelbergKirsten Stoller **Request Documentation** -- |**Document Type**| **Required?** | **Document/Link** | | **Related PHAB Tickets** | Yes | <add link here> | | **Product One Pager** | Yes |<add link here> | | **Product Requirements Document (PRD)** | Yes | <add link here> | | **Product Roadmap** | No | <add link here> | | **Product Planning/Business Case** | No |<add link here> | | **Product Brief** | No | <add link here> | | **Other LinksGrowth Project Page** | No- |[[https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Structured_tasks/Copyedit | project page]] Copyedit Structured Task project page]]| | **Early Research ** | - | [[ https://meta.wikimedia.org/wiki/Research:Copyediting_as_a_structured_task | Research:Copyediting as a structured task ]]|