‘DOM’ino Effect

Share This Post

In today’s post, I would like to touch on the HTML DOM (Document Object Model). In building a web application, developers find themselves interacting with the DOM repeatedly. So what is the DOM?

The DOM at its most basic level is simply the pieces of the HTML page. There is terminology and methods associated with this interaction…

  • Tree – The DOM is sometimes referred to as a tree. This is because it is hierarchal in nature and each piece of the DOM is connected to the other. The concept of a DOM tree gives a very visual picture of the structure of the document.
  • Traversing the DOM – This is referencing moving around the DOM and interacting with each accordingly.
  • Nodes – Each piece of the DOM is called a node. So an HTML tag is called an element node. So a paragraph tag (<p>) would be referred to as a p element node. Text on the page is also referred to as a node, but in this case, it is called a text node.
  • DOM methods – The HTML DOM API has built in methods that allow interaction with the DOM. Here are a couple of examples:
    • getElementById(); – allows the grabbing of pieces of the DOM based upon the ID of the DOM node.
    • getElementsByTagName(); – allows the grabbing of pieces of the DOM based upon the node type. So a developer could grab all of the image tags (img) on a page. This returns the tags in an array data type.

In future posts, I will cover some more detailed DOM interactions, but one thing to keep in mind as you work with the DOM is how HTML works. For example, there are two main type of HTML elements…block and inline. The behavior of each of these can be altered by CSS, but it is important as a developer alters the DOM that they keep these aspects in mind.

Happy Coding!

Clay Hess

More To Explore


Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.


The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top

Need help?

Let's have a chat...


Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 


Begin Your Learning Journey Today!

Come back inside to continue your learning journey.