Readers/Reader Experience

Contact us

• About the Foundation
• Movement Resources
• News and Events

Main Help

• Office of CEO
• Advancement
• Communications
• Finance and Administration
• Legal
• Product and Technology
• People

We build and maintain software focused on enhancing familiar ways of learning and engagement for active readers.

The Reader Experience team focuses on enhancing 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.

Back to Readers

---

Team members

• 
  Hsuanwei Fan
  Senior Product Manager
• 
  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

Projects

• Donate button A/B test

• Reading lists

Maintenance of Web Team work

• Search suggestions

Contact

Reporting an issue

The Reader Experience Team tracks all engineering related work on our backlog board in Phabricator. To submit an issue, please follow these steps:

1. Search first: Before creating a bug, check Phabricator search to see if the issue's already been reported.
2. 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.
3. File a bug
   1. Use the Phabricator Bug Report template
   2. Tag the task with #reader-experience-team
   3. 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

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:

1. File a feature request
   1. Use the Phabricator Feature Request template
   2. Tag the task with #reader-experience-team
   3. 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.

Team documentation

Team Processes