Page MenuHomePhabricator

Account setup: Create interest selector and storage of interests (DE1.3.1)
Open, HighPublic3 Estimated Story Points

Assigned To
Authored By
KStoller-WMF
Jul 22 2026, 3:57 AM
Referenced Files
F98051093: image.png
Tue, Aug 11, 10:08 AM
F96644344: image.png
Aug 3 2026, 3:41 PM
F96123288: image.png
Aug 3 2026, 3:41 PM
F96123278: image.png
Aug 3 2026, 3:41 PM
F96123230: image.png
Aug 3 2026, 3:41 PM
F96644129: image.png
Aug 3 2026, 3:41 PM
F96123059: image.png
Aug 3 2026, 3:41 PM
F96123052: image.png
Aug 3 2026, 3:41 PM

Description

User story & summary

Create a Vue component that enables the selecting of articles as "interests" and shows related articles. This component will be used in three places:

  1. In the new onboarding
  2. as a replacement of the TopicSelector for suggested edits
  3. in the new migrated SuggestedEdits module on the PersonalDashboard (this is created by moderator tools)

Also, this is about defining the user option that will hold these interests.

Background & research

https://www.mediawiki.org/wiki/Home
Parent task: T430058: [EPIC] Account Setup (DE1.3.1 - early onboarding)

NOTE: This is only about creating the Vue.js component, follow up integration work part of this task: T432812: Account setup: Integrate interest selector into suggested edits + propose tasks by interest (DE1.3.1)

Design

Figma designs

image.png (2,778×1,002 px, 502 KB)

Acceptance criteria

  1. if the account creation process was initiated on a page other than an article page (Main Page also excluded even if it counts as a article page) we display random suggestions (pending decision on T433151) below a multiselectlookup. the "Go your Home" button is default quiet as long 3 interests are not picked.
    image.png (856×1,880 px, 265 KB)
  2. if the account creation process was initiated on an article page, the system uses that page to suggests related interests. the "Go your Home" button is default quiet as long 3 interests are not picked.
    image.png (856×1,880 px, 200 KB)
  3. people can add more then 3 interests, but once they add 10 interests we should a confirmation message under the multiselect lookup. additional interests are not to reload the 'Related articles' and are not considered while creating the pool of suggested edits.
    image.png (856×1,880 px, 270 KB)
QS Lead Support Needed

Yes, this is the fundamental UI that needs to be tested for the associated epic.

Event Timeline

KStoller-WMF moved this task from Needs Refinement to Needs Estimation on the Growth-Team board.

Change #1315932 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] [DNM]: proof of concept for InterestSelector

https://gerrit.wikimedia.org/r/1315932

(proof of concept investigation only, not something ready to be merged)

KStoller-WMF set the point value for this task to 3.Jul 27 2026, 3:03 PM
KStoller-WMF moved this task from Needs Estimation to Up next Sprint on the Growth-Team board.

before updating the task description, i wanted to share a few thoughts in a comment to understand if this is enough to make things actionable, and listing open questions in bold.

  1. when there are no interests selected, the multiselectlookup doesn't display the chip container and we display 'random articles' underneath. it should be possible in the future to evolve the random articles that we show based on different signals.
    image.png (856×1,880 px, 264 KB)
  2. the component(s) should be able to receive a seed article, which is the article where the account creation process was initiated.
    image.png (856×1,880 px, 200 KB)
  3. if a seed article is selected we display 'related articles' via the morelike API or similar.
    image.png (856×1,880 px, 200 KB)
  4. as people add new interests/articles the 'related articles' keep updating.
    image.png (856×1,880 px, 167 KB)
    image.png (856×1,880 px, 218 KB)
  5. what is max number of interests that people can add? during account setup we capped at 3 and we're thinking about inline validation.
    image.png (856×1,880 px, 225 KB)
    image.png (856×1,880 px, 225 KB)
  6. the same combo of components can be displayed during account setup and inside the currently todays know as topic selector.
    image.png (1,712×3,732 px, 334 KB)
  1. people add new interests/articles the 'related articles' keep updating.

Is that mockup correct, shouldn't the "Go to your Home" button be active after 3 interests are added?

  1. what is max number of interests that people can add? during account setup we capped at 3 and we're thinking about inline validation.

Let's limit errors and warnings as much as possible. My preference:

  • set the limit to higher (The "Go to your Home" button should be active after 3 interests are added, but users can continue to add up to 10 interests (or whatever limit engineers think we need to set).
  • after three interests are added, automatically navigate to Home. (And we can consider if we need to add a explanation that interests can be added or updated via the interests picker menu).

Admittedly this logic might be implemented outside of this task? My understanding is that this task is just about creating the component.

  1. people add new interests/articles the 'related articles' keep updating.

Is that mockup correct, shouldn't the "Go to your Home" button be active after 3 interests are added?

i've reduced the opacity of every piece of UI that is outside the scope of this task. apologies for not disclosing that in my message.

  1. what is max number of interests that people can add? during account setup we capped at 3 and we're thinking about inline validation.

Let's limit errors and warnings as much as possible. My preference:

  • set the limit to higher (The "Go to your Home" button should be active after 3 interests are added, but users can continue to add up to 10 interests (or whatever limit engineers think we need to set).
  • after three interests are added, automatically navigate to Home. (And we can consider if we need to add a explanation that interests can be added or updated via the interests picker menu).

Admittedly this logic might be implemented outside of this task? My understanding is that this task is just about creating the component.

ok, i'd wait on the final eng recommendation to set the final design.

Change #1318759 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat: add user-property for articles the user is interested in

https://gerrit.wikimedia.org/r/1318759

Change #1318759 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat: add user-property for articles the user is interested in

https://gerrit.wikimedia.org/r/1318759

Change #1315932 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat: add InterestSelector component

https://gerrit.wikimedia.org/r/1315932

Test wiki created on Patch demo by Etonkovidova (WMF) using patch(es) linked to this task:
https://e0d9ff97ab.catalyst.wmcloud.org/w/

@Michael - the scope of the task seems to be bigger than what is stated in the Note:

This is only about creating the Vue.js component

Should we keep the task open to check the task's ACs when the work will be done? I made the test cases doc to incorporate all info from this task for future QA effort. Also, the patchdemo that I created doesn't present the InterestSelector component (it was expected).

@Michael - the scope of the task seems to be bigger than what is stated in the Note:

This is only about creating the Vue.js component

Should we keep the task open to check the task's ACs when the work will be done? I made the test cases doc to incorporate all info from this task for future QA effort. Also, the patchdemo that I created doesn't present the InterestSelector component (it was expected).

Yes, since the scope was unilaterally widened beyond what was agreed upon, this is not done yet. I moved it back to Doing.

Test wiki on Patch demo by Etonkovidova (WMF) using patch(es) linked to this task was deleted:

https://e0d9ff97ab.catalyst.wmcloud.org/w/

Change #1327122 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat: add new account setup

https://gerrit.wikimedia.org/r/1327122

Change #1331781 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat(AccountSetup): Store the signup origin article as an interest

https://gerrit.wikimedia.org/r/1331781