Page MenuHomePhabricator

Suggestion Mode: Entry point in read mode
Open, HighPublic7 Estimated Story Points

Assigned To
None
Authored By
bmartinezcalvo
Jun 4 2026, 5:35 PM
Referenced Files
F94878511: image.png
Jul 20 2026, 6:06 PM
F94877812: image.png
Jul 20 2026, 6:03 PM
F94877764: image.png
Jul 20 2026, 6:03 PM
F94877732: image.png
Jul 20 2026, 6:03 PM
F94865766: Captura de pantalla 2026-07-20 a las 18.50.05.png
Jul 20 2026, 4:51 PM
F94860674: image.png
Jul 20 2026, 4:19 PM
F94227655: image.png
Jul 17 2026, 1:23 PM
F94227515: image.png
Jul 17 2026, 1:23 PM

Description

Background

As part of the work to surface suggestions in read mode, we need to decide on the entry point for logged-in users to access edit mode and navigate available suggestions.

This task is introduce an entry point to Suggestion Mode in read mode that allows logged-in readers to discover that suggestions are available to contribute to an article, without creating the impression of an unread alert that requires their attention.

User stories

As a logged-in Wikipedia reader who has published ≤100 cumulative edits and is arriving on-wiki seeking to learn about something/someone (broadly defined), I want to know when there are edit suggestions available within the article I am reading so that I can easily decide which (if any) I'd like to act on in this moment without needing to manually identify them myself.

Requirements

  • Implement the 3 variants proposed below so we can test them in production (T430712).

Design proposed

The proposed direction is a small indicator on the existing Edit action appearing when suggestions are available in an article in both desktop and mobile.

  • Desktop: to avoid including more elements in the article tabs, the suggestions indicator will appear on the edit icon in the fixed header, which becomes visible when scrolling.
  • Mobile: the suggestions indicator will appear in the edit icon in the article toolbar. I recommend solving T426055 to ensure that the edit action in the Minerva toolbar opens the full-page editor, making it easier for users to find all available suggestions once they enter edit mode.
  • The suggestions indicator will appear aligned at the bottom with the edit icon, in a 12x12px size in both desktop and mobile.
3 variants to implement and test

All these variants reuse the existing edit action as agreed, but vary on the suggestions indicator treatment.

Prototype: https://bmartinezcalvo.github.io/suggestion-mode/suggestions-read-mode-phase1/

image.png (3,900×1,680 px, 1 MB)
image.png (3,900×1,680 px, 1 MB)
image.png (3,904×1,688 px, 1 MB)
  • A — Lightbulb indicator + pulsating effect:
    • On first view, a pulsating effect appears on the lightbulb indicator.
    • On subsequent visits, only the static lightbulb indicator remains.
  • B — Lightbulb indicator + popup:
    • On first view, a popup explains that suggestions are available.
    • On subsequent visits, only the lightbulb indicator remains.
  • C — Numbered badge:
    • On first view, the numbered badge will include a slight pulse effect.
    • On subsequent visits, the numbered badge will appear with no animation effect.

Acceptance criteria (or Done)

Design

  • Explore feasible solutions for the suggestions entry point in read mode
  • Decided on best approach

Implementation

  • Implement decided solution
Future tasks

Event Timeline

I would suggest adding a button or a hint at the very end of the article in the mobile version indicating that users can view recommendations for improving the article and make edits.

We've considered the page actions bar on mobile, so note that it also has a tablet mode where we need to show (short-ish) labels with each icon:

image.png (1,052×138 px, 25 KB)

After exploring different directions and validating with stakeholders, volunteers, and usability testing with some users, here is a summary of the process followed to define the entry point for Suggestion Mode in read mode:

Initial explorations

We started by exploring several approaches with the following constraints:

  • the solution should not add a new element to the toolbar
  • it should not feel like an alert or a task to resolve before reading
  • it should not distract from the article content
Alignment with the Readers team

After reviewing the initial explorations with the Readers team, we aligned on using an indicator on the existing Edit action rather than introducing new UI elements — such as banners — that could conflict with other page components now or in the future.

Proposed direction: lightbulb indicator on the edit icon

Note: At this stage, suggestions can only be counted at the article level — counting suggestions per section is not yet supported.

