Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A new /vulnerabilities experience #990

Open
3 of 9 tasks
andymeneely opened this issue Oct 17, 2022 · 10 comments · May be fixed by #1159
Open
3 of 9 tasks

A new /vulnerabilities experience #990

andymeneely opened this issue Oct 17, 2022 · 10 comments · May be fixed by #1159
Assignees
Labels
enhancement New functionality needs-ux-help Needs help from UI/UX folks
Milestone

Comments

@andymeneely
Copy link
Collaborator

andymeneely commented Oct 17, 2022

Motivation

Currently, the table we have under /vulnerabilities is functional, but it's a little stark as a first impression. For a while we had a "cards" view as an alternative view, but it was a bit too visually busy and had some performance problems so it's disabled now.

Details

Let's use the "accordion" style that was in the branch for #1128.

Tasks

  • Make a mockup of the UI for final polishing
  • Rework the database to include the concept of "tag groupings". Essentially, merge some of the work from Vulnerability Clusters page #1128 (but not all)
  • Tag groupings (e.g. "By Design") have their own descriptions pulled from VHP writing
  • Tag descriptions are cut off after a single sentence.
  • Top 5 most upvoted vulnerabilities are shown using a new "card" format based on Build a vulnerability "Card" using JS #1148
  • Maybe more tasks as I think of them...

Check the following:

@andymeneely andymeneely added enhancement New functionality needs-ux-help Needs help from UI/UX folks labels Oct 17, 2022
@andymeneely andymeneely moved this to 📋 TODO in VHP Becomes a Thing Oct 17, 2022
@andymeneely andymeneely added this to the Spring 2023 milestone Feb 11, 2023
@andymeneely
Copy link
Collaborator Author

Bringing this one back for our next thing. In #1128 I was playing around with a "Clusters" concept but then I realized it would probably be best for this page.

@andymeneely
Copy link
Collaborator Author

image

@andymeneely
Copy link
Collaborator Author

image

@andymeneely
Copy link
Collaborator Author

image

@andymeneely
Copy link
Collaborator Author

image

@andymeneely
Copy link
Collaborator Author

image

@andymeneely andymeneely moved this from 📋 TODO to 🚧 In Progress in VHP Becomes a Thing Jun 6, 2023
@andymeneely
Copy link
Collaborator Author

Here's a rough draft of the mockup. I'd like to incoporate logos and colors into each of the categories, and then the tabs will look a little different than these too. The "D" things are figma comments - ignore.

Image

@andymeneely
Copy link
Collaborator Author

The tabs should look like how they look in this mockup:

image

@Globnartheexquisite
Copy link

I've been working on applying the visual styles of the tags to the categories in the vulnerabilities experience. @andymeneely want to schedule some time next week to discuss me setting up a color/icon organization for all viable tags?

@Globnartheexquisite
Copy link

Globnartheexquisite commented Jul 7, 2023

Some musings on this topic

Possibility 1: Color = Severity, Icon = Category
Possibility 2: Color = Category, Icon = Severity

Both options offer the ability to communicate multiple pieces of information in the smallest package. By using the text in the bubble to apply specifics, we have a chance to offer three pieces of information in each bubble. Category, Severity, and Specificity. However, the trouble with both of these options is that they rely on communicating specific information through color. This is not accessible. In order to rectify this, we will need to deliberately pattern the bubbles in a way that will provide enough visual difference that it provides the same visual cue to a Deuteranopic/Tritanopic/Monochromatic viewer.

Possibility 3: Color + Icon indicate category, text provides specifications.

In option three we are opting to provide two separate depths of information instead. The color and the icon indicate what category the tag falls into, and the text offers up specifics. In this case, it would be nice to have a separate, distinct, “severity” modifier somewhere in the tag cloud, providing a distinction between vulnerabilities that are of interest predominantly for their academic value (akin to the current “neat” tag), and vulnerabilities whose existence caused a vast amount of headache for the internet or specific companies.

Either direction we choose to take, it looks like we have between four specifications in the smaller category tags, and upwards of fifteen in the larger categories. Trying to have discreet icons for each specification would be a headache. Have we selected distinct icons for each tag? And if so, are those set in stone?

@andymeneely andymeneely linked a pull request Oct 3, 2023 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New functionality needs-ux-help Needs help from UI/UX folks
Projects
Status: 🚧 In Progress
Development

Successfully merging a pull request may close this issue.

3 participants