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.

Sign up for GitHub

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

Jump to bottom

EPIC Ongoing Source UI things #83

Closed
11 tasks done
ninavizz opened this issue Aug 14, 2019 · 1 comment
Closed
11 tasks done

EPIC Ongoing Source UI things #83

ninavizz opened this issue Aug 14, 2019 · 1 comment
Labels
EPIC This is a broader thing of which many smaller Issues are tackled. Needs Team Discussion Will this provide value to the whole team—or does the full team agree this is valuable for UX work?? Source Experience UxD User Experience Design (content, visual, interaction)
Milestone
+1.0.1

Comments

@ninavizz
Copy link
Member

ninavizz commented Aug 14, 2019 •
edited
Loading

...creating this right now to track things. Cuz who doesn't like to track things?

Problem

After the 1.0 release has been pushed, the SecureDrop web experiences should continue to be iterated upon. Below is a list of known things to iterate upon, within today's Source experience.

Design Principles

  • From 1.0.0 release
  • Going forward...
    • Follow usability best practices
      • Consistency, patterns; follow the knowledge.
    • Prioritize Inclusion
      • What might work for the widest swath of folks?
      • Written language, translations across languages, semiotics across cultures, color/contrast, legibility, a11y best practices
    • Cultivate Calm
      • Strive for page balance, not decoration.
      • Typography that prioritizes OS native-ubiquity (cough, Tor), legibility, and smooth reading to inform comprehension, in whichever charset the user will be choosing.
    • Clear, human, humble, neutral
      • Visually appealing, without calling attention to itself.
      • SD is the messenger, not the message. Newsrooms are the carriers.
    • Guide behavior to inform safe choices
      • Design for known user needs and motivations, first.
      • Iterate and validate through testing: Written language choices, visual language choices, all contextually within the E2E experience journey.

Yet to prioritize...

  • Update Languages widget (polish styling)
  • Move Codename widget to top of Submit page
  • Add TL;DR/LearnMore page
  • Update messaging styles
  • Update messaging content
  • Revisit "Confirmation" messaging
    • Per inability to do a proper Active state
  • Update "Reply" box styles
  • Revisit Tor messaging/ux
    • Design solution TBD
  • Update body and global typography things
    • More standardizing what's been done per-page in 1.0.0
  • Add Multi-file upload
  • ADMIN UI: Add section for news org name, and populate in Source UI
@ninavizz ninavizz added Needs Team Discussion Will this provide value to the whole team—or does the full team agree this is valuable for UX work?? UxD User Experience Design (content, visual, interaction) EPIC This is a broader thing of which many smaller Issues are tackled. Source Experience labels Aug 14, 2019
@ninavizz ninavizz added this to the +1.0.1 milestone Aug 14, 2019
@ninavizz ninavizz mentioned this issue Aug 14, 2019
Merged
@ninavizz ninavizz mentioned this issue Oct 20, 2019
Closed
57 tasks
@ninavizz ninavizz pinned this issue Oct 20, 2019
@ninavizz ninavizz mentioned this issue Oct 31, 2019
Closed
@ninavizz ninavizz changed the title EPIC +1.0.1 Source UI things EPIC Ongoing Source UI things Jul 20, 2021
@ninavizz
Copy link
Member Author

ninavizz commented Jan 9, 2022

Closing, as items in 2021's SI Redesign, in-motion creation of a Source Safety Guide, and overall team awareness of the need for multi-file uploads (also captured in 2019's SI UxR findings) meet each of the needs outlined in this issue.

@ninavizz ninavizz closed this as completed Jan 9, 2022
@ninavizz ninavizz unpinned this issue Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
EPIC This is a broader thing of which many smaller Issues are tackled. Needs Team Discussion Will this provide value to the whole team—or does the full team agree this is valuable for UX work?? Source Experience UxD User Experience Design (content, visual, interaction)
Projects
None yet
Milestone
+1.0.1
Development

No branches or pull requests
1 participant
@ninavizz