Tokens, layers, and component boundaries
A maintainable stylesheet communicates where values come from and which component owns a rule.
✓ What you will learn in this topic
- Explain the key idea: Use purposeful tokens and clear component boundaries to make styles easier to change.
- Apply the concept: The card reads spacing and shape from purposeful tokens and remains a distinct reusable component.
- Avoid this common mistake:
Concept explanation
Group design tokens, base rules, components, and utilities intentionally. Custom properties centralize values; cascade layers can establish precedence. Component classes should describe the part of the interface rather than its current visual accident.
Keep selectors shallow and avoid styling based on fragile DOM nesting. A component should work in more than one page region where appropriate.
Syntax
A CSS rule has a selector followed by declarations. Each declaration is a property and a value; the braces group the declarations that apply to matching elements.
@layer tokens, base, components, utilities;
:root { --space-card: 1.25rem; }
@layer components {
.card { padding: var(--space-card); }
}Example 1: a small page element
Use this HTML as the target and place the CSS in a stylesheet linked to the page, or inside a <style> element while experimenting.
<main class="demo card-grid course-grid dashboard-panel course-card-list dashboard-grid card-layout"><h2>Learning card</h2><p>Clear styles make this information easier to scan.</p><nav class="site-nav"><a href="/learn">Courses</a></nav><label class="form-field"><span>Email</span><input type="email" aria-invalid="true"></label><article class="card course-card dashboard-card theme-dark"><span class="badge status">New</span><div class="course-card__image"></div><h2 class="course-card__title card__title">Course update</h2><p class="status">New lessons are available this week.</p><a href="/learn" aria-current="page">Read the details</a><div class="actions course-card__actions dashboard-panel__actions"><button type="button">View lessons</button><button type="button" disabled>Unavailable</button></div></article></main>@layer tokens, base, components, utilities;
:root { --space-card: 1.25rem; }
@layer components {
.card { padding: var(--space-card); }
}Expected result: The card reads spacing and shape from purposeful tokens and remains a distinct reusable component.
Example 2: a practical interface card
The same idea can style a reusable card on a course page. The class selector keeps the rule attached to this component rather than changing every element of that type.
<section class="demo card-grid course-grid dashboard-panel course-card-list dashboard-grid card-layout"><h2>Learning card</h2><p>Clear styles make this information easier to scan.</p><nav class="site-nav"><a href="/learn">Courses</a></nav><label class="form-field"><span>Email</span><input type="email" aria-invalid="true"></label><article class="card course-card dashboard-card theme-dark"><span class="badge status">New</span><div class="course-card__image"></div><h2 class="course-card__title card__title">Course update</h2><p class="status">New lessons are available this week.</p><a href="/learn" aria-current="page">Read the details</a><div class="actions course-card__actions dashboard-panel__actions"><button type="button">View lessons</button><button type="button" disabled>Unavailable</button></div></article></section>.course-card {
display: grid;
gap: var(--space-card, 1rem);
border-radius: var(--radius-card, 1rem);
}Expected result: The course update reads as a distinct interface card, and its content follows the spacing, color, and layout choices in the rule.
Common mistake
Creating an elaborate naming or utility system before understanding the projectâs actual component needs.
Best practice
Choose a consistent convention, keep selectors shallow, and remove obsolete rules when components change.
Practice exercise
Refactor a page stylesheet into tokens, base styles, components, and small utilities without changing its appearance. Apply it to the example above and inspect the result at a narrow and a wide viewport.
Section summary
- Use purposeful tokens and clear component boundaries to make styles easier to change.
- Choose a consistent convention, keep selectors shallow, and remove obsolete rules when components change.
Knowledge check
Why keep selectors shallow in component styles?
Reveal the explanation
A component class provides a clearer styling boundary than a long chain of ancestors.
Finish the module lessons, then take the server-scored module quiz to check your understanding.
Practical example
css@layer tokens, base, components, utilities;
:root { --space-card: 1.25rem; }
@layer components {
.card { padding: var(--space-card); }
}
Expected result:
The card reads spacing and shape from purposeful tokens and remains a distinct reusable component.
Hands-on practice task
Refactor a page stylesheet into tokens, base styles, components, and small utilities without changing its appearance.
In this section
Other lessons in CSS Architecture and Maintainability
Broaden your knowledge
Related learning topics
HTML
Learn to structure accessible, meaningful web pages with a complete HTML course from first document to professional application patterns.
JavaScript
Build strong JavaScript foundations with browser examples, focused practice, beginner projects, and module quizzes.