Page MenuHomePhabricator

Community Picks: Feed Layout & Framework
Closed, ResolvedPublic8 Estimated Story Points

Description

Background / Description

The new explore feed introduces a "Community" tab that surfaces articles, stories and resources curated by and about volunteer editors and contributors across the Wikimedia movement. This task covers the overall feed layout and framework — including the disclaimer, date header, language switching behavior, and the "See past from the community" entry point. Getting this foundation right ensures all individual content modules have a consistent and reliable container to live in.

User Story

As a reader opening the explore feed, I want to see a clearly organized feed of community curated content in my preferred language, so that I can easily discover what Wikipedia's volunteer editors have highlighted today.

Requirements

  • ✅ The "Community" tab should display a disclaimer at the top of the feed: "Content and resources selected by and about the Wikimedia community."
  • ✅ Below the disclaimer, the feed should display today's date followed by the content modules in order
  • ✅ Content should be sourced from the user's selected language wiki. If the user changes their language, the feed should reload pulling content from the newly selected language wiki
  • Modules that do not exist in the selected language wiki should be hidden automatically
  • ✅ At the bottom of the feed, users should see a "See past community content" button that loads the same set of modules from previous days
  • ✅ The language selector should be visible in the feed header and allow users to switch languages
    • ✅ The feed should immediately refresh after language change
  • The order of the modules in this section of the feed is Featured Article, Top Read, Did You Know, Today's Featured Picture (from the language), In the news, On this day, Picture of the day (from Commons), Media of the day (Commons)

Design Link

Figma link: full Community tab view →
Figma link: Change language interaction →

Event Timeline

Seddon triaged this task as Medium priority.Mar 17 2026, 4:47 PM
HNordeenWMF raised the priority of this task from Medium to High.Apr 8 2026, 9:33 PM
cooltey set the point value for this task to 5.Apr 13 2026, 7:17 PM
cooltey changed the point value for this task from 5 to 8.

Links now pointing to "Phase 1" board - no ux updates

Moving this to blocked and waiting due to this discussion: https://wikimedia.slack.com/archives/C7P3N5E6P/p1776988680623129?thread_ts=1776985002.547749&cid=C7P3N5E6P - I need to align with @HNordeenWMF and you @cooltey if you want to address the issue in this ticket or a new one. I'll work on the mockup updates tomorrow.

Haley prioritized this as a P1 - I will move columns and would love to update this in the near future since it looks odd! I will add this to the refinement ticket we have. Thanks!

Not working for me on 50584-alpha-2026-05-05.
Tested on:
Pixel 6 on Android 16
OnePlus 8 on Android 13
Galaxy A36

Steps:

  • Tap For You on the last onboarding screen
  • View the building animation
  • Home feed appears

At this point the For You feed is behind the Community feed

Not working for me on 50584-alpha-2026-05-05.
Tested on:
Pixel 6 on Android 16
OnePlus 8 on Android 13
Galaxy A36

Steps:

  • Tap For You on the last onboarding screen
  • View the building animation
  • Home feed appears

At this point the For You feed is behind the Community feed

Hi @ABorbaWMF

This is fixed. Please download the APK from the repo below to see the changes. Thank you!
https://github.com/wikimedia/apps-android-wikipedia/pull/6446

Works for me on 50585-alpha-2026-05-08
Tested on:
Pixel 6 on Android 16
OnePlus 8 on Android 13
Galaxy A36

P1 fix: Order not quite correct

Current order
Featured Article, Top Read, Picture of the day (from Commons), In the news, On this day

Correct order based on Requirements & what we're doing in Phase 1
Featured Article, Top Read, In the news, On this day, Picture of the day (from Commons)

P0 Fix: Language inconsistencies

Matching device language

  • Explanations of module types (subtitles below module titles)
  • Dates ("Today, May 6, 2026)
  • "Views" on Top read
  • Article card 3-dot overflow menu

Matching feed language

  • Module titles
  • Overflow menu for modules (Hide this card, hide this module)
  • See more CTAs like "More on this day"

@SChekfa-WMF do you have a recommendation here on what we should do based on Android platform norms? My proposal is to update all to Device language.

Screenshot_20260512-183721.png (1,080×2,400 px, 253 KB)

Screenshot_20260512-183725.png (1,080×2,400 px, 2 MB)

Hi @HNordeenWMF

FYI, for the following items:

Explanations of module types (subtitles below module titles)
"Views" on Top read

Because these are new strings that do not have translations, that's why they show up in English instead of the feed language.

P0 Fix: Language inconsistencies

The current logic is for everything inside a Feed card to be in the language of that card (as is done in our current Explore feed).
At the moment, however, not all of the new strings have been translated by the TranslateWiki volunteers, and untranslated strings will default to English.

@Dbrant & @cooltey
thanks for the clarification! Of course, makes sense that translatewiki strings aren't in yet. Will the article card 3-dot menu options also be translated & show in feed language?
It would be weird if the article card 3-dot was in a different language than the module-level 3-dot menu.

@Dbrant & @cooltey
thanks for the clarification! Of course, makes sense that translatewiki strings aren't in yet. Will the article card 3-dot menu options also be translated & show in feed language?
It would be weird if the article card 3-dot was in a different language than the module-level 3-dot menu.

Hi @HNordeenWMF

We can update the menu options to show in the feed language.

It would be weird if the article card 3-dot was in a different language than the module-level 3-dot menu.

If you look at the existing overflow menu, it is showing in the device language. (You can long-press on the top-read item.)

@Dbrant & @cooltey
Will the article card 3-dot menu options also be translated & show in feed language?
It would be weird if the article card 3-dot was in a different language than the module-level 3-dot menu.

Our current (old) Explore feed behavior is for overflow menus to be in the device language, since overflow menus are semantically part of the higher-level app UI, like the bottom navigation, etc.
As a multilingual user, I don't find this weird. But if necessary we can make overflow menus in the new feed match the selected language, and deviate from the device language.

Ok, if you feel like it makes sense as a multilingual user, then it's fine by me! I don't use the app often in a second language other than for testing.

Hi folks, overall this is looking good but I'm not seeing Featured Article showing up in languages that do have Featured Articles (example: Spanish, French, Russian, although it did show up on ZH-CN)

Screenshot 2026-05-14 at 4.15.02 PM.png (820×1,786 px, 326 KB)

If this is expected, then we need to add bottom padding to the date header (16pt) ahead of the 'On this day' unit or swap the order to have a card that doesn't have a background fill appear first.

Hi @cmadeo

Hi folks, overall this is looking good but I'm not seeing Featured Article showing up in languages that do have Featured Articles (example: Spanish, French, Russian, although it did show up on ZH-CN)

Upon checking the feed/featured API, it is expected that es, ru, etc., do not have tfa (The featured article) in the response.

If this is expected, then we need to add bottom padding to the date header (16pt) ahead of the 'On this day' unit or swap the order to have a card that doesn't have a background fill appear first.

Yes, but if you look at the design, there is no padding between the date header and the featured article:

Screenshot 2026-05-14 134048.png (426×685 px, 255 KB)

If we add 16dp padding to the bottom of the date header, the space between the featured article and the date header will look larger.

standby - we could do something slightly hacky to explicitly add spacing below the date header only in the cases where the next card has the darker background.