Get data on project page buttons
What questions are you trying to answer?
Do people use the Download and Add buttons in the project page? They are duplicated in the top bar and the repo widget (if enabled for the project).
Do people use the quick links to Readme, Changelog, Files, Commits, etc.?
Are the dashed-border buttons effective?
Are users overwhelmed by the information density? Does the new layout work well?
What assumptions do you have?
- Users probably don't use the Add button much since the project homepage is not a place where you will typically want to add files or create issues.
- The Download button might have more use, but it also competes with its duplicate in the repo widget below.
- The quick links are so understated that users probably don't notice them much.
- The dashed buttons might not be encouraging users enough to add the missing elements. They might also become annoying if users are not interested in setting up those elements.
- The new project page layout proposed in #44704 condenses the elements of the header, which might make them harder to take in.
Ultimately, what would you like to get out of the research?
- Should we remove the Download and Add buttons from the project description?
- Do their duplicates work well enough on their own?
- Do the quick links and dashed buttons need to be changed?
- What adjustments to the new layout would benefit users the most?
What's the latest date that the research will still be useful to you?
We're implementing changes to the project page in 11.1. Answers to these questions would be helpful so we move with more confidence, but we can still make these changes after that release.
Note: The style of the buttons will change, is a concern towards the outcome of the research? @tauriedavis suggested we test the current design with the buttons and the new one without them so we can compare.
- Write questions [Deadline: Tues 10 July]
- Input questions into testing tool [Deadline: Weds 11 July]
- Create a prototype of the existing design within the testing tool [Deadline: Weds 11 July]
- Create a prototype of the new design within the testing tool [Deadline: Thurs 12 July]
- Test the questions and prototype of the existing design [Deadline: Weds 11 July]
- Test the questions and prototype of the new design [Deadline: Thurs 12 July]
- Write email to accompany study [Deadline: Weds 11 July]
- Distribute the study to a test segment of users [Deadline: Thurs 12 July]
- Review responses and distribute the study to the remaining segment of users [Deadline: Fri 13 July]
- Analyse study [Deadline: Tues 17 July]
- Pay users [Deadline: Weds 18 July]
- Write up findings in a report [Deadline: Weds 18 July]
- Add the report to the UX Research Project's ReadMe [Deadline: Weds 18 July]
- Add the report to the UX Research Archive [Deadline: Weds 18 July]
- Update any relevant issues in the CE project [Deadline: Weds 18 July]