When I first learned CSS clip-path back in the days, I took more time than I had expected, and I struggled to memorize it, too. I don’t know the exact reason, but maybe because I didn’t use it that much? In this article, I aim to provide you with a clear explanation of how clip-path works in detail when to use it, and how you can use it today in your web development projects.
I’ve seen CSS frameworks come and go and always favored a bespoke CSS approach for every site. I was reluctant to dive into yet another CSS framework, but after continued internal discussion within the front-end development team, I finally built a site (or two) with Tailwind CSS. At first, I didn’t go all in and only exposed a couple of variants for spacing, but now I’m all in. So as a reluctant grump old web developer who has finally given Tailwind a chance, here are a few thoughts on what I love and hate about it.
In some cases, browsers display large text at different vertical positions across operating systems. In CSS Fonts Module Level 4 there’s a great solution for that issue: Default font metrics overriding: the ascent-override, descent-override and line-gap-override descriptors.
Now that we can count on ESM more, the story is shifting somewhat, and all of those things are being questioned. What if we didn’t have to npm install? What if we don’t need a bundler? What if performance is fine, between HTTP/2+, global CDNs, browsers doing fancy things, etc.? What if maybe we shouldn’t be compiling code so much because we’re down-compiling too much?
When we do that, we quell the insinuation that frontend developers were second-class developers who should at the first opportunity become backend or “full stack” or other types of developers. No: We would recognize frontend developers as first-class developers, and support them to get order into the chaos that “web development as a commodity” and “web development as software development” have caused.