Text edits to "Overview" pg & HP button link

[ninavizz]

Problem

The path for a user to quickly and easily learn how to get SecureDrop for their organization, is too jumbled on today's site. Likewise, in the section that exists to inform users how to get SD, all text is written for a technical user to parse; and, a user whose cognitive functions have not been trained by consumer websites. A few text edits and a page anchor feel like quick/easy fixes towards improved usability and reduced stoking of impostor syndrome. Priority Support shd also be upsold, here, too.

Solution

1. The primary CTA button on the homepage has too many words. It should be reduced, simply, to Get SecureDrop

2. When clicking the primary CTA button from the SD homepage, the user is taken to a page with all above-fold content speaking to a product overview; not about how to actually get the product. Muio confusing. Instead, it is recommended that an HTML page-anchor be added so that the lower-half of the page loads as shown in the below mockup (yep, the H1 should display a comfortable reading distance below the top of the browser page; the anchor should not be a part of the actual H1, rather at the top of the grey hexagons background).

3. The h1 for the page content the homepage's CTA directs the user to, should "complete the thought" that the CTA button begins.

4. Content should be inclusive to non-technical and technical users alike. I'm not installing SecureDrop! Seeing that H1 would stop many users. eg: technical ppl love documentation to be "comprehensive," everyone else just wants their end goal to be plausible or easy to achieve. Pls see annotations in the below mockup.

5. Unrelated to all of the above—pls insert the word "advocacy" before "news" in describing the types of orgs SD can serve, for the page's top-of-page H1. Because the author if this Issue is trying to get an advocacy org to adopt SD, and the existing language and ongoing references to "journalists" vs "tip-checkers" (or similar such language) is confusing.

hp-btn: Get SecureDrop

h1: Get SecureDrop Today

h2: Where to Begin?
body: Technical support staff from Freedom of The Press Foundation are available to help guide your organization through any of the steps involved in deciding if SecureDrop is right for your needs, through setting it up and going live to accept tips. <a>Contact</a> us with any questions you may have, or to see if your organization might qualify for pro-bono support. <a>Priority Support</a> is available for organizations with available funding, and helps us keep the lights on.

H2: Self Install
body: Complete <a>technical documentation</a> is available to guide hardware purchases and instance setup. Required technical skills to maintain and use SecureDrop are also covered in that documentation. Initial setup and installation  can be complicated, but <a>the SecureDrop team can help</a>. 

H2: Setup & Operation FAQ
body: If you cannot find an answer to your questions in our technical FAQ, please contact us. We strive to respond to inquiries within 2-3 business days, but typically respond on the same-day, US Eastern Time```

[eloquence]

Thanks @ninavizz, these are straightforward language changes that require no code update as far as I can tell. Let's track as content issue, will discuss with @rocodes when she's back.

[ninavizz]

Adding this, as I've edited to add key on SVS.

[ninavizz]

/cc @huertanix @martinshelton if there might be interest adding this to the Holidaze Docs Sprint.

[huertanix]

The Securedrop.org website is outside the scope of the 2021 doc sprint. A high-level graphic and updated copy for a less technical decision-maker audience seems like a good idea to me though.