Landing Page - Content - Header

[westonmcwhorter]

Background

Our landing page aims to be simple and informative. It's really less about marketing a particular product than it is about informing visitors what we're up to, how they can get involved and how they can get the app themselves.

That being said, it should still look nice and pro.

Scenario: Landing Page Header

Given I am a visitor to the Nightingale For Health landing page,

• [ ] When I view the header area,
• [ ] Then I see the following:
  • [ ] Project logo (such that it is),
  • [ ] Jump links to:
  • [ ] Mission (#29)
  • [ ] Objectives (#30)
  • [ ] Get Involved (#31)
  • [ ] Partners (#32)
  • [ ] A nicely designed visual element to pique interest

[westonmcwhorter]

@westonmcwhorter is going to provide some visual design direction for this deliverable. @alinelea is going to be heading up content. @vegasgeek is our build master!

[westonmcwhorter]

@vegasgeek, here's an idea for a featured homepage image. Photo by Clayton Cardinalli on Unsplash.

[alinelea]

One quick takeaway from the last community leader interview I was just on, we will need to have Spanish and even Vietnamese website versions in order to reach those communities and community leaders. Not sure we have time to get a translated site up by Friday, but perhaps a sentence or two in Spanish would prove our inclusivity of this project.

[iamjoshfrank]

Quick response: if it seems achievable, set up WP to support internationalization (i18n) so that localization (l10n) can occur down the road.

Having an i18n framework in place really opens up a world (pun intended) of opportunity for non-Revelry contributors that aren't software engineers, designers, or product people; but instead are translators and others within the multilingual community.

Definitions of internationalization (i18n) and localization (i10n) via W3C: https://www.w3.org/International/questions/qa-i18n

@vegasgeek and @westonmcwhorter - leaving it up to the two of you re: capturing ^^ in an Issue for prioritization; or making the call and punting on it for now (knowing that all good ideas resurface eventually).

[westonmcwhorter]

@alinelea and @iamjoshfrank, I haven't even heard the whole story, but I would agree 100% that these populations are likely in the "super vulnerable" category, and as such, deserve specific consideration.

@vegasgeek, I think this is a nice feature out the box. And while we may not be able to have the site fully translated by then, there IS always Google Translate, right?

[jwietelmann]

IMO unless it's practically a 1-click install, just ship English and then go back and refactor it into an i18n thing if there's time.

[bmccrossen]

@westonmcwhorter wanna veto that home page photo. Only 1 woman and everyone is white. I strongly encourage we consider the communities that Covid is impacting the most. It's the right thing to do.

[westonmcwhorter]

@westonmcwhorter wanna veto that home page photo. Only 1 woman and everyone is white. I strongly encourage we consider the communities that Covid is impacting the most. It's the right thing to do.

@bmccrossen, 100% understand. Was a quick search to stand as a placeholder, really. But heard.

[jeremybrady]

Posting high level design direction w/ minor edits from slack thread here for visibility.

Start with Why ahead of making design decisions 

Build for the audience: Trusted community leaders and or business owners (example here) within underserved/at risk communities and low income areas. 

Build what matters: How do I serve my community and or reopen safely?

• Accessibility 
  • We’re asking and this might change “How do we enable them to serve a community, their community w/ at risk health issues” which, at the moment, means creating a design that meets accessibility standards, including color standards.
  • Example; Asking someone at risk with diabetes who might have eye sight issues and a respiratory condition to report on their status over the phone should/will directly influence your design decisions.  Design Direction 
• Clean, simple, and accessible (both in terms of accessibility standards and available devices)
• Visual Design Examples include; 1, 2

CC @westonmcwhorter @bmccrossen @CheetoMao for visibility.

[iamjoshfrank]

@jwietelmann - exactly!!

"if it seems achievable" "capturing ^^ in an Issue for prioritization; or making the call and punting on it for now"

stepping away from this topic now...

[westonmcwhorter]

@vegasgeek, I think this is a little better. https://unsplash.com/@belchev?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText

[westonmcwhorter]

Incoming. Working on image selection as well.

[westonmcwhorter]

Screenshot. PSD uploaded to the GDrive. If we like this image, it may cost us a little jack from Getty.

[iamjoshfrank]

@westonmcwhorter - I like it. Go get the approval you need for budget.

[westonmcwhorter]

Pulling thru to QA/UAT.

[jeremybrady]

Hi @westonmcwhorter and @iamjoshfrank @bmccrossen

Can we please consider an image that might be reflective of what the audience might be feeling health wise, as in this case, and or a non-image based approach like this), or this, or this.

[iamjoshfrank]

@jeremybrady - You make good points. I have a few responses:

1. I've said again and again in multiple places that I think the audience for this Nightingale site is not the large cross-section of potential end users of whatever apps / sites / resources we create. Instead, the audience is potential contributors as well as partners and potential sponsors; and, to a lesser extent, the general public that is paying attention. Any app-specific or site-specific or resource-specific assets will need their own branding efforts and their own entities. I've yet to be told I'm wrong about that audience and what the purpose of the Nightingale site should be. I think the examples you gave and the reason for giving them are all completely valid - I'm just not sure we're talking about the same audience?
2. Even so, I still agree the current image at https://nightingale.revelry.co might be too bright, cheerful, etc. I do think we want to convey a positive, hope-filled theme: "we can have a significant impact on the world with Project Nightingale's various endeavors" -- because, again we're talking to folks we hope are collaborators and co-conspirators in our efforts to make positive change. But I concede this image might be over-the-top joy-filled.
3. Ultimately, @westonmcwhorter has been leading the charge here and has had reviews with several folks along the way. I leave it to Wes to follow up on this Issue and line up a replacement - or, make a significant case for leaving it as-is.

[georgiapetagna]

@westonmcwhorter testing on production as per the readme. i think the AC needs updating? as per @iamjoshfrank comment here, we are not soliciting app downloads at this time.

also the jump link to Choose Language is currently missing. everything else in the AC checks out. i would kick this back to implement, but i'm unable to utilize labels on any tickets and i can't start/finish tickets on kanban 🤔

[vegasgeek]

@georgiapetagna Because the site wasn't live (until yesterday), there was no need to have a production/staging setup. Now that we've launched the site, I'll pull a copy of production over to that staging URL and the two will match shortly.

The "choose language" options have been pushed off for future implementation.

[georgiapetagna]

hey @vegasgeek to confirm, going forward, i should test/QA on staging. is that correct? also, what's the URL for staging? what's linked in the README is directing me to this http://nightingalestg.wpengine.com/.

[georgiapetagna]

updated the AC to remove the requirement for jump links to Download App and Choose Language per the feedback above. this passes QA.