Change Details

====Background **Hypothesis:** If we developed a proof of concept that adds translation tasks sourced from WikiProjects and other list-building initiatives, and present them as suggestions within the CX mobile workflow, then more editors would discover and translate articles focused on topical gaps. By introducing an option that allows editors to select translation suggestions based on topical lists, we would test whether this approach increases the content coverage in our projects. By making topical lists visible in existing editorial workflows, in this case, the CX mobile interface, where editors land to translate articles: - To increase the visibility/discovery of topical gaps; if this works, more editors will become aware of topical lists. - To increase translations; if this works, topical lists can offer an alternative source of translation suggestions. This hypothesis focus allows for a more targeted editor participation toward addressing topical gaps. ====Description/User story `Including WorkLists` As a campaign/ wiki project organizer, I want to include topical lists in the CX mobile workflow, So that more editors can discover and translate articles based on these worklists. `Updating WorkLists` As a campaign/ wiki project organizer, I want to update the worklist that feeds into the CX mobile workflow, So that newer sets of articles within the topic can be translated. `Tracking Translated Articles` As a campaign/ wiki project organizer, I want to know which articles have been translated from the CX mobile workflow, So that the translation worklist can reflect the true status of the gap. `Managing WorkLists` As a campaign/WikiProject organizer, I want to manage the visibility and prioritization of topical lists, So that editors are directed to the most critical content gaps. ====Acceptance Criteria TBA

====Background **Hypothesis:** If we developed a proof of concept that adds translation tasks sourced from WikiProjects and other list-building initiatives, and present them as suggestions within the CX mobile workflow, then more editors would discover and translate articles focused on topical gaps. By introducing an option that allows editors to select translation suggestions based on topical lists, we would test whether this approach increases the content coverage in our projects. By making topical lists visible in existing editorial workflows, in this case, the CX mobile interface, where editors land to translate articles: - To increase the visibility/discovery of topical gaps; if this works, more editors will become aware of these worklists. - To increase translations; if this works, worklists can offer an alternative source of translation suggestions. ====Description This ticket would try to explore : - how best to store translation worklists with parameters such as **source article title**, **source language**, **target language**, **QID**, etc. - a "list-infrastructure" / "list-manager" / "list pipeline" that's useable by any project/ wiki. ====User story `Including WorkLists` As a campaign/ wiki project organizer, I want to include topical lists in the CX mobile workflow, So that more editors can discover and translate articles based on these worklists. `Updating WorkLists` As a campaign/ wiki project organizer, I want to update the worklist that feeds into the CX mobile workflow, So that newer sets of articles within the topic can be translated. `Tracking Translated Articles` As a campaign/ wiki project organizer, I want to know which articles have been translated from the CX mobile workflow, So that the translation worklist can reflect the true status of the gap. `Managing WorkLists` As a campaign/WikiProject organizer, I want to manage the visibility and prioritization of topical lists, So that editors are directed to the most critical content gaps. ====Acceptance Criteria - Recommended approach - Dependencies - Risks

====Background **Hypothesis:** If we developed a proof of concept that adds translation tasks sourced from WikiProjects and other list-building initiatives, and present them as suggestions within the CX mobile workflow, then more editors would discover and translate articles focused on topical gaps. By introducing an option that allows editors to select translation suggestions based on topical lists, we would test whether this approach increases the content coverage in our projects. By making topical lists visible in existing editorial workflows, in this case, the CX mobile interface, where editors land to translate articles: - To increase the visibility/discovery of topical gaps; if this works, more editors will become aware of topical these worklists. - To increase translations; if this works, topical worklists can offer an alternative source of translation suggestions. This hypothesis focus allows for a more targeted editor participation toward addressing topical gaps. ====Description/====Description This ticket would try to explore : - how best to store translation worklists with parameters such as **source article title**, **source language**, **target language**, **QID**, etc. - a "list-infrastructure" / "list-manager" / "list pipeline" that's useable by any project/ wiki. ====User story `Including WorkLists` As a campaign/ wiki project organizer, I want to include topical lists in the CX mobile workflow, So that more editors can discover and translate articles based on these worklists. `Updating WorkLists` As a campaign/ wiki project organizer, I want to update the worklist that feeds into the CX mobile workflow, So that newer sets of articles within the topic can be translated. `Tracking Translated Articles` As a campaign/ wiki project organizer, I want to know which articles have been translated from the CX mobile workflow, So that the translation worklist can reflect the true status of the gap. `Managing WorkLists` As a campaign/WikiProject organizer, I want to manage the visibility and prioritization of topical lists, So that editors are directed to the most critical content gaps. ====Acceptance Criteria TBA- Recommended approach - Dependencies - Risks