User Story:
As a newcomer, I don't want to be forced to understand the complexity of different namespaces and edit types, because getting started on the wikis is confusing enough.
As a more experienced editor that continues to use Growth features, I want the homepage to provide relevant data about my impact and edit count.
Description
The old impact module counted ALL edits, but we wanted to limit the new impact module to just article edits because that's primarily the impact we focus on in the Article list / view count data.
However, this change is causing confusion on the pilot wikis and doesn't scale well.
There was consensus from all four Ambassadors that it would be better to switch the count back to Total edits. Reasoning:
- Consistency: Article edits isn’t really a term / count used elsewhere
- Simplicity: New editors likely have a similar Edit count and Article count, and they don’t really need to understand the difference immediately
- Motivation: Total edits will be higher and more attractive / motivating for newcomers
- Community: being part of the community involves more than just editing articles, incentivizing discussion (talk page edits) and other edits makes sense.
Acceptance Criteria
Given I have the newcomer homepage enabled,
When I view the new impact module,
Then the following data relates to all edits, not just mainspace edits:
- Edit total
- Thanks received
- Last Edited
- Longest streak
- Your recent activity (data visualization)
Completion checklist
Functionality
- Every subtask involved in the user story should have its associated tasks in Phabricator
- Every related task should pass its Task Completion Definition checklist
- Tests for every involved task should pass
- Build process for every involved task should pass
- Coverage for every involved task should have improved or stayed the same
Design & QA
- Must be reviewed and approved by the design/UX team
- Must be reviewed and approved by Quality Assurance
Deployment
- Is publicly available in the required environment.
Documentation
- Must have related and updated documentation
- Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
- Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on Extension:GrowthExperiments or Extension:GrowthExperiments/Technical documentation pages.
