Hello Reader,
The last 3 week’s newsletters have been really long ones, so we’ll keep this one a little shorter 😅.
We'll get to the <article> and why HTML is probably the hardest language to get right down in the Other Awesome Stuff from Around the Web section below.
First though, if you missed any of those previous weeks, they were all a part of a series looking at creating projects that can help stand out on a portfolio:
As another very quick addition, learning in public is another great option that I’ve talked about in the past.
Whether it’s a live stream where you’re working on those projects or a blog where you share things you’re learning along the way, that type of thing is always great.
It also has the added bonus that others can benefit from what you're sharing as well!
🙋♂️ What I’ve been up to this week
Turning off inheritance on custom props is more useful than I’d thought
I was working on another video when I ran into an issue with a custom property, where it was being inherited by a sibling, and that caused my layout to break.
Very frustrating experience, but luckily, it’s easy to fix now that we have @property
, which allows us to declare if a custom property should, or shouldn’t be inherited.
🔗 Other awesome stuff around from the web
I shared something from Piccalilli last week, but this time I’m sharing just the site itself, rather than a specific post, because the redesign is live and it’s wonderful 🙂.
The article element
Heydon Pickering continues his dives into HTML elements, this time looking at the article element.
If you don’t think you need to learn more about it, this quote from the article might be enough to pull you in:
But what does the <article>
element offer, to this end? The answer is: not as much as one who cares about accessibility and who identifies as a responsible HTML author would hope.
He also brings up how it probably doesn’t make sense for a page that’s an article itself (like, if you click through the teaser text to get to the full blog post) that you use an article on that page… which I’d never considered before, but he makes a good case for why that is.
This is one of the reasons I believe that HTML is the hardest to get right, but the one everyone just takes for granted.
Feature detection when @supports doesn’t work
Bramus with a quick one here, looking at how we can use a registered custom property as a way to look for @starting-style support.
I love tricks like this!
And, if you’re not sure what @starting-style is for, it’s what enables us to now transition when we have a property with a discrete animation… so, in other words, a way to easily transition to and from a display: none!
🏁 </newsletter>
Have a fantastic week!
Kevin
Are you looking to step up your CSS? I've got both free and premium courses to help with that! They cover a range of skill levels too 👇
Beginner friendly (and free)
Conquering Responsive Layout
A free course to help you approach responsive layouts with the right mindset.
Enroll →
|
|
Intermediate
CSS Demystified
For those who've been writing CSS for a little bit now, but want to step up their game and start writing CSS with confidence!
Enroll →
|
|
Advanced
Beyond CSS
An advanced course that dives into project architecture, theming, design systems, and more.
Enroll →
|
|