Selectors — Complete Guide
Selectors — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of CSS Tutorial on Toolliyo Academy.
On this page
CSS Tutorial · Lesson 3 of 100
Selectors
Foundations & Layout → Responsive & Motion → Architecture & Perf → Projects
Foundations & Layout · 1 — Style · ~12 min read · CSS — Foundations
1. Introduction
Today: Selectors. Read the diagram, paste the CSS, then change one value and watch the UI update.
Selectors pick which elements get styled — by tag (p), class (.btn), id (#nav), or combinations (.card h2). More specific selectors win when rules conflict.
2. Real-world story
Product needs nav links subtle but CTA buttons bold blue.
Outcome: Targeted selectors keep global nav styles separate from button variants.
3. Why it matters
StyleVerse dashboards target sidebar links, primary buttons, and error text differently. Selectors are how you aim styles precisely.
4. Visual understanding
Read this diagram — the mental model for Selectors.
HTML elements
▲
CSS rules target them
selector { property: value; }
cascade + inheritance + specificity decide the winner
5. Key concepts (easy words)
| Idea | Meaning |
|---|---|
| What | Selectors pick which elements get styled — by tag (p), class (.btn), id (#nav), or combinations (.card h2). More specific selectors win when rules conflict. |
| Remember | Element, class, and id are core selector types. Combine selectors to narrow targets. Prefer classes for reusable UI pieces. |
| Practice tip | Change one property, refresh, watch DevTools Computed. |
6. How it works
- nav a styles links inside navigation. .btn-primary targets elements with that class. #alert-banner styles one unique banner by id.
- Element, class, and id are core selector types.
- Combine selectors to narrow targets.
- Check the result in DevTools → Computed and the box model overlay.
7. Choose wisely
| Option | Notes |
|---|---|
| Do | Practice Selectors on a small StyleVerse card |
| Avoid | Copying huge frameworks before learning core CSS |
8. Try this example
Paste into a <style> block (or use Run Example). Refresh to see StyleVerse UI changes.
nav a { color: #555; text-decoration: none; }
.btn-primary { background: #2874f0; color: #fff; padding: 10px 20px; }
#alert-banner { border-left: 4px solid #e53935; }Line walkthrough
| Code | What it means |
|---|---|
nav a { color: #555; text-decoration: none; } | Selector — picks which elements get these declarations. |
.btn-primary { background: #2874f0; color: #fff; padding: 10px 20px; } | Selector — picks which elements get these declarations. |
#alert-banner { border-left: 4px solid #e53935; } | Selector — picks which elements get these declarations. |
Run Example »
Edit the code below and click Run to see the result in Toolliyo’s live editor.
9. Another real-world angle
10. Best practices checklist
- Prefer classes over ids for reusable StyleVerse components.
- Use design tokens (CSS variables) for color and spacing.
- Mobile-first media queries; test keyboard focus.
- Keep specificity low — avoid !important except rare overrides.
- Animate transform/opacity when you can; respect prefers-reduced-motion.
11. Common mistakes
- Using id selectors everywhere — classes scale better for design systems.
- Overly long selectors like div div div p — hard to maintain.
12. Practice in the browser
- Build HTML with nav, a button class="btn-primary", and div id="alert-banner".
- Apply the three rules in CSS.
- Inspect each element in DevTools to see matched selectors.
- Try nav .btn-primary to combine tag and class.
Experiments
- Add :hover to nav a and lighten the link color.
- Create .btn-secondary with a gray background.
13. FAQ
Where should I put CSS for Selectors?
Start in a <style> block or styles.css linked from HTML. Later use CSS Modules, Tailwind, or tokens in a design system.
Why is my rule not applying?
Check selector match, typos, specificity, and whether a more specific rule or inline style wins. DevTools Computed tells the truth.
Flexbox or Grid for this?
Flex for one direction (toolbars, card rows). Grid for two-dimensional page frames. Many UIs use both.
14. Interview questions
Explain Selectors simply.
Selectors pick which elements get styled — by tag (p), class (.btn), id (#nav), or combinations (.card h2). More specific selectors win when rules conflict.
How do you debug CSS?
Inspect element, toggle declarations, read Computed styles, outline the box model, and reduce specificity conflicts.
How does this show up in production UI?
Targeted selectors keep global nav styles separate from button variants.
15. Remember
- Element, class, and id are core selector types.
- Combine selectors to narrow targets.
- Prefer classes for reusable UI pieces.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!
