=== User Story
As a newcomer, I want to try new tasks, because I want to contribute to Wikipedia
As a more advanced Wikimedian, I want newcomers to learn new skills because I want newcomers to grow into productive contributors, moderators, and Wikimedians.
=== Design
[[ https://www.figma.com/file/fOa1x7hw6EM9VnaMJv7vib/Positive-reinforcement?node-id=3169%3A108978 | Figma Designs ]]
**Illustration assets (from T323785) **
| LTR | RTL
|--|--
|{F35823915} | {F35823997}
=== Description
A new post-edit dialog message type is added to encourage newcomers to try a new task type.
{F35825953}
**New task type (difficulty agnostic):**
- New copy for heading to try a new task.
- Instead of showing a recommended article, a message and illustration is shown to present a clear decision point to change tasks.
- A new task type suggested after a person completes 5 tasks of a certain type.
- Next task suggested may be the same level or harder.
**Details:**
- If 5 tasks are completed, then the next unselected task type is suggested
- If “Try new task” is selected, the standard post-edit dialog is shown with the new task type.
- If they choose "No thanks", then they will only see suggested edits set as before.
- After another 5 completed suggested edits they will see message again.
{F35825951}
**Don’t show again checkbox**
- The second and subsequent times the dialog is shown, an additional checkbox to “Don’t show this again” is shown. If the person selects this checkbox, they will opt out of further level up post-edit dialogs.
**Edit quality gate **
- These dialogs should not be shown to those with more than $(2) reverts in the last $(7) days.
#### 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.