The proposed direction is a small indicator on the existing Edit action appearing when suggestions are available in an article in both desktop and mobile.

image.png (2,880×1,360 px, 951 KB)
image.png (720×1,680 px, 410 KB)
Desktop: to avoid including more elements in the article tabs, the suggestions indicator will appear on the edit icon in the fixed header, which becomes visible when scrollingMobile: the suggestions indicator will appear in the edit icon in the article toolbar.

Note: I recommend solving T426055 to ensure that the edit action in the Minerva toolbar opens the full-page editor, making it easier for users to find all available suggestions once they enter edit mode.

This approach builds on an element already present in the interface, doesn't add new toolbar options or page elements, and is intentionally subtle. It signals that something is worth exploring, similar to a notifications badge, without implying there's a task to complete.

Feedback from users

To validate this direction, I ran a quick unmoderated usability test on Userlytics with 5 participants (2 desktop, 3 mobile), concluding that the edit icon with the suggestions indicator proved visible enough to prompt navigation to edit mode on both platforms. However, conclusions from just 5 participants are limited, so we discussed about running multi-variant quantitative test in production to get real data.

We also shared the proposal with some volunteers in a Discord call and gathered additional feedback that informed the final variants.

Next step: multi-variant quantitative test in production

Given that a small usability test doesn't provide a reliable quantitative signal, we decided to move forward with a multi-variant test in production across 3 variants (T430712). All these variants will reuse the existing edit action as agreed, but vary the suggestions indicator treatment.

image.png (3,900×1,680 px, 1 MB)
image.png (3,900×1,680 px, 1 MB)
image.png (3,904×1,688 px, 1 MB)
  • A — Lightbulb indicator + pulsating effect:
    • On first view, a pulsating effect appears on the lightbulb indicator.
    • On subsequent visits, only the static lightbulb indicator remains.
  • B — Lightbulb indicator + popup:
    • On first view, a popup explains that suggestions are available.
    • On subsequent visits, only the lightbulb indicator remains.
  • C — Numbered badge:
    • On first view, the numbered badge will include a slight pulse effect.
    • On subsequent visits, the numbered badge will appear with no animation effect.
Check the prototype with these 3 variants by selecting each one from the menu in the header: https://bmartinezcalvo.github.io/suggestion-mode/suggestions-read-mode-phase1/

These directions looks great – thank you, @bmartinezcalvo!

Next step(s)

  • Present to Editing Engineering to identify what (if any) technical constraints warrant revision(s) being made to the design
  • Decide when implementation will begin, considering work on the backend is underway (T428811)

I find the placement of the lightbulb indicator in the top right blocks the reading of the edit pencil and/or makes it look like it is part of the edit pencil:

image.png (44×40 px, 1022 B)

I feel like moving it to another corner or further away would help.

I find the placement of the lightbulb indicator in the top right blocks the reading of the edit pencil and/or makes it look like it is part of the edit pencil:

image.png (44×40 px, 1022 B)

I feel like moving it to another corner or further away would help.

The reasoning behind the placement of the lightbulb indicator was to be consistent with the lock modifier in cdxIconEditLock and other icons, placed always on the top-right corner.

Captura de pantalla 2026-07-20 a las 18.50.05.png (78×74 px, 4 KB)

ppelberg set the point value for this task to 7.Jul 20 2026, 5:46 PM

Next steps

As decided during the editing team meeting, I've updated the prototype and requirements with the lightbulb not covering the edit pencil so the edit action is always recognizable.

image.png (58×44 px, 1 KB)

medelius lowered the priority of this task from High to Medium.Wed, Aug 19, 5:13 PM
ppelberg raised the priority of this task from Medium to High.Wed, Sep 2, 5:24 PM

Can we avoid showing these on mobile when someone is "offline"? Cf. A related complexity that the Apps are facing: T437536: The mobile app suggests making an edit when there is no internet connection

Can we avoid showing these on mobile when someone is "offline"? Cf. A related complexity that the Apps are facing: T437536: The mobile app suggests making an edit when there is no internet connection

On web we don't cache articles for offline reading, so offline reading will happen only if the article was loaded online and the connection dropped afterwards. So I guess any indicator loaded before would still appear when the article becomes offline.