All the can't-miss links.

Delivered straight to your email each week. Go Sign Up.

Add the feed to your favorite RSS reader and never miss a thing.

Sponsor a week and reach a large audience of designers and developers.

This week: Time Sliders, Weird CSS, and an AI Toggle

Learn Infrastructure as Code: Step-by-Step eBook

In this comprehensive ebook by Udemy Instructor Justin Mitchel, you'll learn how to use some of the most in-demand IaC tools – Terraform, Ansible, Puppet, and more. For each tool, you'll learn how to deploy a simple Docker-based Python web application from Github.

Build Fast. Scale Big. All in One Place.

Are you ready to take your app development to the next level? Simplify your development process with a fully managed backend infrastructure, auto scaling, and built-in security.

Start building your Web, Flutter & Mobile Apps with ease using Appwrite's Open Source Backend.

CSS Axolotl

Alvaro Montoro illustrates the internet's favorite aquatic amphibian with CSS in two styles. The classic, gills-out style here, and an animated version vibing with headphones.

Content Editable without JavaScript

DeyJordan demonstrates the contenteditable HTML attribute in this editable card demo. Click any of the text on the card to edit.

(waves & water) Miami

The words "Miami Beach Club" fill with gentle waves as they float into view in this beachy "CSS only text effect" from Fabricius Seifert.


Typography maestro Mike Mai sets Emily Dickinson's "Death is a Dialogue" in "superminimal" style with Goudy Bookletter 1911 and plenty of room to savor each line.

Selective Color Effect

Wakana Y.K. layers a pop of selected color on a desaturated image using canvas' drawImage method. Hover over an image to view it in full color.

Keep CSS Weird

Adam Argyle shares a CSS developers rallying cry while "animating the "MORF" axis of the Kablammo variable font" in this suitably weird Pen.

Creative Coding feat. P5.js, Perlin Noise & Randomness

Browse through a pleasingly purple collection of of P5.js examples from Monica Powell's RenderATL 2023 talk on generative art, randomness and noise.

Searching for Contacts Pure CSS Animation

Contact cards scroll in, get scrutinized with a magnifying glass, then disappear in this fun loading animation from Tucker Massad.

Arc Time Slider

Nicolas Jesenberger shares a slick design concept for a time picker. Check out the warm sunrise-sunset gradient!

SVG Displacement Image Mask Reveal

An image gradually emerges, then crumples away, in this animated displacementFilter demonstration from Fabio Ottaviani.

Jupiter in 3D with CSS trigonometry

Ana Tudor takes us to outer space with this visit to Jupiter built entirely with CSS. "Everything is computed. There are no magic numbers." Best enjoyed in Firefox.

AI Toggle

Make an AI-assisted "choice" in this interactive GSAP & SVG animation from Chris Gannon. Then check out Chris' growing "Bad AI" collection for more shenanigans from our artificial friends.

Chris' Corner

If I were going to argue against @scope, the new CSS feature, I might say that CSS already has scope. Like, every selector is “scope”. If you say .el, you’re saying “scope this bit of CSS to elements that have the class name of ‘el'”. But then someone might tell you, ok, but what about “donut scope” 🍩? Donut scope is a way for a scope to stop. Keith Grant shows that off in a recent article:

@scope (.card) to (.slot) {
  /* Scoped styles target only inside `.card` but not inside `.slot` */
  :scope {
    padding: 1rem;
    background-color: white;

  .title {
    font-size: 1.2rem;
    font-family: Georgia, serif;

Imagine that applied to this HTML:

<div class="card">
  <h3 class="title">Moon lander
  <div class="slot">
    <!-- scoped styles won’t target anything here! -->

I’m not sure how I feel about that, honestly. Don’t hate it, but also can’t think of a time when I really really wanted that. That might be because it’s never existed so my brain didn’t try to reach for it. But container queries didn’t exist before, either, and I think we all pined for those anyway. Still, it’s a bit of a +1 for @scope because it’s a thing we can’t do any other way.

If I was still arguing against @scope, then I’d say, well, it turns out actually you can replicate donut scope, thanks to another modern CSS feature, :has(), as Bramus blogged:

.from ~ :has(~ .to) {
  outline: 1px solid red;

And actually, you don’t even need that.

So I’m afraid I have to rescind the point I gave @scope. Are there any other tricks up its sleeve? It does have one! It’s called proximity. This is just kind of a bummer situation in CSS:

<div class="green">
  <p>I’m green</p>
  <div class="blue">
    <p>I’m blue</p>

If you wrote the CSS like this:

.blue p {
  color: blue;
.green p {
  color: green;

Then both paragraphs are green. Just because the green selector came second. That’s just how CSS selectors work. Both have the same specificity so the latter one wins. We can fix this with scopes:

@scope (.green) {
  p {
    color: green;

@scope (.blue) {
  p {
    color: blue;

Now that second paragraph is properly blue because the closer scope wins (and it doesn’t matter what order they are in). This is nice for color theming when you use classes to change the theme “higher up” in the DOM. But it doesn’t save you from increased specificity of other selectors, which are probably a more common “bug”. Still, I’ll say this is worth a +1!

Still, I’m not salivating for @scope. It doesn’t solve any big pain points that I’ve personally had. But maybe it does for you, the web is a big place, so all good.

I’ve said it before, but I think the super old-school idea of sticking a <style scoped> into the DOM anywhere and having those styles scoped to the parent is still a cool idea and actually does solve problems. Coupled with :scope { } it means I don’t even have to think of a name of how to select an element, yet still get the ability to apply pseudo-elements and the like. So inline styles with more abilities. And without having to name anything, there is no possible way for the styles to leak anywhere else. Sure, it’s neat to stop style leaking with a @scope too, but because I have to apply it to a class, I need to make a super obscurely named class like .card_987adf87d (a build tool concern) for it to actually worry-lessly “scope”.