Reader Experience has shared a branch for Collections. The cards in T439985 are built on top of it, so we need to understand how it works before adding our signals. This task covers the review and the first steps of the build. The full card requirements live in T439985, and the quality signal details in T434701.

Part 1: Review the branch

• Get the branch running locally and on a test wiki.
• Document how Collections stores lists and pages, including pages from other wikis.
• Find the existing card component and how it's rendered on desktop and mobile web.
• Check which card data Collections already fetches (title, short description, lead image, wiki name) and what we'd need to add (views, quality, needs).
• Propose where our editing data should live relative to a Collection, and review it with Reader Experience before building on it.
• Note anything in the branch that would block or complicate T439985.

Part 2: Plan and start the build

• Break T439985 into build steps and estimate each. Suggested order:
  1. Base card: title, link, wiki name, short description, image or placeholder
  2. View count with trend
  3. Quality as impact and needs signals (T434701), including the +N expand
• Start step 1 behind a feature flag, off by default.

Acceptance criteria

• Branch runs locally and on a test wiki
• Short write-up of how Collections is structured, what card data it already provides, and what we need to add
• Data storage approach agreed with Reader Experience
• T439985 broken into build steps with estimates, added as comments or subtasks
• Patch for the base card (step 1) up for review, behind a feature flag

Dependencies

• Access to the Collections codebase
• Reader Experience availability to review the storage approach