Weekly newsletter, where I talk about tangentially-related front-end development topics and share what I've been up to in the last week, plus any cool/fun/interesting/useful links I come across as well.
Share
The hidden answers
Published about 2 months ago • 2 min read
Hello Reader,
Sometimes you run into a CSS problem, and you do everything right, but still can't figure out what is going on.
You don’t pile on Band-Aids. You stop and think about why it’s happening. You narrow it down to a specific question. You search for an answer.
And you get nothing.
This happened to one of my students a while back. They added padding to an element, and that padding covered the text of the paragraph above it.
They played around with it and tried a few different things. Same result every time. Being able to reproduce the issue like this, it was clearly an intentional behavior, but why?
They stopped, thought about it, tried to figure out why.
They searched for box model information and didn’t come across the answer.
They looked up padding specifically. Still nothing.
They searched the MDN, W3Schools, and even took the time to read parts of the CSS spec in hopes of figuring out what the heck was going on.
They did everything right. They didn't pile on fixes, but couldn't come up with a solution.
Even the most up-to-date AI models are of no help.
AI doesn't always have the right answers either.
None of Claude’s answers here helps in any way, and the “throw a z-index on there” is really one of those shots in the dark, hoping for the best type of things that we might try as a last resort.
The answer? They needed to look up inline formatting context.
But how were they supposed to know that? Nobody talks about inline formatting contexts. It's not in any beginner or intermediate tutorial. It's not something AI is going to surface because no tutorials or Stack Overflow answers talk about it, so it has no idea that's the answer either.
It's one of those foundational pieces of how the browser actually renders CSS that almost nobody teaches, but that changes everything once you understand it.
This is the kind of knowledge gap that no amount of Googling or prompting will fill, because when you don't know about it, you don't know that's where you need to look for the answer.
That's the kind of gap CSS Demystified is built to close.
Not by covering every property (there are too many), but by teaching you how CSS actually works, and diving into the layer underneath the properties that govern how everything behaves.
Once you have that, you stop running into invisible walls. You know where to look, or better yet, you already understand why something is happening before you even need to look it up.
"I now view CSS as a complex language in its own right which can be leveraged once it is well understood." — Joe Sheridan CSS Demystified alum (v1)
"If they wanted to learn how the browser actually applies CSS, they should start here." — thecodeviking CSS Demystified alum (v1)
And remember, you can get 20% off the new version of CSS Demystified through April 7th. After that, the doors will stay open, but at the full price of $199 instead of $159.
(If you’re in a country where I support purchasing power parity, the best available discount is applied automatically at checkout, whichever is higher between that and the launch coupon.)
If you're on the fence, or have any questions, please hit reply and ask away. And if you're curious about the entire curriculum, you can find it here.
Cheers, Kevin
P.S. Also, there are already more modules in the works, with the next one being Writing Resilient CSS. If you enroll now, you'll get all the future modules for free, but the price will go up as more content is added.
P.S. If you’d like to stop hearing about CSS Demystified and stay on my regular Sunday list, click here.
Weekly newsletter, where I talk about tangentially-related front-end development topics and share what I've been up to in the last week, plus any cool/fun/interesting/useful links I come across as well.
View this email in your browser (or share it with a friend!) Hello Reader, Earlier this week, I posted this on Bluesky. I’m not panicking about the talk itself right now, but as I’ve spent time working on my talk this week, imposter syndrome has hit hard. I know for a lot of people, and especially with newer developers, I’m either the person or one of a handful of people they think of when they think of CSS, so it might seem a little crazy for me to be having imposter syndrome, but boy is it...
View this email in your browser (or share it with a friend!) Hello Reader, In the last three days, I’ve created more content than I usually do in one week (and no, don’t worry, I’m not about to try and sell you some productivity system 😆). As I sat down to write this, I wondered what I had done differently to get so much done, and at least some of it was due to a small tweak I made to my workflow on Monday. I won’t bore you with the details, but I want to talk about the idea of removing...
View this email in your browser (or share it with a friend!) Hello Reader, And I’m back from Smashing Conf Amsterdam, where I had an absolutely wonderful time! Amsterdam is such a beautiful city Amsterdam is one of my favourite cities to visit, and Smashing knows how to put on a wonderful conference, so I had high expectations in combining the two, and it didn't disappoint 😊. As for my talk, it went great… and what an amazing venue to speak at! The Pathé Tuschinski theatre As for my talk, the...