Change Details

This task involves the work with converging on what people will experience when they attempt to reference a source that a project has determined to be unreliable while editing using the visual editor. //A parallel effort for the 2010 wikitext editor is is happening in T347435.// Where "unreliable" in the scope of this ticket refers to a source that exists on a given project's `Special:BlockedExternalDomains` page. //Note: we can see a future where Edit Checks presents people with feedback about source beyond those that projects block from being published. Tho, this work will happen in T348060 once, at a minimum, T346849 is resolved. [i]// === Story **As a person** who is unaware of Wikipedia's [reliability policy](https://www.wikidata.org/wiki/Q4663914) and who is attempting to reference a source that the project I'm editing has deemed to be unreliable //and// unfit for publishing on-wiki, **I'd value** being made aware of this information and presented with an easy and timely way to act on it, so that I can publish the change(s) I'm making and increase the likelihood that they remain on the wiki before I've "moved on" from thinking about sources. === User experience //This section will eventually contain the proposed user experience for, what we're calling, the Reference Reliability Edit Check.// === Learning objectives This ticket is scoped with the goal of helping us to arrive at initial answers to the following questions: - [ ] 1. When and how is the feedback shown initially? - [ ] 2. What call(s) to action is presented along with that feedback? - [ ] 3. When you engage with the call to action, what does the workflow look like? --- i. Please see T346849#9217888 for more context about how/why the Editing Team has arrived at this point of view.

This task involves the work with converging on what people will experience when they attempt to reference a source that a project has determined to be unreliable while editing using the visual editor. //A parallel effort for the 2010 wikitext editor is is happening in T347435.// Where "unreliable" in the scope of this ticket refers to a source that exists on a given project's `Special:BlockedExternalDomains` page. //Note: we can see a future where Edit Checks presents people with feedback about source beyond those that projects block from being published. Tho, this work will happen in T348060 once, at a minimum, T346849 is resolved. [i]// === Story **As a person** who is unaware of Wikipedia's [reliability policy](https://www.wikidata.org/wiki/Q4663914) and who is attempting to reference a source that the project I'm editing has deemed to be unreliable //and// unfit for publishing on-wiki, **I'd value** being made aware of this information and presented with an easy and timely way to act on it, so that I can publish the change(s) I'm making and increase the likelihood that they remain on the wiki. === User experience //This section will eventually contain the proposed user experience for, what we're calling, the Reference Reliability Edit Check.// === Learning objectives This ticket is scoped with the goal of helping us to arrive at initial answers to the following questions: - [ ] 1. When and how is the feedback shown initially? - [ ] 2. What call(s) to action is presented along with that feedback? - [ ] 3. When you engage with the call to action, what does the workflow look like? --- i. Please see T346849#9217888 for more context about how/why the Editing Team has arrived at this point of view.

This task involves the work with converging on what people will experience when they attempt to reference a source that a project has determined to be unreliable while editing using the visual editor. //A parallel effort for the 2010 wikitext editor is is happening in T347435.// Where "unreliable" in the scope of this ticket refers to a source that exists on a given project's `Special:BlockedExternalDomains` page. //Note: we can see a future where Edit Checks presents people with feedback about source beyond those that projects block from being published. Tho, this work will happen in T348060 once, at a minimum, T346849 is resolved. [i]// === Story **As a person** who is unaware of Wikipedia's [reliability policy](https://www.wikidata.org/wiki/Q4663914) and who is attempting to reference a source that the project I'm editing has deemed to be unreliable //and// unfit for publishing on-wiki, **I'd value** being made aware of this information and presented with an easy and timely way to act on it, so that I can publish the change(s) I'm making and increase the likelihood that they remain on the wiki before I've "moved on" from thinking about sources. === User experience //This section will eventually contain the proposed user experience for, what we're calling, the Reference Reliability Edit Check.// === Learning objectives This ticket is scoped with the goal of helping us to arrive at initial answers to the following questions: - [ ] 1. When and how is the feedback shown initially? - [ ] 2. What call(s) to action is presented along with that feedback? - [ ] 3. When you engage with the call to action, what does the workflow look like? --- i. Please see T346849#9217888 for more context about how/why the Editing Team has arrived at this point of view.