This task involves the work of reviewing all of the Edit Check/Suggestion UI copy before the Suggestion Mode is offered as a Beta Feature at all Wikipedias (T415320) so that we can be relatively confident the strings we will be asking volunteers to translate are stable.
Note: the same copy is applied between checks and suggestions, so any changes made need to be applicable to either mode.
### List of types to review
https://en.wikipedia.beta.wmcloud.org/wiki/Special:EditChecks
### Problem
At the moment, checks and suggestions do not follow a consistent copy structure across different types. As a result, when multiple checks/suggestions appear on the same page, they are harder to scan, compare, and understand as a set.
{F71595738}
### Proposed solution
In order to be consistent, we could apply the following structure in the cards copy:
{F71595742}
- **Title:** Action oriented
- **Description:** Explain the issue + Explain the benefit for readers (starting with Help readers… to highlight impact and motivation as detected during usability testing)
- **Link** (optional): always at the end of the description as "Learn more"
- **Buttons:** Primary action (verb) + Decline (to be consistent with Checks)
- **Success message** (if completed): Always the same message "Thank you for helping to make this section easier for people to read."
NOTE: Copy will be iterated once we decide on structure.
### Open questions
[] Do we want to use the same copy for checks and suggestions? If yes, we will need to apply the new copy in both check + suggestions card
### Acceptance criteria
|Step|Description|Responsible|Notes
|---|---|---|---
|1.| Ahead of initial en.wiki Beta Feature release, decide what (if any) copy changes need to be implemented| @bmartinezcalvo |See current copy here: https://en.wikipedia.beta.wmcloud.org/wiki/Special:EditChecks
|2.| Define structure that all Suggestions will adhere to | @bmartinezcalvo |
|3.| Before sending Suggestion card copy off for translation ahead of wider Beta Feature release (T415320), refine copy we defined in "1."| @bmartinezcalvo |Assume this copy will remain in place for the foreseeable future. Share with @Dyolf77_WMF, @IZapico-WMF , @Geugeor-WMF for review
|4.| Implement copy refinements we converge on in "3." | Editing Engineering |