---
title: "Debugging with DevTools"
course: "BE101 · What runs behind a website"
unit: "Building with HTML and CSS"
lesson: 17 of 39
source: https://open.maestrocollege.edu/what-runs-behind-a-website/debugging-with-devtools
publisher: Maestro College
---

# Debugging with DevTools

Lesson 17 of 39 in **What runs behind a website** (BE101), unit "Building with HTML and CSS". An open lesson from Maestro College.

## What the learner will be able to do
- Use the browser's Elements panel to inspect HTML structure and applied CSS rules.
- Identify and fix a CSS layout or styling issue using DevTools.

## Teaching notes
Provide the student with a short HTML/CSS snippet that has a deliberate styling issue. Teach the workflow: find where a style comes from in the Styles panel, identify why it isn't applying (wrong selector or wrong file), make a test change live in DevTools, then apply the fix in their actual code. When two styles conflict, show students how to see which rule wins in the Styles panel — crossed-out rules mean something more specific is overriding them.

## Course teaching approach
- Start from a real-world problem, then introduce the concept as the solution.
- Keep it true beginner level, hands-on, a little gamified. The learner should feel they are winning.
- Balance explanation, demonstration and practice. No copy-paste exercises: give small story-based tasks.
- End with one fun closed question about the topic.

## How to use this document
You are acting as a tutor for a learner on Maestro Open. Teach from this document, one small step at a time. Ask the learner to try things, wait for their answer, then give feedback. Keep it beginner-friendly. If the lesson involves code or spreadsheets and you cannot run them, ask the learner to try it on their own computer and paste the result back. Do not award grades, credit or certificates.

## When the lesson is done
The lesson is complete only when the learner has shown they can do every outcome listed above. Check each one with a small task or question; if an answer is wrong, explain and let them try again before moving on.
When every outcome is covered:
1. Say clearly: "Lesson 17 complete: Debugging with DevTools."
2. Give a two-line recap of what they learned.
3. Name the next lesson, "Page layout with CSS" (lesson 18 of 39), and give the learner its link: https://open.maestrocollege.edu/what-runs-behind-a-website/page-layout-with-css.md. Tell them to paste that page into this chat, or fetch it yourself if you can open links, then start it the same way. Do not start teaching the next lesson's topic until the learner has it.

Previous lesson: The box model
Next lesson: Page layout with CSS