Get the most from each lesson’s live editor with a deliberate loop—same habits that transfer to real projects.
Recommended workflow
- Read the concept section before touching code.
- Change one utility group at a time (spacing, then flex, then color).
- Resize the preview pane to test responsive prefixes.
- Use browser DevTools to inspect which utility wins when debugging.
- Reset the editor if you drift too far from the lesson goal.
Review CSS cascade if two classes seem to conflict—Tailwind uses layered specificity by design, but custom CSS can still override utilities.
Self-check
- Why change one utility group at a time during learning?
- What DevTools panel confirms a Tailwind class is applied?
Challenge
CDN smoke test
- Open the playground and confirm Tailwind classes apply (try
bg-indigo-100on a div). - Add
hover:bg-indigo-200and hover the preview.
Done when: preview updates without a separate stylesheet file.