Closed lukad03 closed 6 years ago
@s2t2 I'm likely going to continue working on this tomorrow morning, so feel free to drop in feedback whenever you get the chance.
@lukad03 Oh ok, just seeing this now. I will pull this down and take a look later tonight.
Header is looking good. Love seeing the blank page. Its inviting us to develop it :-)
Here's how you know!
When testing responsivity to browser width resizing, I noticed some potential areas for further refinement: namely, the visibility of the site title and the flag 🇺🇸
I notice the nav background color (#112E51
) is a USWDS color as well as a Census color. Whereas the menu button background color (#0071bc
) is a USWDS color but not a Census color (the corresponding Census color would be #205493
). So the color choices so far reflect a USWDS identity. Then I notice Roboto
font with Helvetica
and sans-serif fall-backs. The Roboto
font reflects a Census identity. So I'm noticing an identity conflict within the site.
To retain a strong site identity, if we want to keep the Roboto
font, we should adopt a more Census-specific scope and title and color scheme. Otherwise, we should keep the USWDS colors and switch the fonts to USWDS fonts (Merriweather
& Source Sans Pro
).
Given the site's more general title ("Data Design Standards") and scope as I understand it (providing guidance for all agencies), perhaps adopting a more general USWDS identity is the preferred approach.
In that case we could still provide Census-specific branding guidance on one of several agency-specific pages. But that begs the question, is it the role of the Data Design Standards project to house and keep updated the branding guidance for all federal agencies? That might be a more applicable role for the agencies themselves, or maybe even USWDS, but probably not for Data Design Standards.
Executive Summary Final Recommendations:
@s2t2 Need to merge this in but we can review this post-meeting
Setting up the styles and foundational elements before building the prototype.