code-423n4 / code-423n4/code423n4.com
Improve UX of contest reports
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 179
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Opportunity:
We have a huge and growing data source of contests reports. As of today, we give access to these reports by contests.
We could improve this UX by giving some possibilities to make some research in reports, sort the reports with some specific keys.
Example:
-as a user, I would like to see all the High severity findings ...
-as a sure, I would like to be able to search for specific findings
Desired outcome:
Re-working the UI/UX, add possibility to make some research through these reports, look by type of breaches found …
Proposed solution:
- @tealtigrrr to rethink UI ?
- Implement searching system
- Maybe think about some TAGS in the future for people to be able to look up to specific breaches
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing contest-based reports UI and how report data is presented. Define the search and sorting behavior for findings, including severity and breach type; the work is done when users can research reports beyond selecting a contest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100