Edition: 2026-06-29

Daily Digest - 2026-06-29

Total articles in digest: 7

Must Read

CSS has always had pseudo-classes that style things when baed on user interactions.

Why it's relevant: matches terms: javascript; fits Design category
Summary:
- Rather, CSS is accumulating more and more pseudo-classes to help us respond to JavaScript events so that we don’t have to do so with JavaScript itself.
- But while pseudo-classes track states, not events, they sure can feel like event listeners sometimes (not that it really matters in the context of CSS).
- For example, there’s a proposal for event-trigger in the Animation Triggers spec, which would basically listen for events and trigger animations.

AWS Morning Brief for the week of June 29th, with Corey Quinn.

Why it's relevant: matches terms: aws, cloud, lambda; fits IT category
Summary:
- The latest in AWS news, sprinkled with snark.
- Posts about AWS come out over sixty times a day.
- We filter through it all to find the hidden gems, the community contributions--the stuff worth hearing about!

With the progress() function in CSS we've got a new way to calculate the size for type based on the viewport without problems of the past.

Why it's relevant: matches terms: css; fits Dev category
Summary:
- Never do pixel math with em and rem units.
- That’s where we went wrong, by assuming that 16px == 1em is a reliable fact.
- Miriam Suzanne, Reimagining Fluid Typography Fluid typography has been around for a while.

I was a guest on James 's Wonders of Web Weaving podcast and it was such a lovely conversation.

Why it's relevant: matches terms: web; fits Dev category
Summary:
- I was a guest on James's Wonders of Web Weaving podcast and it was such a lovely conversation.
- We talked about old teenage blogs, how I found the IndieWeb community, why I think now is the best time to be your full weird self online, and I accidentally held myself publicly accountable for a side project.
- This was also my first podcast ever, so I was a little bit nervous at the start.

Hey friends!

Why it's relevant: matches terms: web; fits Developers category
Summary:
- 🍫 "Great success doesn't come in short periods of time." - J.B.
- Mine felt good, I was able to get some creative juices flowing on projects and cleaned my office, which was very necessary.
- Web links of the week Text stickers Astro 7.0 Modern CSS theming with light-dark(), contrast-color(), and style queries Wiggly/Wavy Input Range Slider Something that interested me this week This week was fun.

Recording all the "terms and conditions" I claimed to have read on a computer or phone for 10 years.

Why it's relevant: fits Design category
Summary:
- I recorded all the "terms and conditions"1 that I've had to click "agree" to or otherwise claim to have read on a computer or phone for 10 years (starting April 21st 2016 and ending April 21st 2026).
- See the terms and conditions here (page may take several seconds to load) I started doing this because Ts and Cs feel like an aspect of modern life that doesn't work as it's meant to but which we ignore because the workaround is fine and doesn't cause too many problems.
- Most people regularly make the claim once every few days to have read and understood something they haven't read or understood, and that's probably fine.

We seem to be stuck on a new hurdle: the idea that websites need to function the same everywhere.

Why it's relevant: fits Design category
Summary:
- ~ Early 2000s’ Pixel Perfection If you, like me, were building websites back in the early 2000s, you’ll undoubtedly remember the absolute headache that was cross-browser compatibility.
- What didn’t help back then in this era of Internet Explorer, Netscape, and Firefox was the stubborn, widespread belief that websites needed to look exactly the same in every single browser.
- Pixel perfection was the (flawed) holy grail.