Layering vendor, component, and utility CSS
Layers can make large stylesheets easier to integrate by giving resets, dependencies, components, and overrides an explicit place.
✓ What you will learn in this topic
- Explain the key idea: Layers help with precedence but are not a substitute for component architecture.
- Apply the concept: The app layer wins over the vendor layer without needing a more complicated selector.
- Avoid this common mistake:
Concept explanation
Place third-party styles in a lower-priority layer when your application should be able to override them without increasingly specific selectors. Put shared base rules before components and intentional utilities after them. Unlayered normal declarations outrank layered normal declarations, so decide whether to layer all application CSS.
Layers do not isolate styles or scope selectors. They only affect cascade priority; component naming and architecture still matter.
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 vendor, app;
@layer vendor {
.demo { color: #334155; }
}
@layer app {
.demo { color: #1d4ed8; }
}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 vendor, app;
@layer vendor {
.demo { color: #334155; }
}
@layer app {
.demo { color: #1d4ed8; }
}Expected result: The app layer wins over the vendor layer without needing a more complicated selector.
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>@layer reset, vendor, tokens, components, utilities;
@layer components {
.card { padding: 1.25rem; }
}
@layer utilities {
.p-0 { padding: 0; }
}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
Assuming higher selector specificity always beats a declaration in another cascade layer.
Best practice
Declare a stable layer order early and keep unlayered styles intentional because they outrank normal layered declarations.
Practice exercise
Place reset, vendor, component, and utility rules into named layers and verify their intended order. Apply it to the example above and inspect the result at a narrow and a wide viewport.
Section summary
- Layers help with precedence but are not a substitute for component architecture.
- Declare a stable layer order early and keep unlayered styles intentional because they outrank normal layered declarations.
Knowledge check
Do cascade layers scope selectors to a component?
Reveal the explanation
Use component naming or other scoping tools for isolation; layers only organize cascade priority.
Finish the module lessons, then take the server-scored module quiz to check your understanding.
Practical example
css@layer vendor, app;
@layer vendor {
.demo { color: #334155; }
}
@layer app {
.demo { color: #1d4ed8; }
}
Expected result:
The app layer wins over the vendor layer without needing a more complicated selector.
Hands-on practice task
Place reset, vendor, component, and utility rules into named layers and verify their intended order.
In this section
Other lessons in Cascade Layers
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.