Background & research:
As part of the DE 1.3 hypothesis, one of the explorations on driving second-week editor retention centers on displaying tasks that a new editor can undertake in a feed style.
While a Q1 FY26-27, exploration will mostly focus on testing the feed style itself using the existing suggested edits endpoint, at some point in Q2 FY26-27 building a personalised "Explore" feed that accepts multiple feed sources other than Suggested edits will be attempted.
High level discussions are ongoing to figure out key issues like:
- How to approach Personalisation - What sources do we use to aggregate articles e.g. last-edited, watchlist, saved articles. Which sources are the most relevant to consider e.t.c.?
- How to approach Orchestration of various feed sources - What will handle the orchestration of different feed sources and provide a common entry point to getting the feed? A dedicated extension / A module in an existing extension that then gets extracted into a dedicated extension later on?
- How to serve the feed Optimally - Will the feed be pre-computed? Is it going to use caching? Will it use a job to handle feed population in the database?
This Epic could be a central place to track the related technical exploration work related to the multi-source explore feed, since this will most likely be a multi-team effort.
Design:
An early exploration by @AAlhazwani-WMF of how the "Explore feed" could look like:
Architecture:
An early data flow proposal by @Michael after a chat with @Mooeypoo on how the explore feed could work
