GitHub guidelines - type pairing mistakes

GitHub guidelines - type pairing mistakes, minimal, swiss, light

Preview image. Unlock full-res

Unsuccessful type examples page contrasting wrong and right treatments for width styles, mono case, ligatures and letter tracking side by side.

Summary

A typography do-and-don't page pairing four common mistakes (other width styles, mono in uppercase multiline, ligatures on, tight tracking) each as a red wrong example beside a green correct one.

Visual description

A left intro ("Unsuccessful examples ... bias toward readability and clear hierarchy") precedes four stacked rows. Each row has a left monospace caption and rationale (OTHER WIDTH STYLES, MONO STYLE, LIGATURES, LETTER TRACKING) and a right pair of bordered samples: the left flagged with a red no-entry symbol, the right with a green check. The samples show a heavy condensed "First Last" vs the standard cut, uppercase mono vs sentence-case, a "Creative" with vs without ligatures, and "Software" at -5px tracking vs at optical size 77. White background, standard header and green rule above.

Key takeaway

Teaching subtle type rules through tight wrong/right pairs of the same word, with the red and green icons doing the verdict so the difference is instantly legible even when the typographic nuance is small.

Reuse notes

A strong template for catching the fine errors (tracking, ligatures, width axes) that style rules often miss. The matched-pair format makes otherwise abstract advice concrete.

From this deck: GitHub guidelines - type pairing mistakes

View deck

More like this