This task involves the work of prototyping the {nav Revise} workflow the Editing Team sketched out during the team's 26 March offline discussion.
=== Story
As someone who has been made aware that the text I'm attempting to add to Wikipedia is likely to contain biased language //and// who has just expressed interest in revising the tone of what I've written, I want the next step for doing this to be clear and to feel supported in taking it, so that I do not become stuck/confused about what I'm meant to be doing.
=== Requirements
1. Tap {nav Revise} button with an Peacock Check card/hint, regardless of the moment it is presented within (e.g. Mid-Edit, Pre-Save)
2. Notice the text that's currently highlighted in yellow'ish changes to a different highlight color ~~and an accompanying border is addd (akin to what's done with links)~~ and your cursor is dropped into the end of the text you've written that prompted the Peacock Check to activate
-- Notes:
--- For the purpose of a demo, we're going to try gray.
--- The text will remain editable
3. Notice that when you tap/click anywhere within the document //outside// of the text you've written that prompted the Peacock Check to activate, the highlight returns to it's "normal" activated state and the border is removed
=== Open questions
- [ ] Will we move forward with the approach described by the Requirements above?
- [ ] If we decide to move forward with this approach, what – if any – adjustments will we make?
- [ ] Should the gray remain after the cursor leaves the paragraph, until the server-side recheck is complete? (If so, the gray really indicates "recheck pending", which may influence other UX decisions)
=== Done
- [x] Patch demo implementing the behavior documented above is generated
- https://patchdemo.wmcloud.org/wikis/f2bb83e4af/w/index.php?title=Cynghanedd&veaction=edit
- [ ] Answers to all open questions are documented