[EPIC] Improve page issues
Open, NormalPublic

Description

Note: This EPIC has sign off criteria! Please check and resolve it before closing this task!

From RFC on english wikipedia

If an article is up for AfD and flagged as a possible hoax with insufficient medical sourcing, any reader visiting that article on a computer is greeted by three large red and orange boxes at the top of the page, one with a cautionary stop sign. The reader is clearly told that what they're about to read may be a complete fabrication, contains inadequately referenced medical advice, and that an active, serious discussion has been raised about removing the article from Wikipedia. If a reader instead visits the same hoax medical article on their phone (and [https://www.mediawiki.org/wiki/Wikimedia_Product#Reading 45% of Wikimedia traffic is now from mobile devices]), they just get two tiny grey words "Page issues" under the article title - the same ignorable alert they'd get if the article had an inconsistent footnote style or a missing taxobox - and the article is presented like any other.

Problem statement

Page issues are hidden even if they are important.

Because of the hacky way we deal with issues, sometimes other content is unnecessarily identified as issues and hidden e.g.
T166451 and https://en.wikipedia.org/wiki/File:Threat_of_harm_page_on_mobile_using_just_template.PNG

User story

As a reader of wikipedia, I would like to know how reliable is the information I'm reading on wikipedia

Solution

We can group page issues into four buckets.

  1. Severe: type=speedy, type=delete
  2. Medium: type=content
  3. Low: type = style
  4. Notice: type = notice, type = move, type = protection

Visual treatments will vary based on severity.

The treatments varies in color, icons, language, and position of the message.

Sign off steps

  • Make sure T183246 has been resolved by deploying page issues.

Related Objects

StatusAssignedTask
OpenNirzar
Openalexhollender
OpenNone
StalledNone
InvalidNone
ResolvedCKoerner_WMF
ResolvedCKoerner_WMF
InvalidNone
Resolvedovasileva
Resolvedalexhollender
Duplicatealexhollender
Resolvedalexhollender
Resolvedovasileva
Resolvedalexhollender
ResolvedRyasmeen
ResolvedRyasmeen
OpenNone
Resolvedphuedx
OpenTbayer
Resolvedovasileva
ResolvedNiedzielski
ResolvedTbayer
ResolvedTbayer
ResolvedTbayer
ResolvedTbayer
Resolvedovasileva
ResolvedTbayer
Resolvedphuedx
Resolvedovasileva
ResolvedJdlrobson
ResolvedJdlrobson
OpenTbayer
ResolvedTbayer
ResolvedNiedzielski
DeclinedNone
Resolvedovasileva
OpenNone
OpenJdlrobson
ResolvedNone
OpenNone
ResolvedABorbaWMF
There are a very large number of changes, so older changes are hidden. Show Older Changes
Jdlrobson renamed this task from Improve page issues to [EPIC] Improve page issues.May 21 2017, 11:26 AM
Jdlrobson added a project: Epic.
Elitre added a subscriber: Elitre.Dec 12 2017, 4:35 PM

I stumbled on Marina Abramovic's article on en.m., and I thought "Page issues" was some kind of vandalized Wikidata description.

I stumbled on Marina Abramovic's article on en.m., and I thought "Page issues" was some kind of vandalized Wikidata description.

do you mean the description of Page Issues in this task or in general the mbox template?

I meant the current position of the words "Page Issues" right under her name.

Regarding the ordering of page issues (high, medium, low), english Wikipedia uses the following "types" to categorise the ambox templates:

(red)

  • type=speedy – Speedy deletion issues
  • type=delete – Deletion issues

(orange/yellow)

  • type=content – Content issues
  • type=style – Style issues

(blue/purple)

  • type=notice – Article notices
  • type=move – Merge, split and transwiki proposals

( and also "type=protection – Protection notices" but I think those are handled by the "page locked" feature?)

It seems logical to me to use the existing ambox types to determine the "high, medium, low" placement of notices on mobile.

phuedx added a subscriber: phuedx.Jan 18 2018, 5:51 PM

@Jdrewniak: Great! Can we follow up and investigate if/how these types vary by wiki?

Nirmos added a subscriber: Nirmos.Jan 24 2018, 9:19 PM

I'd like to get a better understanding of why exactly some templates are hidden on mobile. Is it tables that are the problem, and if it is, would converting these templates from <table> to <div> solve the problem?

@Nirmos it's my understanding switching to div's will not help here and the problem is more with the positioning and size of the "issues" within the constraints of a mobile screen.

This is what a user will see on a mobile device as they currently exist:


There is just one page issue on this page, but many articles have more than 1... imagine 2 of those boxes.
Meanwhile all the content/knowledge is buried several scrolls down...

Are you only concerned about articles? If so, can you scope these rules to the main namespace?

@Jdrewniak Most of the discussion about general message treatment has been done and should be best proceeded in T127405.

Jdlrobson updated the task description. (Show Details)Feb 26 2018, 4:35 PM
RHo added a subscriber: RHo.Mar 12 2018, 4:52 PM
Restricted Application edited projects, added Readers-Web-Backlog; removed Readers-Web-Backlog (Design). · View Herald TranscriptApr 5 2018, 4:58 PM
ovasileva triaged this task as Normal priority.Apr 5 2018, 4:59 PM
ovasileva moved this task from To Do to Quarterly Goals on the Readers-Web-Kanbanana-Board-Old board.

Just remove the code that collapses the issue boxes and make mobile readers see the same boxes as desktop readers.

stjn added a subscriber: stjn.Oct 4 2018, 2:25 PM

Quick question: after A/B test will be done, will new page issue design display without a delay for users or is it expected to be like this in future?

The delay will be removed. thanks for the reminder! Have updated T206178 to explicitly call that out. Right now delay is needed for the A/B test.

Quiddity removed a subscriber: Quiddity.Oct 4 2018, 10:35 PM
ovasileva changed the status of subtask T200793: Disable page issues A/B test from Stalled to Open.Oct 16 2018, 3:56 PM
Nirmos removed a subscriber: Nirmos.Mon, Nov 12, 10:46 PM