2.3 · Global colors & fonts (Site Settings)

Level 2 · Intermediate: design & rich content

2.3Global colors & fonts (Site Settings)

Goal: define a style guide (global colors and fonts) in the site settings for total, maintainable consistency.
Estimated time: 12 min · self-paced reading · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • The Site Settings define global colors and fonts applied everywhere.
  • Define a palette (primary, secondary, text, accent) and typical text styles (heading, body).
  • Define early, apply everywhere: changing the style guide is done in a single place.

Through-line — Nadia sets the style guide

Until now Nadia set the colors case by case — and slightly different shades of pink crept in everywhere. She redoes it all via the site settings: a clean palette, two text styles. From now on, when the joiner wants to adjust "his" pink, it's a single setting, propagated across the whole site.

Continues 1.4 (a preview of global) — here, the full setup.

1. The global style guide

The Site Settings — accessible from the editor menu — centralize the global design. There you define a color palette (primary, secondary, text, accent) and global text styles (main heading, subheading, body…). These values become reusable: instead of typing a color code, you pick "Primary color".

Nadia creates her palette (brand pink, dark grey for text, an accent) and two text styles. The whole site then shares the same identity.

2. Consistency and maintenance

The benefit is twofold: consistency (the whole site harmonized) and centralized maintenance (a palette change propagates everywhere automatically). The good practice: define your style guide from the start, then apply the global colors/styles on each element — never "hard-coded" values.

So, when the client is unsure about "his" pink, Nadia changes the primary color once, and buttons, headings and links all update at once.

Common misinterpretation: "Global colors are just to save a bit of time." No: it's the basis of a consistent and maintainable site. Without a global style guide, divergent shades creep in and every change becomes a project.
Global style guide applied everywhere A palette and styles defined in the site settings, applied to all elements, editable in one go. Site SettingsPalette + text styles → Applied everywhereButtons, headings, links… ↺ ChangeIn a single place Define early, apply everywhere, edit in one go.
Style guide defined once → applied everywhere → editable from a single setting.
Text version of the diagram (SEO / screen readers / translation): In the Site Settings: define a color palette (primary, secondary, text, accent) and global text styles. Apply them everywhere (instead of hard-coded values). A style-guide change propagates from a single place. Lesson: define early, apply everywhere.

🔎 Concrete example — Setting and applying the style guide (Nadia's case)

Site Settings → Global colors:
  Primary = #b4005a (pink) · Text = #333 · Accent = #e0218a
Site Settings → Text styles:
  Heading = font A, 2.2rem · Body = font B, 1rem, line height 1.6
→ Apply "Primary color" on the buttons (not a hard-coded code).
→ Client changes their mind about the pink: 1 setting, everything updates.

Result: a consistent identity, editable in one click.

Lesson: apply the global, never hard-coded values.

Section vocabulary

Site Settings
The global settings applied to the whole site (from the editor menu).

Simple example: Nadia defines palette and text styles there.

What it is not: setting each page separately.

Reflex: the global identity is driven here.

Global colors
A palette defined at the site level (primary, secondary, text, accent).

Simple example: picking "Primary color" rather than a color code.

What it is not: typing a different color code on each button.

Reflex: apply a global color, never hard-coded.

Global text styles
Typical typographies defined globally (heading, subheading, body).

Simple example: a "Heading" style reused everywhere.

What it is not: setting each heading's font by hand.

Reflex: one global text style per role.

Consistency / maintenance
The whole site shares the same style guide; a change propagates everywhere.

Simple example: changing the pink once updates the whole site.

What it is not: divergent shades for lack of a style guide.

Reflex: consistency = centralized style guide.

Define early & apply everywhere
Set your style guide from the start, then apply it on each element.

Simple example: style guide created before building the pages.

What it is not: inventing the colors as you go.

Reflex: style guide first, building next.

In practice — Setting up a global style guide

  1. Open the Site Settings.
  2. Define a palette: primary, secondary, text, accent.
  3. Define 2-3 global text styles (heading, body).
  4. Apply these global colors/styles on your buttons and headings (no hard-coded code).
You have a consistent style guide, applied everywhere and editable in a single place.

Ready-to-say script — selling consistency to the client (20 s)

"I created a style guide for your site: your colors and fonts, defined once and for all. The result: everything is harmonized, and if you want to adjust your pink or change the font, I do it in a single setting, propagated everywhere. No page-by-page touch-ups."

The style guide = visual consistency + responsiveness to requests.

Copy-paste template — site style guide

GLOBAL COLORS:
  Primary #______  Secondary #______  Text #______  Accent #______
TEXT STYLES:
  Heading: font ______ size ______
  Body: font ______ size ______ line height ______
APPLIED GLOBALLY (not hard-coded): yes / no
STYLE GUIDE DEFINED BEFORE BUILDING: yes / no

New site

Style guide from the start: you build directly with the global colors/styles.

Site to harmonize

Take the "hard-coded" elements and tie them to the global style guide.

Indecisive client

Global style guide = you change "their" pink in one click, as many times as they want.

Team

A shared style guide keeps everyone from inventing their own colors.

✓ Best practices

  • Define the style guide before building.
  • Apply global colors/styles, never hard-coded.
  • Keep few colors and styles, consistent ones.

✗ Common pitfalls

  • Setting colors case by case (divergent shades).
  • Forgetting to apply the global (hard-coded values).
  • Multiplying colors and fonts.

Key takeaways

  • Site Settings = the site's global style guide.
  • Palette + text styles reusable everywhere.
  • Change propagated from a single place.
  • Define early, apply everywhere.

48h challenge — apply tomorrow

Create a palette (4 colors) and 2 text styles in the site settings, then apply them on your buttons and headings. Change the primary color and watch the global update. 20 minutes.

Section exit checklist
  • I've defined a palette and global text styles.
  • I apply them everywhere (no hard-coded values).
  • I can change the style guide in a single place.
Self-assessment 1-5: is my style guide centralized?do I apply the global rather than hard-coded codes?

Frequently asked questions

Where do I define global colors?

In the Site Settings, accessible from the editor menu. There you create a palette (primary, secondary, text, accent) reusable everywhere.

What do you gain with a global style guide?

Consistency (the whole site harmonized) and centralized maintenance: a color or font change propagates everywhere automatically, without touching each page.

Can I still hard-code a color occasionally?

It's possible but discouraged: it creates inconsistencies and complicates changes. Always prefer applying a global color.

Check your understanding — scenario

The joiner is likely to change his mind several times about "his" pink. How does Nadia organize herself?

Additional resources (optional, to go further)

Level 2 examFresh, harder questions to test what you've learned