Skip to content

Information Architecture

Jump to bottom
Harris L edited this page Sep 20, 2017 · 10 revisions

Initial site map. This is not set in stone yet, so don't get too attached to anything specific, but it's good enough that we can start working from it.

  • 📄 Homepage
    • Hero header with SD logo, title ("Secure Drop"), subtitle, and about blurb
    • Prominent block with tech details including:
      • latest release
      • link to release news items page
      • link to GitHub
      • link to contributor page
    • CTA for sources to visit the directory
    • CTA for donation
    • News item previews
  • 📄 News
    • Should have an RSS feed that is also filterable by post category (use case: I want to subscribe to release announcements)
    • 📄 Category (see F.P site for reference on the technical aspects here)
      • Blogs posts on the current SecureDrop.org can be divided into these larger types. These may correspond to the ultimate category taxonomy in some way:
    • 📄 Blog posts
      • is in one or more categories
      • does not necessarily have an author, but could
      • should support a plethora of streamfield blocks including but not limited to:
        • headings
        • rich text
        • code blocks (e.g., preformatted code)
        • raw HTML blocks
        • embed blocks
        • blockquotes
      • probably makes sense to allow release announcements to be associated with a specific Release object
  • 📄 Overview
    • Marketing details
    • Project history
    • CTA for getting started
    • Links to technical details, documentation, and contact
  • 📄 Search
    • Show search results for:
      • pages on the site
      • discourse posts
      • documentation
    • 🛠❓ How should this search be implemented technically? It seems like we'll need to index non-database objects. I know this should be possible with elasticsearch. Is it possible with postgres search? Can we do it with wagtail search? How low-level do we need to go to make this work. Should we try to sync pages from the two non-native sources to our database?
  • 📄 Directory
    • 📄 Submit instance
    • 📄 Manage instance (stretch feature?)
    • List instances
      • We should list all instances and their verification status (i.e., we should even list failing instances)
      • List should be filterable by:
        • accepted language
        • topic
  • 📄 Support
    • Landing page to docs, discourse community, and priority support portal
    • 📄 Support contact form for bugs and feature requests
      • "Warning: Do not submit news tips here! This is not for leaks."
      • FileField for GPG key: "If you'd like to use encryption, you may use this GPG key for securedrop [at] freedom [dot] press. (fingerprint: 734F 6E70 7434 ECA6 C007 E1AE 82BD 6C96 16DA BB79)"
  • 📄 Contribute
    • Information about how to contribute to SecureDrop. Feeds out to: contribution docs, github, development mailing list
  • 📄 Contact
    • Contact form
    • Some note about this form being for general inquiries and not support—link to support form.
    • "Warning: Do not submit news tips here! This is not for leaks."
    • FileField for GPG key: "If you'd like to use encryption, you may use this GPG key for securedrop [at] freedom [dot] press. (fingerprint: 734F 6E70 7434 ECA6 C007 E1AE 82BD 6C96 16DA BB79)"
Clone this wiki locally