--- id: css-font-pairings title: "CSS Font Pairings" category: "Frontend" status: "draft" verification_status: "conceptual" canonical_id: "" aliases: ["font pairings", "CSS font pairings", "font combinations", "heading body font", "typography pairing"] duplicate_of: "" source_trust_level: "B" confidence_score: 0.86 created_at: 2026-06-23 updated_at: 2026-06-23 review_reason: "" merge_history: [] tags: ["css", "web", "frontend", "w3schools", "fonts", "typography"] raw_sources: ["https://www.w3schools.com/css/css_font_pairings.asp"] applied_in: [] github_commit: "" --- # [[CSS Font Pairings]] ## 🎯 ν•œ 쀄 톡찰 (One-line insight) Great font pairings follow a few rules β€” fonts should complement each other, can come from a superfamily, should use contrast (e.g. serif with sans-serif), and one font should dominate the hierarchy β€” illustrated with both web-safe and Google Font combinations. [S1] ## 🧠 핡심 κ°œλ… (Core concepts) - **Complement** β€” a great font combination should harmonize, without being too similar or too different. [S1] - **Font superfamilies** β€” use fonts within the same family designed to work together (e.g. Lucida superfamily variations). [S1] - **Contrast** β€” two fonts that are too similar will often conflict; contrasts, done the right way, bring out the best in each font. Serif-with-sans-serif combinations exemplify this. [S1] - **Hierarchy** β€” one font should be "the boss"; vary size, weight, and color to establish visual hierarchy. [S1] ## 🧩 μΆ”μΆœλœ νŒ¨ν„΄ (Extracted patterns) - **Heading vs body split** β€” assign one font to headings and a contrasting one to body text (e.g. Georgia headings + Verdana body). [S1] - **Serif + sans-serif contrast** β€” pair a serif and a sans-serif to create deliberate contrast. [S1] - **Establish a boss font** β€” make one font dominant via size/weight/color. [S1] ## πŸ“– μ„ΈλΆ€ λ‚΄μš© (Details) The tutorial establishes four guidelines for pairing fonts: [S1] 1. **Complement** β€” "A great font combination should harmonize, without being too similar or too different." 2. **Font superfamilies** β€” use fonts within the same family designed to work together, like the Lucida superfamily variations. 3. **Contrast** β€” "Two fonts that are too similar will often conflict. However, contrasts, done the right way, brings out the best in each font." Serif-with-sans-serif combinations exemplify this approach. 4. **Hierarchy** β€” "One font should be the boss." Vary size, weight, and color to establish visual hierarchy. **Web-safe combinations** [S1] - Georgia (headings) + Verdana (body text) - Helvetica (headings) + Garamond (body text) Georgia and Verdana example: [S1] ```css body { background-color: black; font-family: Verdana, sans-serif; font-size: 16px; color: gray; } h1 { font-family: Georgia, serif; font-size: 60px; color: white; } ``` The Helvetica and Garamond pairing is described as another classic combination that uses web safe fonts, but its specific CSS is not displayed in an example box on the page β€” only a visual demonstration. (Exact CSS: Not found in source.) [S1] **Google Font pairings** listed on the page: [S1] - Merriweather + Open Sans - Ubuntu + Lora - Abril Fatface + Poppins - Cinzel + Fauna One - Fjalla One + Libre Baskerville - Space Mono + Muli - Spectral + Rubik - Oswald + Noto Sans Each pairing includes a "Try it Yourself" code example with the font declarations applied to a sample document about Norway. The explicit `` tags and `font-family` declarations for the Google Font pairings are not quoted in the page content. (Exact Google Fonts CSS: Not found in source.) [S1] ## πŸ› οΈ 적용 사둀 (Applied in summary) The page's applied example styles a "Beautiful Norway" sample document β€” Georgia headings over Verdana body text on a black background β€” and offers "Try it Yourself" demos for each Google Font pairing. No external project/commit applications found in the source. ## πŸ’» μ½”λ“œ νŒ¨ν„΄ (Code patterns) Heading/body contrast pattern (language: CSS): ```css body { font-family: Verdana, sans-serif; } h1 { font-family: Georgia, serif; } ``` ## βš–οΈ 비ꡐ 및 선택 κΈ°μ€€ (Comparison & decision criteria) The page frames pairing as a set of trade-offs: combinations must complement (not too similar, not too different); superfamilies guarantee harmony when fonts are designed together; intentional contrast (serif + sans-serif) outperforms near-identical fonts that conflict; and a clear hierarchy requires one dominant "boss" font set apart by size, weight, and color. Web-safe pairings (Georgia + Verdana, Helvetica + Garamond) favor reliability; the eight Google Font pairings favor expressiveness at the cost of loading external fonts. [S1] ## βš–οΈ λͺ¨μˆœ 및 μ—…λ°μ΄νŠΈ (Contradictions & updates) No contradictions found in the source. ## βœ… 검증 μƒνƒœ 및 신뒰도 - **μƒνƒœ:** draft - **검증 단계:** conceptual (μ‹€μ œ 적용 사둀 발견 μ‹œ applied/validated둜 승격 κ°€λŠ₯) - **좜처 신뒰도:** B (W3Schools β€” widely used educational reference, not a primary standards body) - **μ‹ λ’° 점수:** 0.86 - **쀑볡 검사 κ²°κ³Ό:** μ‹ κ·œ 생성 (New discovery) ## πŸ”— 지식 κ·Έλž˜ν”„ (Knowledge Graph) - **μƒμœ„/루트:** [[CSS Tutorial]] - **κ΄€λ ¨ κ°œλ…:** [[CSS Font Family]], [[CSS Google Fonts]], [[CSS Web Safe Fonts]] - **μ°Έμ‘° λ§₯락:** Referenced when choosing complementary heading and body typefaces for a site's typography system. ## πŸ“š 좜처 (Sources) - [S1] W3Schools β€” CSS Font Pairings β€” https://www.w3schools.com/css/css_font_pairings.asp ## πŸ“ λ³€κ²½ 이λ ₯ (Change history) - 2026-06-23: Initial draft synthesized from the W3Schools "CSS Font Pairings" page (Astra wiki-curation, P-Reinforce v3.1 format).