Introduction To The Dom

Problem Statement

We know how to write HTML and style it with CSS. But what if we want to do more with the content in our pages, such as adding or deleting elements or modifying them? It's time to move on to interactivity, and understanding the Document Object Model, or DOM, will give us the bridge to get there.


  1. Identify the Document Object Model
  2. Interact with the Document Object Model
  3. Explore how JavaScript manipulates the DOM

Identify the Document Object Model

Just as your DNA represents a code-based version of you, the DOM represents a code-based version of a web page. Because of this, when you change the DOM, you change what's displayed in the browser. Adding elements, removing elements, changing elements in the DOM changes what you see in the browser screen. Thanks to the DOM and the way it creates a representative model of document elements, we can use a language such as JavaScript to work with those elements and add to them, delete them or modify them.

To see the DOM in action, let's take a look at the HTML that constructs every website we visit.

NOTE: We recommend that you use Google Chrome. (You can download chrome here). Because Chrome has several developer-friendly features, it's a preferred development tool.

Change the URL of a web page to view the source

In a Google Chrome browser, go to the URL To see the HTML of that page, add view-source: to the front of the URL. The complete final URL will be view-source:

By using the view-source URL prefix, all the page's source HTML will be revealed to you. It will look something like this:


The browser reads this HTML, along with CSS and JavaScript, to create the DOM.

Notice that what we see in our the view-source tab looks very similar to HTML you may have seen previously.

<!DOCTYPE html>
        <meta charset="utf-8">
          <link rel="stylesheet" href="style.css">
    <img id="kitten" class="" src="" alt="" width="120" height="120">
  <script src="" charset="utf-8"></script>

It may look like our browser is displaying the HTML that we see, but it is not. Instead, our browser is displaying the Document Object Model of the respective web page.

Interact with the Document Object Model

The best way to understand the Document Object Model is to interact with it. Let's practice.

  1. Open the Google Developer console

You can open the developer console by opening the context menu (click while holding ctrl on Mac) and choosing Inspect:


Alternatively, from this web page, look at the Chrome menubar at the top of the page. Click on "More tools", then select ""Developer Tools". This will open the Google Developer Console.

developer tools menu

  1. Manipulate the DOM


When you open the Google Developer Console, you will see what looks like HTML. There are head tags, body tags, divs, etc. Now from inside the developer console, click on the element that says header, and then press the delete button on your keyboard. You should see the header at the top turn white. You just deleted it!


Now did you just delete the HTML? No. Let's prove it.

View the page source. Right click (or two fingers click on the mac) on the lesson page in the browser and select view page source. You will see the that the HTML is just as it always was, with a header tag and lots of other elements inside.


The changes that the developer console caused, and the changes the developer console currently displays are changes in the Document Object Model, but not in our HTML. Our webpage now looks blank, reflecting the missing header in our DOM, even though our HTML still has content in the header tags.

So we can conclude that by changing the Document Object Model, we can change the way our web page displays. And we can do this even if our HTML is unchanged. The HTML is essentially the starting point of the page's content. But as we just saw by deleting the header of the page, what is displayed can change. When we change it, we change the Document Object Model, and that changes the appearance in the browser. The HTML, however, once loaded on a webpage, does not change.

Explore How JavaScript Manipulates the DOM

With JavaScript we can (1) view a current representation of our Document Object Model. With JavaScript we can also (2) select specific portions of the DOM, and manipulate them, which changes what shows up in a browser window.

Let's get to it.

  1. Use JavaScript to view the current representation of the DOM

From inside the developer console, click on the tab that says the word "console." At the bottom you will see a cursor. There, type the word document and press "Enter.""

You'll get a #document returned. Click the triangle and you'll see the DOM. If you followed along above, you'll see a head tag, but no header tag. So by typing in document it looks like our header is gone. However, if we view page source, the HTML is unchanged. Remember, this is the difference between the DOM (current representation of the page) and the HTML (the initial representation of the page).

  1. Use JavaScript to manipulate our DOM

Refresh your browser to get the header back. Let's remove the header now with JavaScript. Open up the console and type in the following and press "Enter."


This will return something like this: <header class="site- header">...</header>. Go ahead and click on that display triangle to see more.

It retrieves the header tag, which contains the lesson title among other things. OK, now let's do something with this header. Open up the console, and type in the following:


Take a look at the top of the page again. The header is gone. But do you think the HTML has just changed? Well, no. As you know, the HTML never changes after it is first rendered. Instead, we accessed the Document Object Model, which altered the model and that altered the appearance of our web page. This is the same as we did before, but with code. To get the header back, just hit refresh.



  • HTML is a markup language used to display content in a browser. When we change the appearance of a web page, what we are really changing is the Document Object Model, which directly determines the appearance displayed in the browser.
  • We can view and manipulate the Document Object Model by opening our developer tools, but when we do so the HTML is not changed.
  • We can also view our Document Object Model by opening the console and typing in the word document.
  • We can select a specific piece of the DOM by using JavaScript, such as document.querySelector('header'), and we can also use JavaScript to alter our DOM with document.querySelector('header').remove()
  • To get your header back, just hit refresh
Unlock your future in tech
Learn to code.

Learn about Flatiron School's Mission

With a new take on education that falls somewhere between self-taught prodigy and four-year computer science degree, the Flatiron School promises to turn students with little programming experience into developers.

In the six months since the Manhattan coding school was acquired by WeWork, it has spawned locations in Washington, D.C., Brooklyn, and London. Now, WeWork is opening a fourth Flatiron School location, this time in Houston.

Adam Enbar, Flatiron School's cofounder, believes now is the time to grow. "How the world is changing has impacted working and learning in very similar ways. We think education fundamentally is about one thing: enabling people to pursue a better life."

Learn. Love. Code.
Students come to Flatiron School to change their lives. Join our driven community of career-changers and master the skills you need to become a software engineer or a data scientist.
Find Us