TYPEMATCHSEO
Launch

TYPEMATCH.

V2.1

Browse Directory
700
400
PAIRING ID: OLD-RUB // ETHOS: SERIF + SANS-SERIF

Balancing Old Standard TT with Rubik

Build a contrast-first system where Old Standard TT leads and Rubik keeps long-form content legible.

Display Face

Old Standard TT

Weight: 700

Body Face

Rubik

Weight: 400

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Old Standard TT brings classic, russian, academic energy to hero units, pricing sections, and campaign headlines. Rubik absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its stout, rounded, compact 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

Balancing Old Standard TT with Rubik

Build a contrast-first system where Old Standard TT leads and Rubik keeps long-form content legible.

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Old Standard TT brings classic, russian, academic energy to hero units, pricing sections, and campaign headlines. Rubik absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its stout, rounded, compact 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.

Old Standard TT thrives as a headline face thanks to its classic, russian, academic qualities. Use weights 400–600 for crisp editorial lockups.
Rubik excels in paragraphs and UI thanks to its stout, rounded, compact traits. Keep it between weights 400–600 for optimal readability.
Hierarchy guidance: run a 1:1.4 modular scale and reserve Old Standard TT for H1–H3 while Rubik powers captions, body copy, and data tables.

Best-Fit Use Cases

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

Accessibility Notes

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

CSS Implementation Cheatsheet

:root {
  --tm-header-family: 'Old Standard TT', serif;
  --tm-body-family: 'Rubik', sans-serif;
  --tm-header-weight: 400;
  --tm-body-weight: 400;
  --tm-header-tracking: -0.01em;
  --tm-body-tracking: 0em;
}
Heading scale: clamp(2.75rem, 4.5vw, 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 Old Standard TT at 400 for momentum, while forms, tables, and footnotes stay on Rubik with 400 weight for predictable kerning.

FAQs

Why does Old Standard TT make sense as the lead font?

Old Standard TT owns the emotional register of this system. Its classic, russian, academic profile helps anchor campaign creative, meaning marketing and product teams can reuse the same voice without reinventing the scale.

Where should Rubik show up?

Rubik is the workhorse. Keep it in paragraphs, long-form editorial, knowledge bases, or anywhere legibility is non-negotiable. Its stout, rounded, compact 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.