UX meeting 20190508

Attending: @ninavizz, @eloquence, @harrislapiroff, @huertanix, and @Kev

08 May Meeting (60min) Agenda:

The dev kidz are all at PyCon, so let's continue the Source UI discussions and prioritize 2019 small-byte/iterative next-steps!

• General feedback on Source UI design explorations
  • TorThings — proposed message text inaccurate
• Source UI 2019 Punchlist on GitHub: How does this reflect what everyone else thinks iterative-improvement priorities should be?
  • Footer Stuff
    • Yay, Erik!
  • Multi-file upload support?
  • Linked-out educational things?
    • Mirror existing content like docs.securedrop and eff.org/ssd on .onion services
    • Publish bespoke "About SecureDrop" guide as .onion service that explains alltehthings to non-technie users
      • Ahem, such as the convoluted "Flag for Reply"
  • Iterative small-byte other things
    • CSS only?
      • Fonts
      • Retire FontAwesome (~1,000 lines of code in the CSS!)
• Been Readin' + Shoutouts:
  • Tooltip Best Practices — nifty article from Nielsen Norman, guiding composition of alttext/tooltips (communicate about information, not about function)

Notes

Parting Action Items:

• Nina to update Punchlist OG comment and to add a new comment, to reflect how we left next-step priorities
• Mickael & Jen to be consulted with, on Footer + "Learn More" TL;DR Page idea.
  • If all above agree it's a good idea, David/Kev/Erik/Nina to collaborate to suss through what exactly the the Learn More page should say, and how it should say it (between visual and written language, w/in a Journalist Key page template).
  • Nina post-mortem guesstimates a good target for this work would be the 25 June code-freeze for 0.13 release
• Nina to do post-mortem snooping on Noto, and open ticket in SD repo with CSS rec for font recommendation
• Mickael still needed to provide feedback on interstitial possibility for TorThings bit.

---

Note: "General Thoughts" on Source UI design explorations, was again not discussed. If you've come to read this page, your eyes and curiosity are requested to poke through this prototype & provide async feedback to @ninavizz... :)

• Thoughts on Punchlist
  • Kev:
    • Changing alt tag is easy
    • Including newsroom name as a future feature seems like a neat idea
  • Fonts:
    • Update to System Font, discussed
    • Update to Noto, settled on as tentative desired target
• Footer discussion
  • Erik:
    • Linking to external websites creates paths through exit nodes that could leave correlative paths that could get Sources in trouble.
    • Current site nicely sparse wrt links outside
    • Defensive language—this is not sufficient, but we acknowledge this is "too late"
    • David/Kev, What else might be high priority advise to integrate into the Source UI?
  • David:
    • Speaks to R.W. case
    • Understanding browser history; there was a lot of stuff on sized devices
  • Kev:
    • How to speak to sources about what they're doing may be illegal?
    • Recommend compartmentalization (more boldly)?
    • If you use SD, don't use other methods of communication
  • Nina:
    • Value in "Read More" link-out page is radical focus; the person who will benefit from this page is also the person who will just not invest the time in reading through the Source Guide Kev/David. What are the most valuable 500 words for us to communicate to the person who just won't take the pains to do the research they really should?
  • Erik:
    • Should Read More be hosted by news orgs on their websites?
    • What might Jen and Mickael think? They need to have say if this should even be in the Source UI
    • Technically this is very easy to add, but we need to be clear WHAT the 500 words should be, and if this is even a good idea at all.