-
Notifications
You must be signed in to change notification settings - Fork 687
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
Design updates for SecureDrop 1.0.0, rev1 #4634
Conversation
09c5e80
to
1ed3f3c
Compare
Asks for @ninavizz:
Huge thanks for getting us this far, really looking forward to doing this refresh as part of 1.0.0 :) |
securedrop/sass/_source_index.sass
Outdated
border-width: 1.5px | ||
border-image-source: linear-gradient(145deg, #0096dc, #005db7) | ||
border-image-slice: 1 | ||
border: 1px solid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you need to remove border: 1px solid
here so it doesn't override the gradient border.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, thanks! (Should be fixed.)
Took a spin through the changes to check the source interface against the four issues listed, and they look pretty good. Made a comment about the one bug I found, preventing the border image gradient on the source index page. The only other thing I noticed was that setting the alpha to 20% for the cloud icon on the submit page would make it too light, IMO -- but that item is as yet unchecked on the issue page, so maybe it's not yet nailed down. |
532737c
to
a2237e4
Compare
65e5c93
to
1de835e
Compare
@ninavizz and I made a fair number of smaller tweaks as we audited the colors and styles used throughout the Journalist and Source UI in the last few days. I've attempted to provide a complete changelog in the PR and in the commit summary. To manage scope, I'm going to call this rev1; at this point, updates to this PR will be to identify issues flagged during review. We'll be discussing the scope of a potential rev2 in the next UX meeting, on August 1. |
bebec52
to
bdbbe8c
Compare
👍 LGTM. The border bug is fixed, and the test changes are good. |
@ninavizz Just a note that the full-size logo in this PR still uses the old keyhole cut; could you provide me with a 500 x 449 resolution transparent PNG version with the revised cut? |
Codecov Report
@@ Coverage Diff @@
## develop #4634 +/- ##
========================================
Coverage 82.67% 82.67%
========================================
Files 45 45
Lines 3122 3122
Branches 338 338
========================================
Hits 2581 2581
Misses 454 454
Partials 87 87 Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## develop #4634 +/- ##
========================================
Coverage 82.67% 82.67%
========================================
Files 45 45
Lines 3122 3122
Branches 338 338
========================================
Hits 2581 2581
Misses 454 454
Partials 87 87 Continue to review full report at Codecov.
|
Updates colors throughout to a new "SecureDrop Blue" and a darker "Grimace Blue", a new "danger" color, and blue gradients on the index page; updates the favicon and the default logo. Resolves #4500 Resolves #4501 Resolves #4502 Resolves #4503 Additional tweaks chiefly agreed upon with Nina Alter (@ninavizz) during pair development: Global: - Removal of some button icons that did not disambiguate meaning - Tweaks to default button letter spacing, font weight - Pick headline color that fits with new overall theme - Ensure consistent use of headline levels - Removed unused colors, styles, icons - More careful spacing between icons and text on buttons - Consistent use of upper case on large buttons Source Interface: - New trashcan icon for deleting replies - Flipped order of introductory text on submit page by importance Journalist Interface: - Restyled timestamps, "0 docs, 1 message" type counters to be less easily confused with buttons - Restyled "Select all" type buttons to not have checkbox icons on them, to ensure they're not confused with actual checkboxes - Added spacing between Select buttons and other actions, to make logical distinction more obvious - Removed download icon from each table row, as it did not convey sufficient meaning to justify keeping it - Removed "Reply" icon from Reply headline, and left-aligned it, for consistency with other headlines - Made textbox the same width as the table above it, and removed fixed column width, to ensure proper scaling across viewport sizes - Right-aligned "Submit" button consistent with other forms - Removed hover from "X" of modals, as it did not really add value here Admin Interface: - Made it more obvious when the Delete icon is disabled Out of scope for this rev: - String changes - Typography changes - Docs screenshot updates (will be done after final rev)
We are no longer changing icon hover state, so it's not useful to continue to test for it.
cd30c12
to
064de4a
Compare
(Rebased.) |
border-top-width: 0 | ||
border-bottom-width: 0 | ||
|
||
.index-left | ||
background: $color_purple_medium | ||
background-image: linear-gradient(140deg, #0096dc, #005db7) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would using variables for theses colors make sense here, since they are reused later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @eloquence @ninavizz this looks great! I've noticed a couple of (what seem to me) inconsistencies in the colors, specifically warning/banners. What do you think? I'll defer to @ninavizz for the final review, otherwise this looks good to me, based on the testing below.
- The Tor Security settings banner remaining the same color and not the same as securedrop.org (should it be urgent coral #f360000 ?:
- The yellow message window appears more muted, less fluorescent than the other colors on the page:
- Same as the above comment, to a lesser extent with the green message box:
. Perhaps a color closer to the GitHub green (which is quite close to the exiting) might be better.
Also performed functional testing as follows:
VM testing
Clean install (staging)
- Navigated through both interfaced per the test plan and did not observe any issues (other than what was described above
- No AppArmor errors
VM Upgrade scenario (using diff below [0] due to #4659)
- Navigated through both interfaced per the test plan and did not observe any issues (other than what was described above
- No AppArmor errors
[0] :
diff --git a/molecule/upgrade/side_effect.yml b/molecule/upgrade/side_effect.yml
index a33bddcd8..250535d33 100644
--- a/molecule/upgrade/side_effect.yml
+++ b/molecule/upgrade/side_effect.yml
@@ -3,10 +3,10 @@
hosts: securedrop
become: yes
tasks:
- - name: Perform safe upgrade
+ - name: Perform dist-upgrade
apt:
update_cache: yes
- upgrade: yes
+ upgrade: dist
- name: Lay out app testing deps
hosts: securedrop_application_server
Thanks for the comments and the careful review, @emkll! You're right that those colors are still not ideal. We kept them out of scope for now to keep scope constrained, but they're easy to change, and your comment encouraged us to poke a little. Nina and I will sync up on that tomorrow and may make some final tweaks here. |
Thank you for flagging the design concerns @emkll! I agree with all of the points you've made. The Get Codename page and all Messaging components need more love than just color tweeks, unfortunately. Adjusting the colors, alone, with the visual language currently used in both would potentially make those parts of the UI look "more broken," than simply untouched by the current round of UI updates. If that makes sense. I'll defer to @eloquence on how to scope agreed to updates across which PRs; this one ( Messaging I'd like to revisit holistically in either a point release, or in 1.1.0. At that time colors, iconography, styling, and text will all be overhauled. The Tor messaging banner(s) on the TL;DR, this PR I'm kosher thumbs-up'ing, with the caveat we get the flagged Get Codename updates into the Rev2 PR. Messaging and Tor things that have been deferred until later, I've documented in this Issue in the UX Repo for consideration +1.0.1 |
That makes sense to me @ninavizz! If the changes that are in here are good to go, I'd love to get those into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -72,7 +72,7 @@ <h2>{{ gettext('Reset Password') }}</h2> | |||
<br> | |||
<span id="password" class="password">{{ password }}</span> | |||
</p> | |||
<button class="sd-button btn" type="submit" id="reset-password"><i class="fas fa-sync"></i> {{ gettext('Reset Password') }}</button> | |||
<button type="submit" id="reset-password"><i class="fas fa-sync"></i> {% filter upper %}{{ gettext('Reset Password') }}{% endfilter %}</button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this work with all locales/languages? We should explicitly test this as part of QA
(Hold on merge for one follow-up commit, we agreed to use |
Dismissing per #4634 (comment) , will re-review
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving once more, css changes in 0cc9bc7 look good to me
Updates colors throughout to a new "SecureDrop Blue" and a darker
"Grimace Blue", a new "danger" color, and blue gradients on the
index page; updates the favicon and the default logo.
Resolves #4500
Resolves #4501
Resolves #4502
Resolves #4503
Additional tweaks chiefly agreed upon with Nina Alter (@ninavizz)
during pair development:
Global:
Source Interface:
Journalist Interface:
Admin Interface:
Out of scope for this rev:
Test plan
When stepping through these paths, make note of any obvious design regressions, or design changes which you are uncertain about ("is it intentional that the hover behavior between these two buttons is inconsistent", etc.).
Deployment considerations
Screenshots