Closed
Bug 1378428
Opened 7 years ago
Closed 6 years ago
[beta redesign] Titles and H2s are too big
Categories
(developer.mozilla.org Graveyard :: Design, defect)
developer.mozilla.org Graveyard
Design
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wbamberg, Unassigned)
References
Details
(Keywords: in-triage)
Attachments
(2 files)
This is pretty opinionated, and I've given it time to get used to it, but IMO the titles and H2 headings in article pages are too big. Especially the title takes up a lot of space and really dominates the page. For me personally, the main text body is also a little big.
Comment 1•7 years ago
|
||
Thanks Will. I go back and fourth on this myself but I think, over all, the web is trending to bigger fonts right now. We will make typography changes if we hear a lot of similar feedback.
Comment 2•7 years ago
|
||
Good news, we have the okay from brand to experiment with a different size. Not in time for the redesign launch but hopefully in the next few weeks.
Comment 3•7 years ago
|
||
Hey Will, I wanted to check in with you. Do you still feel this way after 3 weeks?
Flags: needinfo?(wbamberg)
Reporter | ||
Comment 4•7 years ago
|
||
Yes, I do. I don't think it looks bad exactly, but I think for technical documentation (rather than, say, a new site or a blog) smaller headings seem better: more balanced, calmer, and with more space for content. I've attached a couple of screenshots of the current design and one with the title reduced by 1em: I think the smaller one looks better. For a dramatic comparison, see http://cssreference.io/property/background-color/, where the title is hardly bigger than the body text.
Flags: needinfo?(wbamberg)
Reporter | ||
Comment 5•7 years ago
|
||
Reporter | ||
Comment 6•7 years ago
|
||
Reporter | ||
Comment 7•6 years ago
|
||
The issue raised in this bug (giant title and H2 font) has been fixed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•