Page MenuHomePhabricator

Make community nominated collection the default filter on the CX dashboard
Closed, ResolvedPublic4 Estimated Story Points

Description

When a community has nominated their most important collection, it should be the default filter in the Content Translation dashboard.

Screenshot 2025-10-30 at 11.50.32 AM.png (312×796 px, 35 KB)

It should stay visible in the suggestions view when not selected.

Screenshot 2025-10-30 at 11.50.40 AM.png (296×804 px, 34 KB)

If several collections are nominated, they should all be present and the first one (alphabetically) should be selected by default.

Design details

1. Community nominated collection becomes the default selected filter
When a community nominates a vital collection for their language, that collection automatically becomes the default filter when users land on the Content Translation dashboard.

2. Cross-wiki visibility
The nominated collection is shown based on the target language of the translation pair, not the wiki the user is currently on.

Example: A user opens Content Translation on Hindi Wikipedia, but their language pair is English → Spanish. If the Spanish community has nominated a vital collection, that Spanish collection will be shown as the default view even though they're on Hindi Wikipedia.

3. Collection remains visible when not selected
Even when the user switches to a different filter (like "Popular" or "Topic"), the community-nominated collection stays visible in the filter chips. Users can easily switch back to it at any time.

4. Collection chip label
The vital collection chip should display the collection name as provided by the community (e.g. ,"WikiForHumanRights 2025 in Nigeria")

5. Collection chip icon
The vital collection chip should use the standard collection icon(cdxIconArticles) to maintain visual consistency with other collection filters.

Additional Notes

  • If the target language has no nominated vital collection, the tool should work as it currently does with the default filter layout and behavior unchanged.
  • Default behavior is consistent across all user types (new/returning users see same experience)
  • The "why this collection is shown" explanation will be handled in a separate task(T408838)

Derived Requirement

Ensure that when a community has nominated one or more vital collections for a target language, the Content Translation dashboard automatically selects a nominated collection as the default filter on initial load, determines the default selection predictably when multiple collections exist, bases the nominated collection solely on the target language of the translation pair, keeps nominated collections accessible when users switch filters, and preserves existing dashboard behavior when no nominated collection is available.

Test Steps

Test Case 1: Auto-select nominated collection on dashboard load

  1. Open the Content Translation dashboard.
  2. Configure a translation pair where the target language has a community-nominated collection.
  3. Observe the active filter immediately after the dashboard loads.
  4. ✅❓❌⬜ AC1: Confirm that a community-nominated collection is selected as the default filter on initial load.

Test Case 2: Determine nominated collection based on target language

  1. Open Content Translation from a wiki that is different from the target language wiki.
  2. Set a translation pair where the target language has a nominated collection.
  3. Observe the default filter shown on the dashboard.
  4. ✅❓❌⬜ AC3: Confirm that the nominated collection is determined by the target language community and not by the wiki where Content Translation was opened.

Test Case 3: Keep nominated collection available when switching filters

  1. With a nominated collection selected by default, switch to a different available filter.
  2. Observe the list of available filters.
  3. Switch back to the nominated collection.
  4. ✅❓❌⬜ AC3: Confirm that the nominated collection remains available when not selected and can be reselected at any time.

Test Case 4: Preserve existing behavior when no nominated collection exists

  1. Open the Content Translation dashboard for a target language with no community-nominated collection.
  2. Observe the default filter selection and available filters.
  3. Compare the behavior with the current baseline experience.
  4. ✅❓❌⬜ AC4: Confirm that existing default filter behavior and layout remain unchanged when no nominated collection is available.

Test Case 5: Apply consistent default behavior for all users

  1. Open the Content Translation dashboard as a new user.
  2. Open the Content Translation dashboard as a returning user.
  3. Compare the default filter selection in both cases.
  4. ✅❓❌⬜ AC5: Confirm that the default selection of the nominated collection behaves consistently for new and returning users.

QA Results - TestWiki

Event Timeline

