Page MenuHomePhabricator
Create Task
Maniphest T147641

[EPIC] Improve top of the article user experience - mobile
Closed, ResolvedPublic
Actions

Description

Background
Currently, the top of an article can contain a number of issues including:

  1. Repetitive/inappropriate lead images
  2. Page issues link that can look confusing along with wikidata descriptions
  3. Redirect message
  4. Lengthy article notes
  5. Infobox appearing before article text

We would like to address these issues to minimize confusion and provide a more cohesive user experience.
A few examples:

Screen Shot 2016-10-07 at 3.26.30 PM.png (710×398 px, 253 KB)
Screen Shot 2016-10-07 at 3.39.43 PM.png (757×401 px, 86 KB)
Screen Shot 2016-10-07 at 3.41.24 PM.png (779×405 px, 202 KB)

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedJdlrobsonT147641 [EPIC] Improve top of the article user experience - mobile
 ResolvedNoneT145216 MobileFormatter should relocate first paragraph ahead of infobox
 ResolvedPRODUCTION ERROR• bmansurovT149389 Not Found Error in MobileFormatter
 ResolvedNoneT149561 Paragraphs are pulled out of infobox
 ResolvedJdlrobsonT143535 [EPIC] Improve article notes
ResolvedovasilevaT146596 Make redirect into a toast message
 ResolvedphuedxT150639 Redirect toasts should replace underscores with spaces
 DuplicateNoneT157895 Section-templates don't show on mobile
 ResolvedovasilevaT159262 [EPIC] Improve page issues
 ResolvedJdlrobsonT183246 {{Orphan}} template is quasi-visible on mobile web even when it's not visible on desktop
 InvalidNoneT184421 Page issues {{Expand}} template produces empty items on mobile
 ResolvedCKoerner_WMFT186058 Community Liaison support for page issues on mobile
 ResolvedCKoerner_WMFT209405 Announce page issues improvement
InvalidNoneT191305 Mobile page issues - use hide when compact where available
 ResolvedovasilevaT191528 Mobile page issues - allow page issues to display different severity levels
 Resolved• alexhollender_WMFT191303 Mobile page issues - visual styling changes
 Duplicate• alexhollender_WMFT191529 Mobile page issues - visual changes for multiple issues
 Resolved• alexhollender_WMFT191671 [Research] Perform user testing for Page Issues on mobile web
 ResolvedovasilevaT197728 Sistersiteboxs are wired up to page issues when they shouldn't be
 Resolved• alexhollender_WMFT197932 Display section issues modal
 ResolvedRyasmeenT197931 Truncate page issues
 ResolvedRyasmeenT198115 Links should not be clickable in mobile page issue element
 Resolved• NiedzielskiT201634 [EPIC] Post A-B test technical debt cleanup
 ResolvedovasilevaT206177 Page issues: Simplify class selectors we support to provide more sustainable support for severity parsing
 ResolvedNoneT206178 Feature branch: Remove pageIssues A-B test code
 ResolvedovasilevaT202349 When a page has multiple issue boxes but doesn't use multiple issues template, the icon is shared across all issues boxes.
 ResolvedABorbaWMFT208514 Merge PageIssues Feature Branch to Master
 Resolved• alexhollender_WMFT210553 Deploy page issues to all wikipedias (except enwiki)
 DuplicateNoneT201975 Make page issue and hatnote classes names configurable so we are not English-Wikipedia centric
 Resolved• NiedzielskiT211257 Split pageIssues.js into smaller functions
 ResolvedovasilevaT210554 Deploy page issues to enwiki and all remaining projects
 ResolvedovasilevaT200794 Analyze results of page issues A/B test
 ResolvedphuedxT200793 Disable page issues A/B test
 Resolved• TbayerT200792 [EPIC] Run A/B test on page issues (Farsi, Japanese, Russian, English)
 ResolvedovasilevaT191532 Mobile page issues - instrument page issues
 Resolved• NiedzielskiT201124 Provide standard/reproducible way to access a PageToken
 Resolved• TbayerT202098 Log sectionNumbers in PageIssues schema
 Resolved• TbayerT202651 Section number in issues is reported incorrectly.
 Resolved• TbayerT202940 [subtask] Various page issues events sending NaN for sectionNumbers in old treatment
 Resolved• TbayerT203050 sectionNumbers and issuesSeverity should always be consistent in length
 ResolvedovasilevaT202786 [subtask] Edits via the main edit icon are not triggering Schema:Edit or Schema:PageIssues events
 Resolved• TbayerT203725 Icon correct but issuesSeverity in instrumentation is wrong
 ResolvedphuedxT193584 Prepare feature flagging gateway for mobile issues work
 ResolvedovasilevaT198113 QA mobile page issues modal
 ResolvedJdlrobsonT203802 Latvian Wikipedia amboxes should be compatible with Minerva's
 ResolvedJdlrobsonT204144 ReadingDepth sometimes initialises before PageIssues leading to incorrect or missing ReadingDepth events
 Resolved• TbayerT204143 ReadingDepth events are not being sent in browsers where navigator.sendBeacon should be supported but in practice isn't
 Resolved• TbayerT204609 Turn on page issues A/B test for Latvian Wikipedia, and conduct data checks
 Resolved• NiedzielskiT205355 A/B config flag should be subject to ResourceLoader caching rules not HTML caching rules
 DeclinedNoneT204613 Turn A/B test for page issues on for test projects at low rates to validate instrumentation
 ResolvedovasilevaT204090 QA page issues feature
 ResolvedNoneT214653 Page issues broken on english wikivoyage
 ResolvedJdlrobsonT173600 Improve treatment of hatnotes
 DuplicateNoneT141124 Handle promoting feature from beta to stable
 DuplicatephuedxT141121 Implement basic feature management
 ResolvedphuedxT150325 Move first paragraph before infobox on stable
 ResolvedphuedxT149852 Lead introduction edge case in MobileFrontend where paragraph precedes list element
 ResolvedphuedxT149830 Re-enable moving the first paragraph before infobox on MF beta
 ResolvedJdlrobsonT149884 Log instances of infoboxes being wrapped in containers
 ResolvedPRODUCTION ERRORphuedxT151838 [4 hours] Warning: Invalid state error in MobileFormatter
 ResolvedJdlrobsonT162713 [spike 2hrs] Evaluate result of "Log instances of infoboxes being wrapped in containers" (T149884 )
 ResolvedJdlrobsonT163805 Adjustments to how we log troublesome infoboxes and move lead paragraph

