One of the crucial steps for providing Newcomers with an "Improve Tone Suggested Edit" is that we require a backlog of articles that have such an Edit Check available.

A range of potential approaches has been outlined in 🎭 Tone Suggestions: Storage options. Additional discussion happened in the #talk-to-editing channel on slack.

In this task, we want to actually build a rough Proof of Concept for how we can create that backlog of articles for the Improve Tone Suggested Edit. The main goal is to learn about the challenges and risks involved as much as possible and as quickly as possible. So that afterward we can decide if the overall approach is suitable or whether we need to change course.

How to actually move this forward:

• Figure out the columns for the db table to store the backlog of tasks
  • This should ideally be generic enough to support future Suggested Edits from other Edit Checks as well
• Support Editing Team in figuring out the expected volume that comes from Tone Edit Checks that were not acted upon when the edit was saved
• Work with Editing team to figure out the mechanism & interface for recording what Tone Edit Checks were not acted upon
• Work with Editing team to figure out the mechanism & interface for redirecting the user from the Homepage back into VisualEditor and to the task
  • T&S-concerns / validation of the Edit check data when VisualEditor is loading