Article
<div>s as far as the eye can see…
If you’ve ever looked an application’s HTML output, you’re likely quite familiar with this:
Endless tags with cryptic attributes. Looking in, how is it possible to make sense of that image without me telling you what application this is? Imagine working in an application that looks like this. Some of you reading this may already be in that exact environment.
Why is this the default pattern of building HTML? What is it about <div>’s that makes them so enticing to use with this frequency?
Starting with the roots of HTML, there really weren’t any tags to wrap around content other than <p> tags, which is short for paragraph. Thinking of how we currently use <div>s as wrappers for a massive variety of content blocks, “paragraph” doesn’t describe what is often used in <div>s.
Enter <div>.
This was the ultimate type of HTML tag. If at its base, HTML is a markup to contain elements of content, neat boxes that have no other purpose but to divide (as div is short for division) the page, then <div> should have been the first element conceived. It’s easy to understand why this tag is such a “go-to” because it’s broad enough to work in nearly any context.
Some of you may be thinking “Yep, that brings us up to date,” but we’re only up to HTML 3.2 by this point in the history, which was proposed to introduce to W3C on January 14, 1997.
That means, for over 20 years, we’ve stuck with <div> as the default wrapper.
Let’s have a little talk about HTML5. It’s awesome. Semantic tags have an incredible amount of benefits including but not limited to search engine optimisation, accessibility standards, and, important to the start of this conversation, code readability.
At this point, the support for HTML5 is well documented and we can use the new tags regularly without worrying about browser support. Here’s some support info from Can I Use, but the short version is this…
IE Edge Firefox Chrome Safari iOS Android
9+ All 21+ 26+ 6.1+ 7.1+ 4.4+
… it’s supported. Even with older browsers that may need support like older IE, there are alternatives to add support like html5shim.
Specifically we’re going to talk about semantic tags such as <article>, <aside>, <footer>, <header>, <main>, <nav>, and <section>. It would be quite difficult to find a type of page content that can’t be better described by one of these than generically, “a division”.
The other usage that is commonly mis-attributed to <div> is the tagging of content with a content-type purpose. Consider <address>, <blockquote>, <caption>, <cite>, <code>, <data>, <details>, <dialog>, <figcaption>, <meter>, <pre>, <progress>, <summary>, and <time> before using a <div> that might be displaying content meant to be one of these items.
When you step back and look at these content types, you can see why you might use it. Imagine trying to use an <img> tag for anything other than an image. It doesn’t make sense, but that’s the logic we’ve adapted to with <div> because of its universality. Everything is a division because it’s a section of the page that is divided by its bounds. A small amount of extra effort can make your markup infinitely more expressive to the next developer, company, or user of your application.
Here’s an entirely <div>-less blog-style site made from major semantic elements for layout, and more descriptive tags for the content within.
It’s not that there isn’t a use for <div>s, there absolutely is. We use them because they make so much sense. However, by adapting to use new technologies, we can capitalize upon existing and yet unseen benefits.
These tags will continue to grow support, features, and usage. Let’s be part of the progress!
Ackama has acquired OptimalBI, a New Zealand-based company specialising in data engineering, insights, and operations. This acquisition strengthens Ackama’s ability to support governments, the energy sector and mission driven organisations, where high quality data and data capabilities are…
Read more
This year at Ackama has been one of resilience and progress in a challenging environment. Following our acquisition of Common Code, we’ve continued to strengthen our capabilities and expand our impact. We’ve worked with…
Read moreSquareweave is now Ackama.
We've merged with New Zealand company Ackama!
We're excited to be working with our Kiwi colleagues to deliver ambitious, purposeful digital products on both sides of the Tasman.
Common Code is now part of Ackama.
We’re now part of Ackama, delivering purposeful technology across the Asia-Pacific.
Together, we’re creating impact across energy, government, international development, and beyond. Delivering pragmatic, innovative solutions where they matter most.