Context
This task continues design work from T426702: Design prototyping: Personal Dashboard + Homepage [FY26-27, Deepen Engagement 1.3], which explored Dashboard layout paradigms, onboarding simplification, and navigation, and T420862: Early Design Ideation: Personal Dashboard + Homepage [FY26-27, Deepen Engagement 1.3] before it.
We are now moving from exploration to definition: the parent task T432668: Design: Pilot wiki release of Home (MVP to replace Newcomer Homepage) covers the final designs and specs for the pilot wiki release of Home. This subtask covers only the Suggested Edits module.
For this release we are aiming to improve second-week retention.
https://www.mediawiki.org/wiki/Contributors/Strategy
Task Objective
Produce final mobile and desktop designs and specs for the Suggested Edits module on Home, sufficient for engineering handoff.
The module must:
- Be capable of fully replacing the Suggested Edits experience for pilot wikis
- Be mobile-first: all core flows optimized for mobile, with desktop parity
- Use Codex components when logical
- Be designed for the new Home view, which is delivered technically via the PersonalDashboard extension.
- Limit suggestions to a motivational and achievable number
Designs
- Mobile and desktop layouts for the Suggested Edits module on Home
- All module states: loading, populated, empty/error
- The post-account-creation flow: what a new account holder sees on first landing, and how the module reflects choices made (or skipped) during account setup
UX specs & display states needing definition
Post-account-creation flow
- If the user completes account setup (interest/topic selection), how are their selections reflected in the module on first view?
- If the user skips account setup, what default suggestions do we display, and do we prompt them to add interests later?
- If suggestions don't exist for the indicated interests, what do we display? Do we fall back to other topics, and how do we communicate that?
- If the user completes all available suggestions, what do they see?
Module display states
- Suggestions fail to load (error state): what messaging and retry affordance do we show?
- Can the user minimize or dismiss the module?
Content & layout edge cases
- Long article titles, missing article images, and truncation behavior on small viewports
- RTL layouts and long translated strings
Acceptance Criteria
- Final mobile and desktop designs for Suggested Edits on Home
- All module states designed (loading, populated, empty/error)
- Specs documenting display states and conditional logic, sufficient for engineering handoff







































