Overview

DevTools let you see what your design is actually doing. This guide connects what you already know about inspecting HTML and CSS to understanding how JavaScript behavior works.

New here? Start with the tutorial

Your First 15 Minutes is a hands-on walkthrough using the Console Playground. You'll open DevTools, run your first JavaScript, and discover the hidden message. Takes about 15 minutes.

What You Already Know

From DESN368, you're comfortable using Firefox's Inspector to examine HTML structure and CSS styles. You know how to:

This guide builds on that foundation. Everything here uses Firefox DevTools—the same tools you already know.

The Two Sides of DevTools

DevTools has two sides that work together. You already know one of them:

┌─────────────────────────────────────────────────────────────────┐
│                        THE PAGE                                  │
│                                                                  │
│   What you SEE                    What it's DOING               │
│   (Inspector)                  (Console)                        │
│                                                                  │
│   ┌─────────────┐               ┌─────────────┐                 │
│   │ HTML Tree   │◄────────────►│ DOM Objects │                 │
│   │ CSS Rules   │               │ Events      │                 │
│   │ Layout      │               │ State       │                 │
│   └─────────────┘               └─────────────┘                 │
│          │                             │                         │
│          ▼                             ▼                         │
│   "This element has                "When I click,                │
│    these styles"                    this happens"                │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

The Inspector shows you structure and appearance. The Console shows you behavior and state. The bridge between them is a simple tool called $0.

The $0 Bridge

When you select an element in the Inspector, you'll see == $0 next to it. This means you can type $0 in the Console to reference that exact element.

Try it now
  1. Right-click any element on this page → Inspect
  2. Notice the == $0 indicator next to it in the DOM tree
  3. Click the Console tab (or press Esc for the split view)
  4. Type $0 and press Enter
  5. The Console shows you the same element you selected visually

This is the bridge. Visual selection becomes code access. Once you have $0, you can ask questions:

// What classes does this element have?
$0.classList

// What data attributes?
$0.dataset

// Add a class and watch the Inspector update
$0.classList.add('active')

What You'll Learn

What This Guide Skips

Traditional DevTools tutorials focus on debugging complex JavaScript. That's not where designers start. Here's what we're setting aside for now:

Engineering Focus Designer Focus
Breakpoints and step debugging Reading what changed
Call stack analysis Watching events fire
Memory profiling Checking element state
Network request debugging Understanding errors

The engineering tools exist and you may need them later. But for learning how behavior works, we start simpler.

Next Steps

If you haven't done the tutorial yet, start there:

Your First 15 Minutes →

Otherwise, explore the sections that match what you're trying to do:

Bookmark This Guide

You'll use DevTools throughout this course—for Lab 0-2 this week, for the theme toggle in Week 1, and for every project after. Keep this guide handy.