SBisson triaged this task as High priority.Nov 5 2025, 7:18 PM
SBisson moved this task from Incoming to Prioritized on the LPL Hypothesis board.

Change #1203032 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/ContentTranslation@master] CX dashboard: Make community nominated collection the default filter

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

ngkountas changed the task status from Open to In Progress.Nov 7 2025, 2:53 PM
ngkountas moved this task from Prioritized to Needs Code Review on the LPL Hypothesis board.
ngkountas moved this task from Needs Code Review to In-progress on the LPL Hypothesis board.
ngkountas set the point value for this task to 4.Nov 10 2025, 2:15 PM

Change #1203032 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] CX dashboard: Make community nominated collection the default filter

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

Change #1206444 had a related patch set uploaded (by Sbisson; author: Sbisson):

[mediawiki/extensions/ContentTranslation@master] CX3 Build 1.0.0+2025111

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

Change #1206444 abandoned by Sbisson:

[mediawiki/extensions/ContentTranslation@master] CX3 Build 1.0.0+20251117

Reason:

Skipping the CX build this week

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

Change #1210670 had a related patch set uploaded (by Eamedina; author: Eamedina):

[mediawiki/extensions/ContentTranslation@master] CX3 Build 1.0.0+20251124

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

Change #1210670 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] CX3 Build 1.0.0+20251124

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

@ngkountas Can you review AC1 for Mobile and Tablet compared to the task description? It says "Popular" is removed and "For You" if it has sufficient space, but it still acts like the Desktop. Does the task description need to be updated or is Mobile and Tablet are wrong?

Test Result - Test Wiki

Status: ✅ PASS ❌ FAIL
Environment: Test Wiki
OS: macOS Tahoe 26.1
Browser: Chrome 143
Device: MBA
Emulated Device: NA

Test Artifact(s):

Test Steps

Test Case 1: Auto-select nominated collection on dashboard load

  1. Open the Content Translation dashboard.
  2. Configure a translation pair where the target language has a community-nominated collection.
  3. Observe the active filter immediately after the dashboard loads.
  4. AC1: Confirm that a community-nominated collection is selected as the default filter on initial load.
✅ Desktop❌Mobile❌Tablet
2025-12-24_14-38-37.png (1×1 px, 159 KB)
2025-12-24_14-39-10.png (912×1 px, 136 KB)

Test Case 2: Determine nominated collection based on target language

  1. Open Content Translation from a wiki that is different from the target language wiki.
  2. Set a translation pair where the target language has a nominated collection.
  3. Observe the default filter shown on the dashboard.
  4. AC2: Confirm that the nominated collection is determined by the target language community and not by the wiki where Content Translation was opened.

Test Case 3: Keep nominated collection available when switching filters

  1. With a nominated collection selected by default, switch to a different available filter.
  2. Observe the list of available filters.
  3. Switch back to the nominated collection.
  4. AC3: Confirm that the nominated collection remains available when not selected and can be reselected at any time.

Test Case 4: Preserve existing behavior when no nominated collection exists

  1. Open the Content Translation dashboard for a target language with no community-nominated collection.
  2. Observe the default filter selection and available filters.
  3. Compare the behavior with the current baseline experience.
  4. AC4: Confirm that existing default filter behavior and layout remain unchanged when no nominated collection is available.

Test Case 5: Apply consistent default behavior for all users

  1. Open the Content Translation dashboard as a new user.
  2. Open the Content Translation dashboard as a returning user.
  3. Compare the default filter selection in both cases.
  4. AC5: Confirm that the default selection of the nominated collection behaves consistently for new and returning users.

@GMikesell-WMF you are right, the task description was outdated. I removed the conflicting part ("Responsive behaviour") from the description. I think we can close this task as done.

Ok, sounds good. I will move this to Sign-off.

GMikesell-WMF updated the task description. (Show Details)
GMikesell-WMF moved this task from Needs QA to Design Signoff on the LPL Hypothesis board.

Looks fine to me, hence moving to product signoff