Change Details

####User Story As the Growth team, I want to be sure that patrollers and community moderators understand suggested edits / newcomer tasks, because they add a patrolling burden so it's important to understand they help more newcomers start editing AND help with retention ####Description Newcomer Tasks are tagged, example: Tags: Visual edit, Newcomer task, Newcomer task: copyedit However the "Newcomer task" and "Newcomer task: copyedit" tags link to the very lengthy project page: https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_tasks This isn't a very helpful page for community moderators who likely just want a quick summary of what a "Newcomer task" is and why they exist. Let's simply create a new, succinct summary of what these tasks are about AND the impact they have on newcomer activation and retention, and then link to this new page. ####Acceptance Criteria [] CRS to create new page and write WHAT / WHY summary for Newcomer tasks. [] PM to review [] CRS to help coordinate translations with Ambassadors / others [] Engineers to update code so that the new page is linked Given I'm viewing any page that includes a "Newcomer task" or "Newcomer task: ..." tag, When I click on it, Then it links to the new "Newcomer Task" media wiki page (//add link here//) #### Completion checklist **Functionality** [] The patches have been code reviewed and merged [] The task passes its acceptance criteria **Engineering** [] There are existing and passing unit/integration tests [] Tests for every involved patch should pass [] Coverage for every involved project should have improved or stayed the same **Design & QA** [] If the task is UX/Design related: it must be reviewed and approved by the UX/Design team [] Must be reviewed and approved by Quality Assurance. **Documentation** [] Related and updated documentation done where necessary - Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc) - Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.

####User Story As the Growth team, I want to be sure that patrollers and community moderators understand newcomer tasks (AKA suggested edits), because they add a patrolling burden so it's important to understand that these tasks help more newcomers start editing and improve retention. ####Description Newcomer Tasks are tagged, example: Tags: Visual edit, Newcomer task, Newcomer task: copyedit However the "Newcomer task" and "Newcomer task: copyedit" tags link to the very lengthy project page: https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_tasks This isn't a very helpful page for community moderators who likely just want a quick summary of what a "Newcomer task" is and why they exist. Let's simply create a new, succinct summary of what these tasks are about AND the impact they have on newcomer activation and retention, and then link to this new page. ####Acceptance Criteria [] CRS to create new page and write WHAT / WHY summary for Newcomer tasks. [] PM to review [] CRS to help coordinate translations with Ambassadors / others [] Engineers to update code so that the new page is linked Given I'm viewing any page that includes a "Newcomer task" or "Newcomer task: ..." tag, When I click on it, Then it links to the new "Newcomer Task" media wiki page (//add link here//) #### Completion checklist **Functionality** [] The patches have been code reviewed and merged [] The task passes its acceptance criteria **Engineering** [] There are existing and passing unit/integration tests [] Tests for every involved patch should pass [] Coverage for every involved project should have improved or stayed the same **Design & QA** [] If the task is UX/Design related: it must be reviewed and approved by the UX/Design team [] Must be reviewed and approved by Quality Assurance. **Documentation** [] Related and updated documentation done where necessary - Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc) - Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.

####User Story As the Growth team, I want to be sure that patrollers and community moderators understand suggested edits / newcomer tasksnewcomer tasks (AKA suggested edits), because they add a patrolling burden so it's important to understand theythat these tasks help more newcomers start editing AND help withand improve retention. ####Description Newcomer Tasks are tagged, example: Tags: Visual edit, Newcomer task, Newcomer task: copyedit However the "Newcomer task" and "Newcomer task: copyedit" tags link to the very lengthy project page: https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_tasks This isn't a very helpful page for community moderators who likely just want a quick summary of what a "Newcomer task" is and why they exist. Let's simply create a new, succinct summary of what these tasks are about AND the impact they have on newcomer activation and retention, and then link to this new page. ####Acceptance Criteria [] CRS to create new page and write WHAT / WHY summary for Newcomer tasks. [] PM to review [] CRS to help coordinate translations with Ambassadors / others [] Engineers to update code so that the new page is linked Given I'm viewing any page that includes a "Newcomer task" or "Newcomer task: ..." tag, When I click on it, Then it links to the new "Newcomer Task" media wiki page (//add link here//) #### Completion checklist **Functionality** [] The patches have been code reviewed and merged [] The task passes its acceptance criteria **Engineering** [] There are existing and passing unit/integration tests [] Tests for every involved patch should pass [] Coverage for every involved project should have improved or stayed the same **Design & QA** [] If the task is UX/Design related: it must be reviewed and approved by the UX/Design team [] Must be reviewed and approved by Quality Assurance. **Documentation** [] Related and updated documentation done where necessary - Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc) - Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.