search

TypeNetwork / variable-fonts-info-site

A brochure website to demonstrate the benefits of variable fonts
https://variablefonts.typenetwork.com
Apache License 2.0
36 stars 12 forks source link

New Overview/X pages #50

Closed dberlow closed 5 years ago

dberlow commented 5 years ago

crumbs n heads1 crumbs n heads2 crumbs n heads3 crumbs n heads4

ghost commented 5 years ago

Subheads and new headline weight are in: https://variablefonts.typenetwork.com/topics/overview/variations

ghost commented 5 years ago

How gray you want it image

ghost commented 5 years ago

I believe everything is done for this one, except turning off the Mac notifications.

dberlow commented 5 years ago

Oh, I see that the last subhead: On ‘OVERVIEWExamples’ Is a repeat of the previous one...

And I’d like to settle on less padding between sub heads and the texts below them that they lead into.

On Jan 25, 2019, at 7:20 PM, Chris Lewis notifications@github.com wrote:

I believe everything is done for this one, except turning off the Mac notifications.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

litherland commented 5 years ago

Oh, I see that the last subhead: On ‘OVERVIEWExamples’ Is a repeat of the previous one...

Yes, indeed! How would you like the hed under “Suggestions for using variable fonts” to read? Here’s a possibility:

Better typography through interactions of instances and code

I also wonder how you would feel about simplifying the two preceding subheds to mitigate any repetitiveness between the two. E.g.,

~More than thirty years later,~ SFNT still serves the needs of users and software developers ~After more than thirty years as an extensible font format, the~ SFNT does it again

dberlow commented 5 years ago

Simplifying the two preceding subheds, adding and clarifying somehow with the third sounds like a good idea if you don't mind.

Thanks.

litherland commented 5 years ago

Sure, @dberlow. Added.

dberlow commented 5 years ago

Chris,

The subheads here need to be the same size and weight, or the lower one must be the smaller. I won't specify heads getting larger as we go down a hierarchy.

Thanks,.

screen shot 2019-01-28 at 10 22 59 am
litherland commented 5 years ago

David, I noticed that earlier and fixed it. Not sure how that happened.

ghost commented 5 years ago

I changed an h3 to an h4. I'll fix the styles.

litherland commented 5 years ago

Just to be clear, those two subheads are at the same level and should be the same. If we’re marking up the new subtitles DB has introduced as h2, then we can make the subheads in the article h3s. No h4s here.

ghost commented 5 years ago

Sorry, I had missed the second subhead down below. Certainly they should be the same level. I interpreted @dberlow's comment above as referring to the two levels of the global "SFNT does it again" at the top, vs the internal "Sooner or Later" down below. They are now visually the same, although above is h2 and below is h3.

dberlow commented 5 years ago

I’m hoping that the three subheads can all be the same font, weight, size and indentation, as well as have the same linespacing to the text below each them.

On Jan 28, 2019, at 12:52 PM, Chris Lewis notifications@github.com wrote:

Sorry, I had missed the second subhead down below. Certainly they should be the same level. I interpreted @dberlow's comment above as referring to the two levels of the global "SFNT does it again" at the top, vs the internal "Sooner or Later" down below. They are now visually the same, although above is h2 and below is h3.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

ghost commented 5 years ago

Aha. Will do.

ghost commented 5 years ago

OKAY sorry for that misunderstanding on my part. Now the top subheads are "part of" the article below and not glued to the big headline up at the top.

screenshot 2019-01-28 at 3 15 59 pm screenshot 2019-01-28 at 3 16 10 pm screenshot 2019-01-28 at 3 16 24 pm
dberlow commented 5 years ago

Thanks!

Chris, Can we schedule a 30 minute working hangout to discuss and go over some illustrations I’m finished with?

On Jan 28, 2019, at 6:18 PM, Chris Lewis notifications@github.com wrote:

OKAY sorry for that misunderstanding on my part. Now the top subheads are "part of" the article below and not glued to the big headline up at the top.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

ghost commented 5 years ago

Chris, Can we schedule a 30 minute working hangout to discuss and go over some illustrations I’m finished with?

Yes! Tomorrow morning would work for me, anytime between noon and 2pm EST. Or I can do first first thing when I wake up, about 10am EST if needed. Just me or anybody else?

dberlow commented 5 years ago

Sounds great. I’ll check in with you at 11:30 Eastern. Anyone else who wants to can listen in for sure.

On Jan 28, 2019, at 6:41 PM, Chris Lewis notifications@github.com wrote:

Chris, Can we schedule a 30 minute working hangout to discuss and go over some illustrations I’m finished with?

Yes! Tomorrow morning would work for me, anytime between noon and 2pm EST. Or I can do first first thing when I wake up, about 10am EST if needed. Just me or anybody else?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

ghost commented 5 years ago

I'll be out from 11 to noon taking the kids to preschool.