72. Color, spacing and typography tokens
Module 15 · About 20 minutes · Lesson 71; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use color, spacing and typography tokens, and how can you prove it?
- Explain color, spacing and typography tokens using the example source
- Predict the visual or structural effect of one controlled change
- Repair the supplied fault and verify actual output
Predict
Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.
Understand
A design token names a reusable design decision, such as surface, text or space. Semantic names survive theme changes better than names such as blue-button. Tokens should have a small intentional scale and be tested for contrast in each combination. Keep primitive values and semantic roles understandable; an enormous token file is not automatically a better design system.
Important source lines
- index.html:1 <section class="token-card"><h1>Consistent decisions</h1><p>Tokens connect components.</p></section>
- A thematic grouping, usually identified by a heading. Attribute guidance: aria-labelledby optional for an explicitly named region.
- styles.css:1 :root { --space:16px; --surface:#edf2fb; --text:#172f54; } .token-card { padding:var(--space); background:var(--surface); color:var(--text); }
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.
Example 1: Color, spacing and typography tokens
The card reads its spacing and color roles from shared custom properties.
index.html
<section class="token-card"><h1>Consistent decisions</h1><p>Tokens connect components.</p></section>
styles.css
:root { --space:16px; --surface:#edf2fb; --text:#172f54; } .token-card { padding:var(--space); background:var(--surface); color:var(--text); }script.js
Expected: The card reads its spacing and color roles from shared custom properties.
Edit and Render This ExampleExample 2: Property: color
Sets the foreground text color; contrast depends on the actual background.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { color: #17324d; }script.js
Expected: Inspect .sample in the block context. Sets the foreground text color; contrast depends on the actual background. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 3: Property: padding
Creates internal space between content and border.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding: 24px; }script.js
Expected: Inspect .sample in the block context. Creates internal space between content and border. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 4: Article contents
A reusable article contents pattern with semantic source and responsive styling. Inspect its actual structure and interaction before adapting it.
index.html
<nav aria-label="Article contents"><h2>On this page</h2><ul><li><a href="#box">Box model</a></li><li><a href="#layout">Layout</a></li></ul></nav><main><h1>CSS field guide</h1><section id="box"><h2>Box model</h2><p>Internal and external space.</p></section><section id="layout"><h2>Layout</h2><p>Relationships between boxes.</p></section></main>
styles.css
body { font:18px/1.6 system-ui; color:#17324d; margin:1.5rem; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }
nav { border:1px solid #a8b8c8; padding:1rem; } section { padding-block:2rem; }script.js
Expected: Change the content and one design token, then test at narrow and wide widths. Preserve destinations, visible labels and native interaction.
Edit and Render This ExampleExample 5: Element: main
The document’s principal content, normally one visible instance.
index.html
<main><h1>Principal content</h1><p>The central task belongs here.</p></main>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: The document’s principal content, normally one visible instance. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleBuild and test
The card reads its spacing and color roles from shared custom properties. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<section class="token-card"><h1>Consistent decisions</h1><p>Tokens connect components.</p></section>
Starter styles.css
:root { --space:0; --surface:#edf2fb; --text:#172f54; } .token-card { padding:var(--space); background:var(--surface); color:var(--text); }Objective contract
[
{
"type": "variable",
"selector": ":root",
"property": "--space",
"value": "16px",
"label": "Spacing token defines the component padding"
}
]Hint 1
Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.
Hint 2
The relevant source uses --space:16px. The exercise instead uses --space:0. Identify its effect before changing it.
Hint 3
Restore the intended --space:16px operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<section class="token-card"><h1>Consistent decisions</h1><p>Tokens connect components.</p></section>
styles.css
:root { --space:16px; --surface:#edf2fb; --text:#172f54; } .token-card { padding:var(--space); background:var(--surface); color:var(--text); }Explain, reflect and extend
Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.
Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.
Troubleshooting and professional practice
If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. The card reads its spacing and color roles from shared custom properties.
Knowledge check
Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.
Optional AI prompts
- Explain this lesson’s source line by line using the actual objective above.
- Help implement one small extension and define normal, boundary and failure tests.
- Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.