Transitions — Complete Guide
Transitions — 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 31 of 100
Transitions
Foundations & Layout ✓ → Responsive & Motion → Architecture & Perf → Projects
Responsive & Motion · 2 — Adapt · ~13 min read · CSS — Animations & Effects
1. Introduction
Today: Transitions. Read the diagram, paste the CSS, then change one value and watch the UI update.
Transitions animate property changes smoothly over time. transition property, duration, timing-function, and delay control how hover and state changes feel.
2. Real-world story
Flipkart-style CTA darkens on hover with subtle lift.
Outcome: 200ms transition feels responsive, not sluggish.
3. Why it matters
StyleVerse buttons and cards use subtle transitions so banking UI feels polished without distracting motion.
4. Visual understanding
Read this diagram — the mental model for Transitions.
trigger (hover / class / scroll)
│
transition OR @keyframes
│
transform / opacity (GPU-friendly)
prefers-reduced-motion → quieter motion
5. Key concepts (easy words)
| Idea | Meaning |
|---|---|
| What | Transitions animate property changes smoothly over time. transition property, duration, timing-function, and delay control how hover and state changes feel. |
| Remember | transition lists property, duration, easing. Hover and focus states trigger smooth change. Prefer transform and opacity for GPU-friendly motion. |
| Practice tip | Change one property, refresh, watch DevTools Computed. |
6. How it works
- Base button transitions background and slight lift on hover over 200ms. Only listed properties animate — others snap instantly.
- transition lists property, duration, easing.
- Hover and focus states trigger smooth change.
- Check the result in DevTools → Computed and the box model overlay.
7. Choose wisely
| Option | Notes |
|---|---|
| Do | Practice Transitions 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.
.btn {
background: #2874f0;
color: #fff;
padding: 10px 24px;
border: none;
border-radius: 6px;
transition: background-color 0.2s ease, transform 0.15s ease;
}
.btn:hover { background: #1a5fd0; transform: translateY(-1px); }Line walkthrough
| Code | What it means |
|---|---|
.btn { | Selector — picks which elements get these declarations. |
background: #2874f0; | Declaration — property and value that change appearance. |
color: #fff; | Declaration — property and value that change appearance. |
padding: 10px 24px; | Declaration — property and value that change appearance. |
border: none; | Declaration — property and value that change appearance. |
border-radius: 6px; | Declaration — property and value that change appearance. |
transition: background-color 0.2s ease, transform 0.15s ease; | Declaration — property and value that change appearance. |
} | Ends the rule block. |
.btn:hover { background: #1a5fd0; transform: translateY(-1px); } | 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
- transition: all — animates unexpected properties and hurts performance.
- Long transitions on layout properties like width causing jank.
12. Practice in the browser
- Hover button and observe color fade.
- Change duration to 0.5s for slow motion demo.
- Add transition: none for reduced-motion users.
- Limit transitions to transform and opacity for performance.
Experiments
- Add box-shadow transition on hover for elevated card.
- Use transition-delay: 0.1s for staggered menu items.
13. FAQ
Where should I put CSS for Transitions?
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 Transitions simply.
Transitions animate property changes smoothly over time. transition property, duration, timing-function, and delay control how hover and state changes feel.
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?
200ms transition feels responsive, not sluggish.
15. Remember
- transition lists property, duration, easing.
- Hover and focus states trigger smooth change.
- Prefer transform and opacity for GPU-friendly motion.
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!