Event Timeline

ovasileva created this task.Oct 7 2016, 1:42 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 7 2016, 1:42 PM
ovasileva moved this task from Incoming to Epics/Goals on the Web-Team-Backlog board.Oct 7 2016, 1:43 PM
ovasileva added a subtask: T146596: Make redirect into a toast message.Oct 7 2016, 1:46 PM
ovasileva added a subtask: T145216: MobileFormatter should relocate first paragraph ahead of infobox.
• Moushira subscribed.Oct 7 2016, 4:42 PM
ovasileva closed subtask T145216: MobileFormatter should relocate first paragraph ahead of infobox as Resolved.Oct 28 2016, 10:12 AM
Jdlrobson reopened subtask T145216: MobileFormatter should relocate first paragraph ahead of infobox as Open.Oct 31 2016, 9:15 AM
• bmansurov closed subtask T145216: MobileFormatter should relocate first paragraph ahead of infobox as Resolved.Nov 2 2016, 6:56 PM
phuedx changed the status of subtask T146596: Make redirect into a toast message from Open to Stalled.Nov 3 2016, 9:36 PM
• jhobs changed the status of subtask T146596: Make redirect into a toast message from Stalled to Open.Nov 7 2016, 6:05 PM
ovasileva closed subtask T146596: Make redirect into a toast message as Resolved.Nov 9 2016, 10:12 AM
Jdlrobson reopened subtask T146596: Make redirect into a toast message as Open.Nov 14 2016, 9:06 AM
• jhobs closed subtask T146596: Make redirect into a toast message as Resolved.Nov 14 2016, 5:00 PM
Jdlrobson reopened subtask T146596: Make redirect into a toast message as Open.Nov 14 2016, 8:29 PM
ovasileva closed subtask T146596: Make redirect into a toast message as Resolved.Nov 16 2016, 12:48 PM
ovasileva added a subtask: T143535: [EPIC] Improve article notes .Nov 22 2016, 2:49 PM
ovasileva added subtasks: T141124: Handle promoting feature from beta to stable, T150325: Move first paragraph before infobox on stable.
Jdlrobson moved this task from Epics/Goals to Design on the Web-Team-Backlog board.Apr 13 2017, 11:32 PM
Jdlrobson edited projects, added Web-Team-Backlog (Design); removed Web-Team-Backlog.
• Capt_Swing subscribed.Apr 27 2017, 8:30 PM

There appears to be write-up related to this study here: https://www.mediawiki.org/wiki/Wikimedia_Research/Design_Research/Reading_Team_UX_Research/Top_Chrome_Usability

ovasileva closed subtask T150325: Move first paragraph before infobox on stable as Resolved.May 25 2017, 10:24 AM
Jdlrobson assigned this task to • Nirzar.Jan 31 2018, 6:53 PM
Jdlrobson added subscribers: • Nirzar, Jdlrobson.

@Nirzar this epic has only one open subtask: T143535. Is it useful to have this epic, or can we close it in favor of the more granular T143535 ?

• Nirzar added a comment.Feb 1 2018, 9:20 PM

I think we need to keep this open. T143535 is made up bunch of other things, as well. but the end goal is to improve top of the article experience

ovasileva triaged this task as Medium priority.Nov 15 2018, 10:44 PM
AfroThundr3007730 subscribed.Dec 17 2018, 9:19 PM
• alexhollender_WMF mentioned this in T217197: Move skin "subtitle" markup that contains redirect and breadcrumbs.Mar 13 2019, 2:06 PM
Jdlrobson closed subtask T143535: [EPIC] Improve article notes as Resolved.Mar 19 2019, 9:30 PM
Aklapper removed • Nirzar as the assignee of this task.Nov 4 2019, 10:19 AM

Removing @Nirzar as assignee, as that account has been disabled.

Jdlrobson added a subscriber: • alexhollender_WMF.Jun 8 2021, 7:35 PM

@alexhollender is this epic up to date/relevant 2 years later?

Jdlrobson moved this task from Design to Tracking on the Web-Team-Backlog board.Jun 8 2021, 7:35 PM
Jdlrobson edited projects, added Web-Team-Backlog (Tracking); removed Web-Team-Backlog (Design).
• alexhollender_WMF added a comment.Jun 14 2021, 1:17 PM

@Jdlrobson it seems that all except one (T214653) of the child tasks are complete, so maybe we can close this epic? There are definitely more improvements to be made to the top of article experience on mobile, but not sure there is much guidance / value left in this task.

Jdlrobson closed this task as Resolved.Jun 14 2021, 3:15 PM
Jdlrobson claimed this task.

Sounds good.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL