Closed nataliafitzgerald closed 7 years ago
@nataliafitzgerald the documentation on this looks nice will be really interesting to hear thoughts around some of the details you mentions
@duelj -
I agree with bullet point one and with forklifting content for FJ we have found how the length, formatting, etc. of content can really affect a design concept. Our intro sections are a great example. Our hope was all of them would have a title and a succinct sub-heading description with some instances of a short description paragraph. But in forklifting most content doesn't have a short description to use as a subheading which makes the style seem inconsistent. I think the hero's and intros being a first impression could really benefit from more consistency (as you mentioned) in the content format.
Also, looking forward to hearing some more insight on the UX intention of the CTA differences between the hero styles. The guidance seems like it would be helpful as we refine styles so we can think about specific use cases.
In working on the KBYO landing page with @danny8000 I was able to see the hero graphic standards specified above within the browser. Seeing this at desktop size, the 300px height felt quite tall and the H2 text for the subhead felt large. Have other designers had that experience? @caheberer @stephanieosan @klocraft So, I tried another option for the purpose of experimentation. I'd love to hear what you think @stephanieosan and @huetingj
This is the approach I posted initially. The content fits well in the space but I am worried about how large the subhead text and the box height when viewed on a desktop computer. It looks fine on a laptop.
Headline in H1 (34px), Subhead in H2 (26px) |
---|
Here's an alternate approach trying out H3 for the subhead and reducing the height to 270. This means that the hero takes up less vertical real estate. There's also a little more space for content.
Headline in H1 (34px), Subhead in H3 (22px) |
---|
I had to create layouts at different widths for this project so I took an initial stab at exploring this (I have not tested this out on other use cases).
Headline in H2 (26px), Subhead in H4 (18px) |
---|
Headline in H2 (34px), Subhead in H4 (18px) |
---|
One thing I noticed is that for the hero graphic, the 1290 to 767 range is too broad which comes to play at the landscape tablet size. It is beneficial to break to the 768-321 specs a lot sooner. So, that's another item to discuss (but I know we have a lot in flux or becoming standardized right now with breakpoints so perhaps this is already being addressed).
Headline in H2 (34px), Subhead in H4 (18px) |
---|
I have posted my illustrator as well as full size PNGs here (if there is a better folder, let me know @stephanieosan @huetingj https://drive.google.com/a/cfpb.gov/folderview?id=0B3epifaWXQGRfklvdXAyOEhUS2k3X3k2Z3JhT3VYTjltUW9yd1NBQXdoZFc5aXVkaklRTVk&usp=sharing
Adding @Scotchester
@nataliafitzgerald and I discussed hero dimensions on Wednesday, and the OaH team discussed them today. We want to look at the design in code and tweak there as we write the guidelines. Here are the details.
Couple of questions come to mind:
I ask for couple of reasons, the first we are finding that as we look to a hero acting as an introduction to a page it has to bear the weight of the introduction section that we were using previously. From the content end there is a concern of whether the hero will offer enough real-estate to effectively introduce users to a page. But we have been trying to decide if pages should have both a hero and an intro section since they serve similar purposes with different levels of emphasis.
As I was looking I could not find many examples of websites (including those that we reference for inspiration) having hero heights of below 300px. The trend seems to be moving toward larger, more expansive heroes and relying on the user to be comfortable scrolling.
Energy | DOI | Wellington | Whitehouse | Politico |
---|---|---|---|---|
In V1 after we worked on simplifying out breakpoints we have heading levels drop one level (for h1-h3, h4-6 remain the same) at the 599px width breakpoint. This also happens to be when we change to mobile links assuming at this screen size most devices will likely be touch input based. This pattern worked well for us, we dropped the heading size to allow for better line lengths on smaller screens across the page. I wondered if this was something that had been considered in on the above hero explorations and at what width the heading size actually drops (or is it at 768px)?
Since we have been working to establish web header spacing, I was curious why the H1 & H2 in the hero use 15px rather than the 30px being discussed in the DM? Is this the only place this is expected to happen?
Good thoughts @duelj! Looking at the 15px spacing specifically— @nataliafitzgerald do you have thoughts about this regarding using 15px instead of 30px after an H1 as defined in the design manual?
Here it is with 30px spacing
With 30px spacing, it'd serve us better to change the hero back to 300px to ensure enough space for text.
My take is to have it as 30px so as not to break from the design manual and other H1/H3 paragraphs.
We definitely questioned height, too. I think the homepage should have a large hero. Could see a hero relationship like airbnb has on some of its pages.
Homepage
Second-level page
@nataliafitzgerald and @benguhin, can you please review? thank you!
Hey, @nataliafitzgerald and @benguhin! Any chance you might be able to check this out today? Thanks!
Design manual page version of this here: https://stephanieosan.github.io/design-manual/ui-toolkit/heroes.html
I met with @huetingj this afternoon to go over the FCM. She will sum up what we discussed and add that to this issue. We identified some open questions and made some adjustments. We should be getting close.
We submitted pull requests to the design manual and capital framework with the following designs.
Pull request here: https://github.com/cfpb/design-manual/pull/362
@huetingj @stephanieosan - I'm seeing source files for hero graphics in two places on Drive. Which one is correct (and can we delete the other?).
Google Drive/Brand 2.0/Templates/Web/Hero graphic or Google Drive/Brand 2.0/Templates/Web/Website templates/consumerfinance.gov/New patterns
Hey team - @nataliafitzgerald @huetingj @stephanieosan : I'm starting to work on a new hero for the Tax Insert webpage. We won't have a call to action or link in the hero, so I'm wondering how to use the space. Does this look right to you?
@huetingj What's the latest on how the spacing ultimately got coded up?
cc: @jimmynotjim @virginiacc
@mebates @stephanieosan we ended up vertically centering the text!
I didn't see an answer to @mebates question above about the multiple source files in different locations. I used my best judgement and moved the "Google Drive/Brand 2.0/Templates/Web/Hero graphic" into the "Previous versions" folder within "Google Drive/Brand 2.0/Templates/Web/Website templates/consumerfinance.gov/New patterns".
As far as I can tell the official source file is: https://drive.google.com/a/cfpb.gov/file/d/0B0w0ULKKFAtgUnpZNDY0R1RVRUk/view?usp=sharing. I think it would be safe to delete the previous version at this point but I'll want the green light from @huetingj.
What's the status of getting this into the Design Manual?
Here is the final file: https://drive.google.com/a/cfpb.gov/file/d/0B0w0ULKKFAtgMVZvVzhuQ29BODA/view?usp=sharing (Google Drive/Brand 2.0/Templates/Web/Website templates/consumerfinance.gov/New patterns)
The DM page had been in design-manual master, but I just pulled it to my repo to update the spacing after paragraph headings to be 15px, reflecting the new standards. Here is the page: https://huetingj.github.io/design-manual/ui-toolkit/heroes.html @nataliafitzgerald feel free to give it a glance. If all looks good, I'll submit a pull request today. Just a note that the content structure does not follow any guidelines. When the UX team finalizes the content approach, I'll rework the page using those standards and submit a new pull request. Thanks!
Pull request here: #384
Merged. Any reservations about adding these pages to the navigation at this time?
Thank you! I don't have any reservations.
Scratch that— I'm going to follow up with @jimmynotjim to double check that everything is good to go. Will post again here when ready.
We're using these from Capital Framework in cfgov-refresh, and they seem to be pretty solid. I think we're ok to officially publish them.
Ok, sounds good. Thanks @jimmynotjim!
Overview
The purpose of the Hero graphic is to "provide a brief overview of the purpose for a group of pages and indicate to users that they are in the right place to accomplish their goals." The Hero graphic sits at the top of the content hierarchy, so visual design elements, such as the height of the graphic and type size, must reinforce this position. Graphic standards must be flexible enough to accommodate different types of content yet also provide some limits, particularly in terms of the amount of content. Concise and engaging copy is key to the success of the Hero graphic.
Related issues and documentation
Hero graphic standards and hierarchy: https://github.com/cfpb/design-manual/issues/301 UX pattern discussion: https://docs.google.com/document/d/120S1FyRaIAefcVgODGhnaO99ycigH_-5_4cI5KAfE4A/edit#
Proposed standards for desktop size
Dimensions and measurements
Hero Height: 300 px Content width = 8 columns Illustration width = Up to 4 columns Illustration height = 180 px
For top facing illustrations, the width of the image should extend no wider than 4 columns. The height should be set to 180 pixels to leave 60 pixels of padding on top and bottom.
For front facing illustrations, the width of the should be limited to 4 columns maximum. The shelf line at the base of the illustration should extend 4 columns. The height should be set to 180 pixels to leave 60 pixels of padding on top and bottom.
Text content should be vertically centered within the space and the text box should extend 8 columns in width. The padding above and below the text content should be no less than 60 pixels top and bottom.
Typographical specifications
Header: 34 pixels (H1) Subhead: 26 pixels (H2) Link: 22 pixels (H3 Medium) Eyebrow: 18 pixels (H4)
The following hero graphics have been tested applying these standards:
Remaining items to tackle as part of this issue:
@stephanieosan @Dnpizarro @huetingj @kurzn @klocraft @duelj @ajbush