Hello Reader,
Creating websites was a hobby of mine for a long time. I started making my first sites in the late 90s with Photoshop slicing, table layouts, and image maps. I never thought writing HTML and CSS would become such an important part of my life.
After a wandering path of unrelated degrees, I ended up as a graphic designer at a small agency.
I loved it, but the pay was terrible, so I started freelancing on the side as well, mostly designing websites. After a few jobs, I figured that if they were hiring me to make the designs already, I could probably make more money by also coding those designs into actual sites as well.
Little did I know that making something for a client is a lot harder than the random hobby sites I made back in the day!
But even though it was hard, I enjoyed it even more than the design work.
Then things took a big turn.
I left my design job to become a teacher.
While the school’s focus was print design, once they found out I had web experience, I quickly became the go-to web teacher.
And that’s when I realized that while I could build a website, I didn’t really know what I was doing.
I had figured out a few patterns I could repeat to create the layouts I was designing, and I had enough experience to recognize the common pitfalls, but teaching was a completely different beast. I had to explain why things worked, and I had no idea.
So I started researching, reading, and watching any video I could get my hands on (there were a lot fewer back then), spending most of my evenings trying to find ways to explain things to my students.
And somewhere in all that, something shifted. While I learned about a ton of CSS features that I hadn’t even been aware of, the most important part was that I started to understand how CSS works.
Suddenly, the code I wrote just worked. Not because I memorized more stuff and knew more properties, but because I was finally working with the browser instead of against it. When I ran into a problem, I could figure it out without even needing Google because I understood what the browser was trying to do and where my instructions conflicted with it.
It honestly felt like I suddenly had a cheat code.
That’s what I want for you, which is why I created CSS Demystified. I wanted to give people the same shift I experienced, one that turned CSS from a source of frustration into something I enjoy, without you having to spend the years it took me for things to start to click.
As you might know, I shut down CSS Demystified a few months ago. That's because I've completely recreated the course from the ground up, including building a custom platform, so I didn't have to make any compromises due to the limitations of 3rd-party tools.
The new version is *finally* ready after more than a year's work. I’ll have a lot more details about the course for you tomorrow. For now, I’ll leave you with this, from someone who’s been through the original version of the course:
“You will learn to write CSS with confidence. This course gives you a structured guide on how to approach CSS by teaching you how to think and by giving you plenty of truly practical tools.”
Igor dos Reis — CSS Demystified V1 alum
Cheers,
Kevin
P.S. With this launch of CSS Demystified, I'll be sending more emails than usual over the next several days. If you aren't interested in the course and you’d like to only get my regular Sunday emails, click here to opt out of these extra emails. |