-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
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. |
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? |
Some musings on this topic Possibility 1: Color = Severity, Icon = Category 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? |
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
Check the following:
The text was updated successfully, but these errors were encountered: