1.0 Release UX Punchlist

[ninavizz]

The below are things slated to go into the 1.0 release of the SecureDrop product, that have UX dependencies.

Targeted UX freeze: August 15th, 2019 (2pm PDT)
QA, feature and string freeze: August 20, 2019 (EOD PDT)
Translation Freeze (new): September 1, 2019 (EOD PDT)
Release: September 4, 2019 (EOD PDT)

---

Release Goals: Product Maturity

The primary goal for all UX items slated for the 1.0 release of SecureDrop, are things that tighten the tool's presentation to evoke credibility and cultivate trust for source users. Because we are finally giving the SD product a 1.x versioning, the priority with the below is to establish a solid foundation of trust and credibility upon which future iterations can be made w/ elegance.

What does that mean?

• For source users... based on established mental-models from use of webapps to date:
  • Credibility
    • "Does the SecureDrop experience feel credible and legitimate to me? Is there a real business/vendor behind it, or did some yo-yo in the newspaper's IT department throw it together?"
      • ...because, yes, in Capitalism, someone making money or some other source of authority ruling over an experience, is how we've been trained to evaluate safety and legitimacy... #lesigh
    • "Is this thing broken, or has it been hacked?"
    • "Is it clear to me what the SecureDrop tool is, and the difference between it and the org I'm submitting information to?"
  • Trust
    • "Do I know where I'm submitting information to? Do I know who owns the data once it's been submitted?"
    • "Could this experience have been hacked so that my submission goes somewhere unintended?"

Within the above, it will be important for users to more clearly understand whom each player is in the B2B2C dynamic—as this had been flagged as a likely problem in a prior UX audit, based on today's source Experience diverging from established B2B2C best practices.

Because the Source and Newsroom (journo/admin) UIs share SASS attributes, updates to the Newsroom experience will also go in.

• For journalist and admin users... based on established mental-models from use of B2B2C webapps to date:
  • Credibility: "Is this indeed the correct frontend for our SD instance, or something that's been hacked?"
  • Credibility: "Does this experience align with what I'm seeing across all the other SD touchpoints in my workflow?"

Technical updates in the 1.0 release will be upgrading the codebase to use Python 3.0, and support for Tor v3 onion services. Along with the major brand-presentation overhauls, all of the above make for a nice one-dot-oh boom.

Other branded touchpoints

Action items below pertain to alignment of the brand's presentation across its ecosystem of touchpoints, but the Footer is specifically to foster trust with users—as the footer is a known go-to spot in a UI to pattern-match expected credibility items. Footer updates also dovetail into user expectations around co-branding of B2B2C experiences.

Landing Page Things

Yet to discuss w/ team—all existing org landing pages w/ the SD logo, will need to be updated by those orgs. That will need to be communicated to them, with a rudimentary "Brand Use Guidelines" guide for using the (updated) logomark on their pages. Updates will not need to be done in time for the 1.0 release, but should be done soon thereafter.

• RedMine Comms
• Docs stuff
  • Update Brand/Mark Use Guidelines (or at least create a do/don't advisement)

Journalist/Admin UI Things

Yet to discuss w/ team—do we care if there's a disconnect btwn this and the Source UI? Might it confuse newsroom users?

• Color Schema (basic things—buttons, headers, linx... eliminate steely-blue, nothing fancy)
• Logo use?
• Footer?
  • No link-outs needed, but some parity w/ the Source footer wd be nice... also for credibility/tightness.

Source UI Things

• Color Schema
  • Design solution drafted
  • Solution finalized w/ team signoff
  • Zeplin and/or Invision spec(s) published
  • SD Repo implementation Issue created
  • Assets published w/ links in Issue
  • Standard(s) updated, if relevant
  • UX review(s) of committed code
• Logo update
  • Design solutions drafted
    • ^ that Nina reeeeeally wants to update per Issue TBD, but interim solution finalized.
  • Solutions finalized w/ team signoff
  • Zeplin and/or Invision spec(s) published
  • SD Repo implementation Issue created
  • Assets published w/ links in Issue
  • Standard(s) updated, if relevant
  • UX review(s) of committed code
• Footer
  • Design solution drafted
  • Design solution finalized w/ team signoff
  • Copy finalized w/ team signoff
  • Zeplin and/or Invision spec(s) published
  • SD Repo implementation Issue created
  • Assets published w/ links & copy in SD Repo Issue
  • Standard(s) updated, if relevant
  • UX review(s) of committed code
• TL;DR Page
  • Design solution drafted
  • Solution finalized w/ team signoff
  • Copy finalized w/ team signoff
  • Illustrations finalized w/ team signoff
  • Zeplin and/or Invision spec(s) published
  • SD Repo implementation Issue created
  • Assets published w/ links & copy in SD Repo Issue
  • Standard(s) updated, if relevant
  • UX review(s) of committed code

Ecosystem Things

Who would be implementing these items, and which ones must we prioritize to push in parallel to the 04 Sept release?

• Website Logo updates MUST (nina)
  • Tracking in Update SD logos on Twitter & Website #71
  • Design solution drafted
  • Solution finalized w/ team signoff
  • Copy finalized w/ team signoff
  • Zeplin and/or Invision spec(s) published
  • SD Repo implementation Issue created
  • Assets published w/ links & copy in SD Repo Issue
  • Standard(s) updated, if relevant
  • UX review(s) of committed code
• Tool Logo Updates
  • Tracking in EPIC: Update all SD ecosystem logos for 1.0 #72
  • Twitter
    • MUST (nina)
  • GitHub
    • SHOULD (nina)
  • RedMine
    • MUST, when the Newsroom UIs colors get updated (nina)
  • RTD
    • MUST (nina)
    • Note: Could be strange disconnect if RedMine doesn't and RTD does; ideally we can do both, with minimal color/logo updates to Journalist and Admin UIs
  • Weblate
    • COULD (nina)
  • Forums
    • COULD (nina)
  • ???

[ninavizz]

All but the TL;DR page and updating of standards in RTD and the SD repo, have been completed. cc'ing #83 here to get these needs onto that punchlist, and closing, for now.