Without the new property margin-trim, I’m forever doing :last-child { margin-block-end: 0; } and things like that to prevent an elements margin from combining with a parent elements padding to make too much space. The fact that we can avoid the extra awkward targeting and removal rule with this is great. I’ll stick by Coyier’s […]

Don't underestimate `shape()` — it's the CSS version of SVG that we absolutely needed.

Container units (e.g. cqi) are only able to reference the closest container. But if you register a custom property and set that higher up, you can get your hands on other containers units.

A rare fundamental change to browser default stylesheets: <h1> elements used to get smaller the more <section>s they were nested within, but no more. I would guess because the HTML Outlining Algorithm never really materialized.

A bit of a pivot from the Redwood gang, splitting RedwoodJS into Redwood GraphQL … To minimize disruption and provide clarity going forward, we’re renaming the existing RedwoodJS framework to Redwood GraphQL, reflecting its strength as a mature, stable framework built around GraphQL. … and the newfangled RedwoodSDK. Redwood has always been ultra opinionated (I […]

Kinda like that "bento box" look.

Matt Smith on when to use map() vs. forEach() in JavaScript. Just one of those things I can imagine asking or being asked in a coding interview. Some interesting comments below the article as well.

Is there a perfectly clear and reasonable answer? Or could we get this someday?

It's not particularly obvious, but a child's useEffect will run before a parent's will. Let's look at why.