A clear editorial typography hierarchy helps readers understand what matters first, move comfortably through an article, and recognize recurring content patterns. This reusable checklist gives you a practical system for setting headline levels, decks, captions, metadata, body copy, spacing, line length, and responsive behavior across articles, magazines, newsletters, and reports.
Overview
Editorial hierarchy is the visual order created by type size, weight, spacing, alignment, color, and placement. It tells readers whether a line is a title, introduction, section label, supporting detail, or main passage before they read every word.
A reliable system is more useful than a collection of individually attractive text styles. Start with a small set of named levels and define how each one behaves. A typical article may need only the following:
- Display headline: The primary title of the article or feature.
- Deck or standfirst: A short summary that establishes context beneath the headline.
- Section heading: A major division within the article.
- Subheading: A supporting division used when a section needs more structure.
- Body text: The main reading style, usually optimized for sustained reading.
- Pull quote or callout: An optional emphasis style for selected content.
- Caption: Explanatory text attached to an image, chart, or illustration.
- Metadata: Author, date, category, reading time, labels, and similar supporting information.
Record the system in a style guide or design file rather than relying on memory. For each level, specify its purpose, typeface, weight, size, line height, maximum width, spacing before and after, and responsive behavior. If you are choosing typefaces at the same time, test them with real headlines and paragraphs using a font specimen and type test sheet.
A practical starting scale
The following values are a starting point, not a rule. Adjust them to the typeface, format, language, and reading distance.
| Element | Suggested desktop size | Suggested line height | Primary job |
|---|---|---|---|
| Display headline | 40–64 px | 0.95–1.1 | Establish the article’s strongest entry point |
| Deck | 20–28 px | 1.25–1.45 | Summarize or frame the story |
| Section heading | 26–36 px | 1.1–1.25 | Mark a major change in topic |
| Subheading | 19–24 px | 1.2–1.35 | Break a long section into readable units |
| Body text | 16–20 px | 1.45–1.7 | Support comfortable continuous reading |
| Caption and metadata | 12–15 px | 1.3–1.5 | Supply context without competing with the article |
Use proportional relationships rather than copying these values mechanically. A narrow, high-contrast display face may need less size than a wide, low-contrast one. Likewise, a compact serif intended for text may appear smaller than a generous sans serif at the same numeric size. Compare actual samples before finalizing the scale.
Checklist by scenario
For a web article
- Give the headline one unmistakable visual priority above the deck and metadata.
- Keep the reading column comfortably narrow rather than allowing body text to stretch across the full viewport.
- Use section headings to create meaningful navigation points, not to decorate every few paragraphs.
- Define a clear spacing rhythm: larger space before a heading, smaller space between a heading and its first paragraph, and consistent paragraph spacing.
- Test long titles, short titles, links, lists, block quotes, and image captions in the same template.
- Check the hierarchy at narrow widths, where a large headline may wrap to several lines.
For a magazine or print feature
- Set the headline in relation to the page grid, image area, folio, and surrounding white space.
- Use the deck to establish the reading route when the page has multiple entry points.
- Keep captions visually attached to their images through proximity, alignment, or a shared marker.
- Check line endings, widows, orphans, hyphenation, and paragraph breaks at final size.
- Confirm that pull quotes add emphasis without repeating the page’s only important information.
For a newsletter
- Make the subject or issue title distinct from article headlines inside the message.
- Use fewer levels than a magazine spread. Too many competing styles make a compact email feel fragmented.
- Keep body copy and links legible on small screens, with sufficient contrast and comfortable spacing.
- Preview the longest headline and the smallest metadata line in the actual sending environment.
- Use a repeatable combination of label, headline, deck, and call to action so readers learn the pattern.
For a report or data-led publication
- Separate narrative headings from chart titles, axis labels, notes, and source lines.
- Use typography to distinguish evidence, interpretation, and navigation without relying on color alone.
- Give tables and charts enough surrounding space to remain readable when the page is exported or printed.
- Test numerals, abbreviations, dates, and multilingual text in the selected font.
What to double-check
Type pairing: If you combine a display face with a text face, compare their proportions, x-heights, stroke contrast, and overall voice. A pairing should clarify roles, not create two unrelated personalities. For broader brand applications, the brand typography system template can help connect editorial styles with logo, heading, and body use.
Line length: The ideal measure depends on the typeface and format, but extremely long lines make it harder to return to the next line, while extremely short lines create excessive breaks. Adjust the text column, font size, and tracking together rather than solving every problem with one control.
Contrast and emphasis: Weight, size, spacing, and position should do most of the hierarchical work. Avoid making every label bold, colored, uppercase, or underlined. When everything is emphasized, nothing is prioritized.
Accessibility: Check text contrast, zoom behavior, focus states, and heading structure in the final implementation. Visual size is not the same as semantic structure: a large line should still use the appropriate heading level in HTML. Do not communicate meaning through color alone.
Font coverage and licensing: Confirm that the typeface includes the characters, punctuation, symbols, and language support your publication needs. Verify the license before using a font in a commercial, client, embedded, or distributed project. See the commercial font licensing checklist for a practical review workflow.
Real content: Test the system with the longest likely headline, a short headline, a multi-paragraph section, a caption, a numbered list, and a quote. Placeholder text hides wrapping and spacing problems.
Common mistakes
- Choosing sizes before choosing roles: A scale is easier to evaluate when each level has a defined editorial purpose.
- Using too many typefaces: More families rarely create more hierarchy. A restrained pairing with several weights or styles is often easier to maintain.
- Making the deck look like body text: If the summary has no visible separation from the article, readers may miss its framing function.
- Ignoring mobile wrapping: A desktop headline can look balanced while becoming awkward, oversized, or confusing on a narrow screen.
- Relying on spacing alone: Large gaps cannot compensate for weak contrast between heading levels.
- Defining only visual styles: Include semantic heading order, reusable component names, and implementation notes so the system survives handoffs.
- Skipping font verification: A typeface that looks right in a short specimen may fail with real punctuation, numerals, accents, or long-form paragraphs. Use a structured font evaluation worksheet before committing.
When to revisit
Review the hierarchy before a seasonal planning cycle, publication redesign, new content format, or major change to your publishing platform. It is also worth revisiting when editors report inconsistent layouts, when new languages are added, or when a template begins carrying content it was not designed to support.
Use this short audit:
- Collect three recent pieces: one typical, one unusually long, and one unusually short.
- Compare their headlines, decks, body columns, captions, and metadata side by side.
- Mark styles that appear only once or that serve the same purpose under different names.
- Retest the typefaces with required languages, symbols, numerals, and links.
- Preview desktop, tablet, mobile, print, and exported versions where relevant.
- Update the style guide, design components, CSS tokens, and editorial examples together.
Typography systems should be stable enough to create recognition but flexible enough to accommodate real content. Keep the core levels small, document their intent, and revisit the details whenever the publication, tools, or audience changes. For long-form reading decisions, compare the results with a dedicated long-form typography guide, then test the final hierarchy in the actual format readers will use.