Product theory
The general product approach will be to support “flow through” needs from Notifications first, other talk needs second and intensive page management or administrative needs as least important for v1. We will also not focus in this initial version on the readers but first ensure that basic editing needs are met.
The priority story for this epic is:
When I receive a notification that needs a response, either on my User or Article talk I want to be able to read and respond in a timely and intuitive way.
Based on the design research personas the priority of the Talk user personas for this version is:
- Moderator
- Wordsmith
- Topic Expert
- Reader
- Architect
Must Haves
- Basic display of all discussion content on the page
- The ability to reply "in line" to a comment
- The ability to post and start new pages and sections (topics)
- Empty and common error states with basic user education
- Pages previously visited should be viewable offline, however offline support for post edits to Talk is out of scope
- Ability to understand the timelines and basic activity of the discussion
- Clear licensing and policy information
- Accessibility support for reading, tools and editing (equivalent to support in article editing)
- Support for both User:Talk, article Talk and your own user page, replacing our existing patchwork of experiences for these pages
- Easy signing (exists in current User Talk support)
- Basic "Share" button actions (open in Safari, copy URL, etc)
- Other common page toolbar actions as determined to be vital by design research
- Either "Find in Page" OR Collapsable Topic headers as determined by design research
- Support for all app supported Wikipedia languages and scripts (incl RTL and variants)
Nice to Haves
- Support for "header" or top of the page templates rendered via mobile html
- Basic formatting toolbar in reply editing (bold, etc)
Support Work
- EventLogging of basic usage of tools and editing engagement
Batteries Not Included in V1
- Visual editing, Wikitext syntax highlighting or preview
- more complex template support, both in editing toolbar and reading UI
- Offline editing
- Saving talk pages to permanent or Reading list storage
- Watchlist subscribe/management
- Special or extensive support for complex notice and talk template and page types such as village pumps or Admin notice boards. Depending on the level of templating, we may continue to route these to the mobile web presentation in the in-app browser were unsupportable with a standard article and User Talk approach.
- Read/unread states
Design doc
https://docs.google.com/presentation/d/1wifraOKuy0-p0JPCEHtdfEFQ01u5BYVB22SQiGWnY5M/edit?usp=sharing