Readers/Reader Experience
|
Reader Experience
Enhancing familiar core ways of learning and engagement.
|
The Reader Experience team focuses on enhancing familiar core ways of learning and engagement. Our work aims to improve and refine the foundational experiences that users rely on for browsing, navigating, and consuming content. Investments in this area focus on driving enhancements to the usability, personalization, and trustworthiness of the platform.
Team members
[edit]-
Jan Drewniak
Engineering Manager -
Jon Robson
Principal Software Engineer -
Eliza Blackorby
Movement Communications Specialist -
Sneha Patel
Lead UX Designer -
Anne Tomasevich
Staff Software Engineer, tech lead -
Volker E.
Staff Software Engineer -
Katie Filbert
Senior Software Engineer -
Loren Mora
Software Engineer -
Steph Toyofuku
Senior Software Engineer -
Bernard Wang
Senior Software Engineer -
Hsuanwei Fan
Senior Product Manager
Projects
[edit]Our hypothesis is that if we run an A/B test experiment on logged out users to display subtle variants of the donation entry point for both mobile and desktop, we will observe a 2% higher number of donations via the treatment paths, as compared to control. Owner is Steph, delegate owner is Jan.
Our hypothesis is that if we give logged-in readers the ability to save articles to a private reading list, we expect engagement on the site to increase, as measured by a 5% increase in internal referral traffic for readers who use the feature, and a statistically significant increase for all users. Owner is Jan, delegate owner is Anne.
- WE3.3.5 Collections
Our hypothesis is that if we conduct a user study that allows web readers to collect/curate content from Wikipedia, then at least 10% of participants will save two or more distinct types of content (e.g. articles, excerpts, media) to a collection. Owner is Sneha, delegate owner is Justin.
Maintenance of Web Team Work
[edit]Contact
[edit]Reporting an issue
[edit]The Reader Experience Team tracks all engineering related work on our backlog board in Phabricator. To submit an issue, please follow these steps:
- Search first: Before creating a bug, check Phabricator search to see if the issue's already been reported.
- Confirm ownership: Make sure the issue falls under the Reader Experience team's stewardship or team mandate. Check the Developers/Maintainers page if it's regarding a specific extension or skin.
- File a bug
- Use the Phabricator Bug Report template
- Tag the task with
#reader-experience-team - Add any relevant component tags (e.g.
#vector-2022,#minervaNeue)
If you have access to Wikimedia's internal Slack, please post in the #talk-to-reader-experience channel after creating the task to get direct feedback.
Requesting a feature
[edit]Before submitting a feature request, understand that the Wikimedia Foundation undergoes a rigorous Annual Planning Process to determine which features to pursue in any given year. Your feature request is most likely to be accepted if it falls within an existing annual plan initiative.
First, consider adding your feature request to the Community Wishlist to have it more formally integrated into our planning process.
Alternatively, you may submit a task to request a feature as well:
- File a feature request
- Use the Phabricator Feature Request template
- Tag the task with
#reader-experience-team - Add any relevant component tags (e.g.
#vector-2022,#minervaNeue)
If you have access to Wikimedia's internal Slack, please post in the #talk-to-reader-experience channel to get feedback from our product manager.
If you don't have access to Phabricator, see phabricator/Help#Creating your account for detailed instructions on how to create one.