Written by Harry Roberts on CSS Wizardry.
This morning I awoke to find Smashing Magazine had retweeted a tweet I made two months ago about how you should always try and apply margins in one direction only. This, like most rules in web development, is a very general (and breakable) rule. It’s even a rule you can opt not to follow at all, but after receiving a slew of Tweets asking why, I thought I’d write up why it’s a rule I live by, and one I’d recommend to anyone…
I’m not sure how I arrived at this rule, but I’m really glad I did and I would likely never ever change it. The basic premise is that you should try and define all your margins in one direction. This means always use
margin-bottom to push items down the page, and
margin-left to push them across the page. I’m going to focus mainly on
margin-bottom throughout this article as it’s the most obvious to explain, but this can be applied to both directions (top/bottom, right/left).
The benefits are, as I see them:
This next bit on its own is enough to convince me, this one tip is one of the most valuable ones I have, personally.
Whenever I start a new project I typically want to know two things; my base
font-size and my base
line-height. Let’s say that I choose a base
font-size of 16px and a base
line-height of 24px. This gives me (in proper units) this:
font:1em/1.5 "Comic Sans MS", cursive;
That 1.5 is my Magic Number. This is massively important; knowing this number allows me to set up my entire project’s vertical rhythm in one go:
Bosh. Done. Now any block level element (I may have missed some) I add anywhere in that page will have a
line-height of 24px (if my base
font-size is 16px) and will be spaced apart by 24px (again, if my base
font-size is 16px).
I can extend that list of selectors as and when I need to and all will remain in order:
For me that is reason enough to stick to just defining my margins in one direction, I can just drop any element anywhere and it will obey the same vertical rhythm as any others.
So if I know that all my margins are consistently in the same direction then I can be a lot more confident that if I add, move or remove an element my spacing won’t mess up. This isn’t just about something as pretentious as vertical rhythm, this is about spacing in general. If everything is the same then it doesn’t really matter what is where, it all behaves similarly.
If I had some odd situation where I have a
margin-top on element A, a
margin-bottom on element B and a
margin-bottom on element C how can I be sure that removing B won’t break anything? I can’t, because I mixed up my margins!
So if you can be sure things are a lot less likely to break there’s one less thing to worry (as much) about.
One counter argument I got on Twitter today was that I didn’t ‘get’ collapsing margins. This kind of response really annoys (and offends) me. A similar one I get is ‘You just don’t understand specificity!’ whenever I advise against the use of IDs. It’s a developer’s understanding of a subject that allows them to know when to avoid or circumvent something.
Collapsing margins aren’t rocket science but they are one more caveat, one more thing to remember. Look at all that in the spec, all of that to have to consider just as a result of adjoining margins on elements. Don’t mix
margin-bottom and you won’t even need to think about that.
As a developer gets better they try to be less clever. I know where using IDs can be a pain so I save myself the hassle by not using them, same with collapsing margins; no one gets points for taking the more complex route. I honestly believe that if anything with caveats or potential ‘gotchas’ can be avoided they should be*.
I find I have never had any collapsed margin oddities in any of my projects because I avoid introducing the possibility.
By applying the
margin-bottom to all block-level elements that means that most things you put into a page will carry that spacing. Let’s say for example you have a heading in a promotional box that you don’t wish to have a
margin-bottom, simply override the rule as you would with any sensibly architected CSS:
border-bottom:1px solid #ccc;
Using more specific selectors you can undo or alter your spacings with ease.
In working at Sky, there were times when we wanted a larger break between one section and another, let’s say double (
3rem) between a carousel and the content below it. Simple:
Interestingly, what I actually did was create an abstract class of
.landmark which carried that
margin-bottom:3rem; to denote any content that was deemed a large, thematic break in the page (signified by larger spacing).
Other times we had a boxed-off bit of content for which I used the Island Object. Some CSS like this…
Obviously there will come a time when this rule needs breaking; we can’t even try and kid ourselves–all web development rules get broken. However, before you do go against it, double and triple check that there isn’t a nicer solution. I really cannot remember the last time I broke this rule, but I’m sure I have and will need to in future. I just really, really try not to.
Everything I’ve written here is nigh on impossible to prove and isn’t quantifiable, but speaking anecdotally and from experience on some huge websites, the method I use works perfectly. More than perfectly. I genuinely cannot remember a time I have had problems with collapsing margins or spacing issues or anything arising from arbitrary margin declarations.
If you think this might be of use then I urge you to try it, it really has worked wonders on every site I’ve ever employed this on. Conversely, if I’ve missed a trick please do tell me!
If you don’t like the idea of it then that’s totally cool; I can’t prove anything and if you’re comfortable as you are then that’s great!
*From the guy who likes unquoted attributes in HTML… I know!
Hi there, I’m Harry Roberts. I am an award-winning Consultant Web Performance Engineer, designer, developer, writer, and speaker from the UK. I write, Tweet, speak, and share code about measuring and improving site-speed. You should hire me.
You can now find me on Mastodon.
I am available for hire to consult, advise, and develop with passionate product teams across the globe.
I specialise in large, product-based projects where performance, scalability, and maintainability are paramount.