Skip to content

Information Architecture

Jump to bottom
Harris L edited this page Aug 21, 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
    • Filterable by blog post category (this could also work by having 📄 Category pages as children of the News page)
    • Should have an RSS feed that is also filterable by post category (use case: I want to subscribe to release announcements)
    • ❓ Is it working for FPF to have all SecureDrop blog posts in a single blog? Should we leave that as is (introducing the ability to filter by category, as listed below) or would be useful to, for example, separate release announcements from other blog posts? My current inclination is to leave it as is (which is basically how I've seen other software projects, such as Django, do it) but I'd be curious to hear from FPF staff. Maybe have a separation of featured posts that display by default, like the GitHub blog where you have to explicitly choose "All Posts" to see the blog comprehensively.
    • 📄 Blog posts
      • is in one of these 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 (❓ do we want to allow users to update their instance details?)
    • List instances
      • ❓ Should we list all instances and their verification status? (e.g., if an instance fails verification, should we list it anyway with a warning?)
      • ❓ Should instances be filterable? By country or other parameters?
  • 📄 Support
    • Landing page to docs, discourse community, and ❓ "live" support
  • 📄 Contribute
    • Information about how to contribute to SecureDrop. Feeds out to contribution docs and github
  • 📄 Contact
    • Contact form
    • ❓ Should there be different contact forms/avenues for support vs. technical vs. "sales" queries?
Clone this wiki locally