T325711 ended up involving the work of defining at a high, and also relatively detailed level, what the Editing Team would propose for the //initial// **mobile** Edit Check user experience.
This task involves the work of creating a similarly detailed proposal for the //initial// **desktop** Edit Check user experience.
=== Mockups/Storyboard
[Tappable prototype (figma)](https://www.figma.com/proto/t1MMZZiDjkqZMJwkjhyJNB/Editing%2FEdit-Check?page-id=1345%3A50735&type=design&node-id=1345-51391&viewport=178%2C-42%2C0.03&scaling=contain&starting-point-node-id=1345%3A51391&hide-ui=1)
=== Overall approach
Per what the Editing Team decided offline on 15 March 2023, we will approach the //initial// Edit Check desktop user experience in a way that we ended up converging on for the mobile experience: **present people who are attempting to publish edits that match the criteria defined in T324730 with a new, distinct step within the desktop publishing flow.** Like on mobile, this "distinct step" will prompt people to decide whether they would like to accompany the new information they're adding with a source. If they choose //not// to add a source, Edit Check will prompt people to express why they have made this choice.
=== Done
- [ ] A link to mockups showing the "full" Edit Check desktop UX is included within the "Mockups/Storyboard" section above.
-- //Note: similar to what we did as part of T325711, these mockups ought to be visualized in a way that enables the Editing Team to see the various ways in which the screens within the UX relate to one another.//