User:Elitre (WMF)/Sandbox1
 |  This page is currently a draft. More information pertaining to this may be available on the talk page. Translation admins: Normally, drafts should not be marked for translation. |
| Whatever | |
|---|---|
| this project is supposed to achieve. | |
| Group: | Community Tech |
| Team members: | Joydeep Sengupta, Dayllan Maza, Harumi Monroy, MusikAnimal, Sam Wilson, Karolin Siebert, Sandister Tei, Sammy Tarling |
| Lead: | Joydeep Sengupta, Dayllan Maza and Karolin Siebert (Product Owners) |
| Updates: | Updates |
Whatever was the #??? wish in the Community Wishlist Survey 20??. The objective of the wish is to ... This page outlines Community Tech's approach to addressing the needs expressed in this wish's proposal. Link here to talk page - Please leave feedback if you have any.
Background & Problem Space edit
Here they explain what exists, what works and what doesn't.
The number one wish on this year’s (20??) Community Wishlist Survey was ProjectNameHere. VERIFY: This wish has appeared more than once on the different wishlists.
This wish called for an improvement on something...
Existing gaps: Product, Technical, and Design Debt edit
While researching this issue, we discovered that... Maybe add a list.
Anything worth further highlighting? edit
If so, add it here.
Scope of Work & User Stories edit
User Story requirements edit
Example: As a persona, when I do something, I want to outcome of my action, so that I can understand...
MVP Requirements
As a persona,
- I am able to do this.
Ideal Scope Requirements
As a persona,
- I will be able to do something.
Scope and Constraints edit
For the purpose of this improvement led by Community Tech, we will NOT be prioritizing... list follows.
While we may hold meetings with those teams and share knowledge about what our user research and technical investigations unveil, we will not be taking on the work of engineering the fixes yada yada.
We will only be working on the core experience of doing this thing, this means that explicitly, there will NOT be design requirements around:
- this other thing: We will not be focusing on how people do this other thing
- Other actions that users can take...
The above are all outside of the scope of what this team will focus on due to resourcing. We are aware of other internal efforts by the a different team to address these other issues.
Design debt and plans:
Data Investigations edit
List of questions here about data needs
Why and how did we accept this wish edit
This wish scored high in our prioritization process for 20??. It was - judgement based on their matrix.
Design Research edit
So far, we've ran some (unmoderated?) user search to understand... Please see the research protocol attached in the form a PDF together with the insights analysis in video form, or whatever is available.
X scores:
- 4.5/5: content addition experience received an average ranking in terms of clarity - if it applies, this is a list
Status Updates edit
August 30, 2023 edit
Say something here.
Thank you to all of you who took the time to engage with us and provide feedback on the Talk page link here, maybe. We read through all of the feedback and did an aggregate analysis on the points made. We then combined your feedback on those proposed designs, as well as unmoderated user research, and we've finalized the proposed designs to go into engineering for the improvements regarding the wish changes. Please see the designs in this update which include - a list would follow, but this content should probably not be added initially.
In addition, a demo of the changes would go here if it existed. Before you try out the demo to give us feedback, please note:
- It's a work in progress, our QA engineers are currently doing this thing...
- The demo page does NOT include all final UI changes but can give testers a good sense of how the completed experience will end up looking.
- To use the demo, instructions here.
We'd love to hear your feedback on our Yet another link to the Talk page here!
Next Steps edit
- This would be the first: explain, then add more if necessary.
We also want to include big thank you in this update to someone's name here, who graciously stepped up to help us with something. We are always happy to receive support fulfilling wishes from other humans that have the expertise necessary to fulfill a wish even if they are not in the Community Tech team.
We're looking forward to hearing from all of you!
Open Questions from first update: We want to hear from you! edit
- Are there questions? If so, they will be listed here.
Yet Moar Updates edit
Community Tech has some upcoming releases regarding ProjectName in the coming months. Here's where they are explained.
The table below tracks the releases on Phabricator. It would need to be changed if relevant.
| # | Task | Code (Core, VE, Wikidiff2) | Release dates |
|---|---|---|---|
| 1 | Inline Diff: Add legend and tooltips | Core and MobileFrontend | |
| 2 | Better Diffs: Wikidiff2 revise algorithm | Wikidiff2 | |
| 3 | Add dropdown to allow switching between "Difference between revisions" formats | Core and VE | |
| 4 | Dropdown: VE should add the `Visual` diff format option to dropdown | Core and VE | |
| 5 | Dropdown: mobile version should only show options 'Visual' and 'Wikitext' in switch dropdown | Core and VE | |
| 6 | Dropdown: update "Review your changes" modal with a switch diff dropdown | Core and VE | |
| 7 | Two Column: Symbol and visual marker changes | Core and Wikidiff2 | |
| 8 | Two Column: one or more lines added or removed | Core and Wikidiff2 | |
| 9 | Inline Diff: Visual marker changes | Core and Wikidiff2 |
Relevant Links edit
Don't forget to change the categories.