Browser DevTools

About 45 minutesYou need: my-studio-site open in Cursor on the practice-bugs branch (Lesson 5.1), npm run dev running, Google Chrome
This video is in the full courseGet the course to watch every video and read every lesson in full. GHS 399, paid once.Get the course · GHS 399
Video · 14:18
Goal

Use Chrome's DevTools on your own site: inspect and test styles in the Elements panel, read the Console, check every file the page loads in the Network panel, and test on phone sizes in device mode.

Why this matters

Some bugs shout. They turn the page red and tell you the file and line. Lesson 5.1 handled those.

Other bugs whisper. A button has the wrong colour. An image doesn't load. A section is fine on your laptop but spills off the side of a phone. A form button does nothing when you tap it. No red screen, no message in the editor. Only something not quite right.

For whispering bugs, you need to look inside the page as the browser sees it. Chrome has a full set of tools for this, built in and free: DevTools. You used one small part of it in Lesson 0.1, when you changed a heading on example.com. Now you'll learn the four panels professionals use every day. They'll be essential in Stage 2, when you need to see whether an order really left the browser.

In the full lesson

  1. The idea in plain English
  2. Do it
  3. Check it worked
  4. Quick check
  5. What you can do now
Stage 2 · Make it workYou’ve seen the why. The how is in the course.

The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.

Get the course · GHS 399See what’s inside
Already have the course? Open the full lesson