I’ve been using CSS as a web developer since CSS became something we could actually use. My first websites were built using
<font> tags and
<table>s for layout. I remember arguments about whether this whole CSS thing was a good idea at all. I was quickly convinced, mostly due to the ability to easily change the font on an entire site in one place. Managing common styles was so useful at a time when most websites were just a stack of HTML pages with no management of content or any form of templating. I was an early adopter of using CSS rather than tables for layout, despite the backdrop of people asking, “but what about Netscape 4?”
CSS is a remarkable language. Those early sites were developed in a time where the best we standards advocates hoped for was that browsers would support the CSS that existed; that developers would validate their HTML and CSS and use the CSS that existed. Yet, a website built back then that is still online, or one accessed via the Wayback Machine will still work in a modern browser. Such is the care that has been taken to not break the web by the CSS Working Group, and the other groups working to add features to the web platform.
I’ve been teaching CSS for almost as long as I’ve been using CSS. I’m incapable of having a thought without turning it into words. I write things down to remember them, I write things down to help them make sense to me. This leaves me with a lot of words, and from the earliest days of my career I had an idea that they might be useful to other people and so I started to publish them. Over the years I’ve learned how to teach people, discovered the things which seem to help the various concepts click for folk with different ways of learning and processing information. Since the early days of CSS layout, we’ve been teaching it along the following lines.
- this is a block thing
- this is an inline thing
- you can turn the block things into inline things and vice versa using the
- this is the Box Model, it is very important and also kind of weird.
Typically we would teach CSS by jumping right in, styling up a layout and explaining the strange collection of hacks that allowed for a layout as we went along. Unlike other languages, where we might start with the core fundamentals of programming, in CSS we had very few concepts to teach outside of building things and explaining the weirdness in the context of actual layouts. The Box Model was important because it was all we really had in terms of layout. It was core to our method of giving things a size and pushing them around in a way that would allow them to line up with other carefully sized things to make something that looked like a grid. If you didn’t understand the standard Box Model, and that the width you set wasn’t actually the width the thing took up, your carefully calculated percentages would add up to more than 100%, and bad things would happen.
Over the last few years, we’ve been handed all of these new tools, Flexbox and Grid give us a layout system designed for CSS. Perhaps less obviously, however, a set of concepts are emerging that give us a real way to explain CSS layout for the first time. There has been something of a refactoring of the language, turning it from a collection of hacks into something that can be taught as a cohesive system. We can start with normal flow and move onto what it is to change the value of
display because it is here that all of our new layout capabilities live. We can share how
display controls two things – the outer value of
inline and the inner formatting context – which might be grid, or flex, or normal flow.
Explaining Writing Modes early on is vital. Not because our beginner is going to need to format a vertical script, or even use vertical writing creatively immediately. It matters because writing modes explain why we talk about start and end, and the block and inline dimensions rather than the physical top, right, bottom and left corners of their screen. Understanding these things makes alignment in grid and flexbox and the line-based positioning in grid much easier to understand. The Box Model can then drop back to a brief explanation of the fact that
block-size) relate to the
content-box and we can change it to relate to the
border-box with the
box-sizing property. In a world where we aren’t giving things a size and pushing them around, the Box Model becomes just part of our discussion on Box Sizing, which includes the intrinsic sizing far more useful when working with flexbox and grid.
Finally we need to focus on the idea of Conditional CSS. Media Queries and Feature Queries mean we can test the environment of our user using metrics such as their viewport size, whether they are using a pointing device or a touchscreen, and the capabilities of their browser. We can never be sure how our websites are going to be encountered, but we increasingly have the ability in CSS to optimize for the environment once we are there. One of the greatest skills we can give to the person beginning their journey as a web developer is an understanding of this truth. The person visiting your site might have a touchscreen, they might be using a screen reader, they may be on a small-screen device, and they might be on IE11. In all of these cases, there are things you want to do that will not work in their situation, your job is to deal with it and CSS has given you the tools to do so.
As I started my CSS layout journey with a backdrop of people complaining about Netscape 4, I now continue against a backdrop of people whining about IE11. As our industry grows up, I would love to see us leaving these complaints behind. I think that this starts with us teaching CSS as a robust language, one which has been designed to allow us to present information to multiple environments, to many different people, via a sea of ever-changing devices.
enjoyed the article, we have come a long way since CSS was introduced and with the introduction of SCSS, SASS, LESS etc.
Its turned into its own full-fledged programming language to help support the development of websites and Web Apps.
I have started to enjoy writing CSS with preprocessors where you can separate the logic of each CSS components and pages etc.
Can’t wait to see what the future will bring!
Thank you Rachel for all of your hard work improving the css we have to work with, it is much appreciated.
I remember the days before CSS was a thing. I read a lot of the back and forth about it also. I was on the side that CSS wasn’t a good thing. And I’d say within a year my mind was changed. I do think CSS needs to be a little more programmy. And it seems to be heading that way somewhat. We have Custom Properties, Calc, Animations and such. Now if we get loops I think I’d be happy for a while. Overall I have been excited to see how the web has grown over the years and I am quite curious how it will look in another 5 years.
Good article Rachel as always,
Have a look on CSS preprocessors : SASS, LESS, etc… They extend a lot the basic CSS with super useful tools like lists, loops, etc… And allows you to make it a lot more “programmy”
Hi Michael, I do use preprocessors, but I am talking about the actual CSS spec that should add more program style features. They seem to be implementing them in slowly and I have seen the snail’s pace that the W3C can go.