In Fixing the URL params performance penalty, Barry Pollard sets up a very clear real-world conundrum. The content at these two URLs is probably the same: The content at these two URLs is probably not: Who cares? Cache cares. Because content with different query params might be different, the various tech that deals with caching […]

Alex and Chris talk about how the 2.0 Editor supports packages from npm. The trick is both simple and complex. The idea is simple. We detect the packages you want to use, list them in an (editable) package.json file, then turn that into a <script type=”importmap”> in your HTML files that import those packages from […]

I’ve always loved a good blog post of someone just saying what they use and do. Keerthana Krishnan has a good one here with Chrome DevTools Features I Use All the Time (and Why You Should Too). Cheeky parentheticals, Keerthana. Like, sure, I’ll read a blog post about new Chrome DevTools features, but I’m more […]

Stephen & Chris look at the UI of the 2.0 Editor and show all the control you have over what you’re looking at. Way more control than the Classic editor! We share some of the thinking behind it. Don’t miss the Omnibar! Time Jumps Links

Perfectionist? So how can you tell when your perfectionist traits, which in many ways have aided your creative prowess, have gone too far? If you’re prone to obsession, especially when it comes to work, there’s always a way to justify why it’s worth the agony. But, as Siqi, renald and Pablo attest, getting bogged down […]

It’s always interesting observing multiple people attack the same problem. Sometimes they aren’t even aware of each other. Like how Isaac Newton invented calculus in the mid 1660’s in England, then Gottfried Leibniz did the same a decade or so later, independently (or so it is said). I just read Ibrahim Bendebka’s recent take on […]

The other week when I was talking about Web Components in the Corner, I mentioned zero-md, a nice little Web Component for doing exactly that. I had to bite my tongue a little bit though, as the 2.0 public beta hadn’t quite made it out of the door yet. See, the new compiler, among its many […]

With CodePen 2.0, we’ve got a new word we’re using: Blocks. A way to think about Blocks is anything that processes code. They are added as steps to the CodePen Compiler as needed. For example, TypeScript is a block, because it processes files in the TypeScript syntax into JavaScript files. But something like Lodash is […]

As of January, with Firefox 147’s release, Anchor Positioning is supported across all major browsers. I’m happy about that, of course. I think Anchor Positioning is really powerful and a layout mechanism we probably should have had a long time ago. My enthusiasm was tempered when I found out how finicky it can, simply not […]

CodePen 2.0 was the most ambitious project that we’ve ever taken on in our lives. Why would we do such a thing? Chris and Alex explain the thinking behind it. We’ve been around a long time, know what our customers want, and are developers ourselves, so we know how this industry moves. We thought we […]