TYPEMATCHSEO
Launch

TYPEMATCH.

V2.1

Browse Directory
700
400
PAIRING ID: ALE-POL // ETHOS: SERIF + SERIF

Systematizing Aleo & Poly

Build a mono-category system where Aleo leads and Poly keeps long-form content legible.

Display Face

Aleo

Weight: 700

Body Face

Poly

Weight: 400

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Aleo brings slab, semi-rounded, clean energy to hero units, pricing sections, and campaign headlines. Poly absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its medium-contrast, agile, web texture and dependable rhythm. Together they create a typography stack that scales from high-impact landing pages to dense documentation without retooling your CSS tokens.

Typographic Hierarchy & Scale

H1The Quick Fox
H2The Quick Fox
H3The Quick Fox
PThe quick brown fox jumps over...
Dark Context
Aa

High contrast negative space.

Accent
Gg

Legibility on high-chroma.

Pairing Strategy

Systematizing Aleo & Poly

Build a mono-category system where Aleo leads and Poly keeps long-form content legible.

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Aleo brings slab, semi-rounded, clean energy to hero units, pricing sections, and campaign headlines. Poly absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its medium-contrast, agile, web texture and dependable rhythm. Together they create a typography stack that scales from high-impact landing pages to dense documentation without retooling your CSS tokens.

Aleo thrives as a headline face thanks to its slab, semi-rounded, clean qualities. Use weights 700–900 for crisp editorial lockups.
Poly excels in paragraphs and UI thanks to its medium-contrast, agile, web traits. Keep it between weights 400–600 for optimal readability.
Hierarchy guidance: run a 1:1.2 modular scale and reserve Aleo for H1–H3 while Poly powers captions, body copy, and data tables.

Best-Fit Use Cases

  • High-growth SaaS landing pages that require slab hero statements with trustworthy product copy.
  • Editorial magazines and thought-leadership hubs where Aleo can dramatize pull quotes while Poly keeps 1,500-word essays skimmable.
  • Conversion funnels or onboarding flows that need Poly's medium-contrast voice to balance Aleo's attention-grabbing display.

Accessibility Notes

Maintain a minimum 4.5:1 contrast ratio for Poly body copy and loosen letter-spacing to 0.01em for uppercase Aleo moments. Pairing different categories demands disciplined color pairing—test both light and dark themes to ensure Poly does not bloom at small sizes.

CSS Implementation Cheatsheet

:root {
  --tm-header-family: 'Aleo', serif;
  --tm-body-family: 'Poly', serif;
  --tm-header-weight: 700;
  --tm-body-weight: 400;
  --tm-header-tracking: -0.01em;
  --tm-body-tracking: -0.005em;
}
Heading scale: clamp(2.75rem, 3.6vw, 5.25rem) for H1, clamp(1.5rem, 2.8vw, 3rem) for H2, and keep paragraph size at 1rem–1.125rem with 1.6 line-height.
Component guidance: Buttons inherit Aleo at 700 for momentum, while forms, tables, and footnotes stay on Poly with 400 weight for predictable kerning.

FAQs

Why does Aleo make sense as the lead font?

Aleo owns the emotional register of this system. Its slab, semi-rounded, clean profile helps anchor campaign creative, meaning marketing and product teams can reuse the same voice without reinventing the scale.

Where should Poly show up?

Poly is the workhorse. Keep it in paragraphs, long-form editorial, knowledge bases, or anywhere legibility is non-negotiable. Its medium-contrast, agile, web qualities reduce fatigue on dense layouts.

Does this pairing support complex localization?

Yes—both families are available on Google Fonts with generous glyph coverage. Test cyrillic/latin accents early, but most Latin-based locales and UI patterns are fully supported.