This is a great (free!) course on learning CSS from the basics up. Nicely-pitched explanations with plenty of examples.
This is a guide to how to be a web developer.
Really good advice from Laurie.
What this site is not is a tutorial. Tutorials are very specific to a time and a technology. This is intended to be a guide to tell you all the things you can learn, so you can then go off and learn them.
This is a really thoughtful look at the evolution of CSS and the ever-present need to balance power with learnability.
Anselm isn’t talking about becoming a CSS wizard, but simply having an understanding of what CSS can do. I have had similar experiences to this:
In the past years I had various situations where TypeScript developers (they called themselves) approached me and asked whether I could help them out with CSS. I expected to solve a complex problem but for me — knowing CSS very well — it was always a simple, straightforward solution or code snippet.
Let’s face it, “full stack” usually means “JavaScript”—HTML and CSS aren’t considered worthy of consideration. Their loss.
The paradigm shift that web development is entering hinges on the fact that while React was a key enabler of the Single-Page-App and Component era of the web, in practice it normally tends to result in extremely poor products. Built-in browser APIs are now much more capable than they were when React was first invented.
As a self-initiated learner, being able to view source brought to mind the experience of a slow walk through someone else’s map.
This ability to “observe” software makes HTML special to work with.
Celebrating ten years of the wonderful community event.
Had you heard of these bits of CSS? Me too/neither!
I never would’ve known about the `display-mode` media feature if I hadn’t been writing about it.
CSS logical properties here, they just aren’t evenly distributed yet.
Applying the principle of least power to tools and technologies.