Putting It Together

Typography Fundamentals

Course 1 ยท Chapter 8 ยท Putting It Together

In Typography Fundamentals 7 you learned to make type work for readers with different eyes, screens and languages. Now comes the payoff. Seven chapters of vocabulary, measurements and rules only become skill when you apply them to something real, so this final chapter is one long worked example: take a deliberately bad page and fix it, one decision at a time, naming the chapter each fix comes from.

What was run, and what was not
The one Python script in this chapter was run on Windows with Python 3.14.0, using only the standard library; the output shown is exactly what it printed. The CSS snippets were not tested across several browsers, the font names are real system fonts chosen only for illustration, and the numeric thresholds are rules of thumb rather than laws (check them against the guidelines you work to).

The Patient: A Poor Page

Imagine a small bakery's "About Us" page. The owner built it quickly and it shows. Here is its stylesheet, with a comment on each choice. Read it as a doctor reads a chart: how many problems can you spot before the next section tells you?

body { font-family: "Comic Sans MS", "Papyrus", sans-serif; font-size: 12px; /* small */ line-height: 1.1; /* tight */ color: #aaaaaa; /* "subtle" grey */ background: #ffffff; text-align: justify; } .page { width: 1100px; } /* one very wide column */ h1 { font-family: Impact; font-size: 14px; text-transform: uppercase; } h2 { font-family: "Times New Roman"; font-size: 13px; } .note { font-size: 9px; font-style: italic; text-transform: uppercase; }
Before

OUR STORY. We have been baking bread in the same oven since the shop opened, and every loaf is still shaped by hand before sunrise, so that the first customers of the day can take one home while it is still warm.

After

Our story. We have been baking bread in the same oven since the shop opened, and every loaf is still shaped by hand before sunrise, so that the first customers of the day can take one home while it is still warm.

The same paragraph, live text with fixed colours: judge the difference on your own screen.

Diagnosis before treatment
A good redesign starts with a list, not with a font. Count the problems first, rank them by how many readers they affect, and fix them in that order. Changing the typeface before fixing size, spacing and contrast is the classic beginner's mistake, because the typeface is the most visible change and the least important one.

Step-by-Step Treatment

Each step below names the chapter it comes from, so you can see the whole course working as a single toolkit.

StepProblem foundFixFrom
1. Size12px body text, 9px notes1.125rem body, notes no smaller than 0.875remTypography Fundamentals 3 and 7
2. Contrast#aaaaaa on white (about 2.3:1)#333333 on white (about 12.6:1; the script below checks it)Typography Fundamentals 7
3. Leadingline-height 1.1line-height 1.55Typography Fundamentals 3
4. Measure1100px column, about 130 characters per linemax-width: 65ch plus paddingTypography Fundamentals 3 and 7
5. AlignmentJustified text with riverstext-align: leftTypography Fundamentals 7
6. FamiliesFour unrelated familiesOne serif for text, one sans-serif for headings, with fallback stacksTypography Fundamentals 5 and 6
7. HierarchyHeadings nearly the size of the bodyA modular scale with a ratio of 1.25Typography Fundamentals 4
8. EmphasisSmall all-caps italic notesSentence case, upright, a little muted but still above 4.5:1Typography Fundamentals 7
9. DeliveryNo fallback, no language declaredSystem-font stacks, lang="en", charsetTypography Fundamentals 6 and 7

Build the Scale First

Steps 1 to 5 are single-property corrections. Step 7 deserves a moment because it replaces guesswork with arithmetic. With a body size of 1.125rem and a ratio of 1.25, each heading level multiplies the one below it. The sizes in the finished stylesheet below are those multiples, rounded to tidy numbers. The script that follows then runs this chapter's checklist as an audit on the before and after settings.

"""Type audit: score a page's text settings against a simple checklist. py audit.py """ def channel(v): v = v / 255 return v / 12.92 if v <= 0.03928 else ((v + 0.055) / 1.055) ** 2.4 def luminance(hexcol): r, g, b = (int(hexcol[i:i + 2], 16) for i in (1, 3, 5)) return 0.2126 * channel(r) + 0.7152 * channel(g) + 0.0722 * channel(b) def ratio(fg, bg): a, b = sorted((luminance(fg), luminance(bg)), reverse=True) return (a + 0.05) / (b + 0.05) def audit(page): results = [] results.append(("Body size at least 16px", page["body_px"] >= 16)) results.append(("Line height 1.4 to 1.7", 1.4 <= page["line_height"] <= 1.7)) results.append(("Measure 45 to 75 characters", 45 <= page["measure"] <= 75)) results.append(("Body contrast 4.5:1 or more", ratio(page["text"], page["bg"]) >= 4.5)) results.append(("Two families or fewer", len(page["families"]) <= 2)) results.append(("Heading 1.7x body size or more", page["h1_px"] / page["body_px"] >= 1.2 * 1.2 * 1.2)) results.append(("Left-aligned body text", page["align"] == "left")) return results before = {"body_px": 12, "line_height": 1.1, "measure": 130, "text": "#aaaaaa", "bg": "#ffffff", "families": ["Comic Sans", "Papyrus", "Impact", "Arial"], "h1_px": 14, "align": "justify"} after = {"body_px": 18, "line_height": 1.55, "measure": 66, "text": "#333333", "bg": "#ffffff", "families": ["Georgia", "Verdana"], "h1_px": 36, "align": "left"} for label, page in (("BEFORE", before), ("AFTER", after)): res = audit(page) print(f"{label}: {sum(ok for _, ok in res)}/{len(res)} checks passed " f"(contrast {ratio(page['text'], page['bg']):.2f}:1)") for name, ok in res: print(f" [{'x' if ok else ' '}] {name}") print()
BEFORE: 0/7 checks passed (contrast 2.32:1) [ ] Body size at least 16px [ ] Line height 1.4 to 1.7 [ ] Measure 45 to 75 characters [ ] Body contrast 4.5:1 or more [ ] Two families or fewer [ ] Heading 1.7x body size or more [ ] Left-aligned body text AFTER: 7/7 checks passed (contrast 12.63:1) [x] Body size at least 16px [x] Line height 1.4 to 1.7 [x] Measure 45 to 75 characters [x] Body contrast 4.5:1 or more [x] Two families or fewer [x] Heading 1.7x body size or more [x] Left-aligned body text
What this audit cannot tell you
Seven passing checks do not make a beautiful page. The script measures numbers, not taste: it cannot see whether the two chosen families actually suit each other, whether the heading has real personality, or whether the page feels like a bakery. Use it as a safety net under your own eyes, never as a replacement for them. (The first draft of this script labelled the heading check as a "1.2x step", which was wrong, since the code tests three steps of 1.2, about 1.7 times. A label that disagrees with its code is a small bug; reading your own output aloud is a quick way to catch it.)

The Finished Stylesheet

Here are all nine fixes combined. Notice how much shorter the thinking is when the rules are on your side: every value has a reason.

:root { --text: #333333; --muted: #595959; /* 7:1 on white */ --step-0: 1.125rem; /* body */ --step-1: 1.4rem; /* 1.125 x 1.25, rounded */ --step-2: 1.75rem; --step-3: 2.2rem; } body { font-family: Georgia, "Times New Roman", serif; font-size: var(--step-0); line-height: 1.55; color: var(--text); background: #ffffff; } .page { max-width: 65ch; /* a comfortable measure */ margin-inline: auto; padding-inline: 1rem; /* room on phones */ } h1, h2 { font-family: "Trebuchet MS", Verdana, sans-serif; line-height: 1.2; /* big type needs less leading */ margin: 2rem 0 0.5rem; } h1 { font-size: var(--step-3); } h2 { font-size: var(--step-2); } .note { font-size: 0.875rem; color: var(--muted); }
Keep what you were given
The finished version still respects the reader: sizes are in rem, nothing blocks zoom, and the column is capped in ch rather than fixed in pixels. A redesign that looks better but takes control away from the reader has only moved the problem.

The Final Checklist

Here is the whole course on one page, in the order you would work. Keep it beside you the next time you open an empty stylesheet.

Ask yourselfRule of thumb (check for your project)Chapter
Is the text a designed object, not a default?Choose deliberately; read it as a reader, not a designerTypography Fundamentals 1
Does the typeface suit the job?Pick a family type that fits the tone; use weights and italics with purposeTypography Fundamentals 2
Are size, measure and leading set for reading?About 16px or more; 45 to 75 characters; line-height about 1.4 to 1.6Typography Fundamentals 3
Can a reader see the structure at a glance?A scale, a few clear levels, contrast through size, weight, colour and spaceTypography Fundamentals 4
Do the typefaces belong together?Two families at most; contrast or harmony, not a near missTypography Fundamentals 5
Does it arrive and render well on screen?WOFF2, fallback stacks, font-display, subset with careTypography Fundamentals 6
Can everyone read it, in any language?4.5:1 contrast, zoom works, lang and charset declared, coverage testedTypography Fundamentals 7

Course Complete

You started with the parts of a single letter and finished by repairing an entire page. Along the way you learned to name what you see (baseline, x-height, counter), to tell the families apart, to measure and set text, to build a hierarchy, to pair typefaces, to deliver fonts to a screen and to make sure every reader can use the result.

Where to go from here
The best next step is practice on real material: restyle a page you use every day, or set a favourite poem or recipe as carefully as you can. After that, courses on page layout and grids, on colour, or on front-end styling in general would build naturally on what you now know, and a deeper look at type design (drawing letters yourself) is a rewarding direction if you fall in love with the craft. Keep a small notebook of typography you admire, and write down why it works. Your eye will improve faster than you expect.

Hands-On Exercises

The last three exercises are capstones: a written redesign brief, a code task that builds an audit tool, and a CSS task that restyles a page from scratch. Each has a solution file that opens in a new tab.

Exercise 1

Choose a real page you know (a school or club website, a recipe page, a news article) and write a one-page redesign brief for its type. Describe the current state in the words from this course, list at least six problems, and for each give a fix with a number or a named choice. Rank the fixes in the order you would make them and explain why. Finish by naming two things the page already does well that you would keep.

๐Ÿ“„ View solution
Exercise 2

Extend the audit script from this chapter. Add three new checks of your own devising (for example: a maximum number of font weights, a minimum size for small print, a check that the page declares a language). Add a third page called unfinished that passes some checks and fails others, and make the script print a short "fix first" line naming the failed check you consider most important. Run it and show the output.

๐Ÿ“„ View solution
Exercise 3

Write the HTML and CSS for a small one-page article, such as a recipe or a short biography, from a blank file. Use a modular scale built from custom properties, a capped measure in ch, two font stacks with fallbacks, accessible contrast, a caption style, a pull quote and a lang declaration. Add a comment above each rule saying which chapter of this course it comes from.

๐Ÿ“„ View solution

Chapter 8 Quick Reference

  • Diagnose first: list every problem, rank by how many readers it affects, then fix in that order
  • Typeface last: size, contrast, leading, measure and alignment matter more than the font name
  • The poor page: 12px, #aaaaaa, line-height 1.1, about 130 characters per line, justified, four families
  • The fixed page: 1.125rem, #333333 (about 12.6:1), line-height 1.55, 65ch, left-aligned, two families, a 1.25 scale
  • Audits help, eyes decide: numbers catch the obvious failures, not bad taste
  • Respect the reader: rem, zoom, lang, charset and tested font coverage stay in every redesign
Course complete
You have finished Typography Fundamentals. You can now describe type precisely, choose and pair it with reasons, set it for reading on paper and on screen, and check that it works for everyone. Well done.