The Elements of Typographic Style Applied to the Web
webtypography.net
webtypography.net
Namely, much of the book is about making choices that depend on the exact placement of individual characters on the screen. Like the entire section about hyphenation. This doesn't make sense if the glyphs show up slightly different on different screens. Like Mac/PC/Android might render the same glyph for a font just a pixel different (maybe even just due to the way it rounds a number), bumping a glyph on to the next line. It's really hard to control the exact placement of each glyph, and not worth fretting about for the web. So I think the principles in the book that are focused on exact placement of individual glyphs (characters) is incompatible with the more general principles of responsive layouts or using a native font stack.
Some of the advice is automatically taken care of by defaults on the browser/OS, like kerning or letterspacing are often not that relevant to the web designer. It might be relevant to the people working on rendering at the browser level. And the other advice is stylistic and depends on the content (like indentation and casing).
I think the most practical advice from this book is fairly straightforward: choose some appropriate sizings for various headers and body text, check that you have about 70 characters per line, and choose a comfortable line-height for the body text.
It kinda looks broken on a big screen and it took me a while to figure out what to do next. Call to actions were not clear.
Keep things simple, the web is fluid and make sure your text is legible and ensure good contrast. Also think about load performance and ideally stick to fonts that are generally already installed on devices by default.
Or follow this handy guide:
https://betterwebtype.com/articles/2021/06/07/all-you-need-i...
https://betterwebtype.com/ (free web typography course)
So don’t justify text on the web."
I've been waiting for this to be fixed since 1997. I suspect it is a very difficult problem to get right. My Kindle accidentally hyphenates things like "Walde-r" and "Lannister-s" (yes, I'm reading GoT again).
https://www.gatsbyjs.com/plugins/gatsby-remark-hypher/
and
https://github.com/siawyoung/remark-hypher
(An example of how it looks like: https://siawyoung.com)
It's from 2019, but nothing much has changed since. My biggest gripe is that browsers should prevent hyphenation when a word starts with an uppercase letter, which doesn’t seem too hard?
The only bulletproof (but more complicated) solution is to process text beforehand and insert soft hyphens (­) where appropriate.
[1] https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens
On some machines, maximum contrast is exhausting; on others, reduced contrast is near-invisible. The “exhausting” machines can be configured to reduce contrast, but the “invisible” machines cannot trivially be configured to increase contrast.
To give you an example of the sort of high contrast user interfaces I like, turn on he dark High Contrast theme in VS Code.
No idea what they do different, but while I don’t prefer it, it looks a lot less problematic than the website. There is no glare effect where the letters bleed into the black.
I use to go through hundreds of typefaces like going through hundreds of photos on Tinder and think ‘they all suck’ but then I started adjusting the letter spacing and now I ‘love the one I’m with’.
I recently developed an unofficial corporate identity for my workplace (improving signage) that uses serif fonts. All the other signs use sans-serif which is half because it fits the modernist building and half because people don’t know how to do the manual kerning it takes to make serif fonts pop.
That said I have felt no need to kern for the web and have no desire since it will certainly go bad if the user isn’t seeing the typeface I want them to see.
This site - and other similar "web typography" sites - seems to immediately fall foul of that by using serif fonts. In my opinion this makes them less comfortable to read.
That fact doesn’t stop some people from repeating the old mantra.
Sans serif font faces, on the other hand, manage to be readable at smaller sizes, and even more so on modern anti-aliased displays, where they support a greater number of words per line.
Lest it seem that I am biased, serif fonts continue to be the best option for so-called "display" purposes (i.e., short line length such as headlines), as well as for subtractive, engravure-based applications such as stone, metal or wood; in these applications, sans serif fonts fail to provide a reasonable sight line.
And _nothing_ looks tappable/clickable either. A prime example why the web is an interactive medium, different from print.
typography is generally involved with any text, many of these are standards that have existed for hundreds of years and still exist on computers
Jeffrey Zeldman said (in 2015):
“Mobile is today’s first screen. So design responsively, focusing on content and structure first. Websites and apps alike should remove distractions and let people interact as directly as possible with content. 90 percent of design is typography. And the other 90 percent is whitespace.”
(Zeldman knows his shit. He was one of the most influential designers and standards-setters for the early web, e.g., founder of the Web Standards Project, which was instrumental in helping us escape the minefield of browser-specific customizations in the late 90s).
Most of the principles of good typography apply anywhere that type can be used, from books to billboards to websites to mobile games. Typography as a discipline is thousands of years old, and based in the fundamentals of human perception. We know how humans read. Typography is the practically application of that knowledge.
There was a brief period where coolness and aesthetic appeal on the web trumped good typography principles (e.g., again, the Arctic Adventure site). Most of that has settled down, though, and most sites have reverted to simple and common standards.