❌ 1. anonymous website moved to @netlify.com but I messed up DNS it seems. ⏳ 2. veneman.dev is transferring out DNS but already successfully deploying on Netlify ⏳ 3. projectwallace.com also deploying successfully on Netlify but I'll wait with the DNS stuff until 2. has resolved

Can't wait for this work day to be over so I can start moving domains and websites. Gah!

This was a good reminder for me that I'm still paying the triangle squad for the hosting of @projectwallace.com. I've had plans to move away for a long time bur had forgotten about it. Anyway, expect some downtime this week as I'm moving over.

I think.... I did it....? A tiny Playwright fixture that collects CSSCoverage reporting and writes the JSON to disk. Then grab the (apparently) 157 JSON files (7.2MB) and put them in the CSS Coverage analyzer. A bit slow, but it's not even running in a WebWorker yet...

This panel is infinitely more useful after this update. Use it a ton because it's so intuitive. No idea why I stuck with the previous one for so long.

... and if I were to ask you "Who would you like to see speak at CSS Day 2026", what would your answer be? Name as many names as you like. I'd like to hear about people who aren't that well known yet.

Does anyone automate their periodic updates? Thinking of writing a small script to do monthly updates for node, npm, brew, reboot security cams, etc. etc.

Analysis for the @httparchive.org Almanac CSS chapter is underway!! I had a sneak peek at the first query results and charts and I'm confident that this is going to be a fun edition because we get to compare 6 years of CSS data 🤩

Ugh, really, really tempted to start a CSSTree-like project to have more control over some cases that I want for Wallace but writing a new parser from scratch isn't fun. Maybe a job for AI. Would like to contribute to csstree but I get lost on every attempt.

I wish CSS Highlights would let me add borders or outlines. It's a perfect application for highlighting (partial) search results.

Last night I updated my personal @11ty.dev website from version 0.11 to v3 in less than 20 minutes. One of the most pleasant major upgrades I've done in a long while.

I've been writing CSS analyzers for (... checks notes ...) 13 years and CSS overflow shit will never not mess me up.

With these compromised packages flying all over the place I'm so happy that all my CI setups include `--ignore-scripts` durng NPM installs. Not bullet proof but surely a great way to beat the most common type of issue.

Documented all of the tokens of my most recent package. A ton of work but hopefully useful if anyone feels the urge to create design tokens out of their CSS github.com/projectwalla...

TIL you can expand the Typescript type hint popup to show what is inside the types by clicking on that tiny `+` in the bottom left. Previously I'd always option+click on that type to go to definition and lose my tracks.

TIL you can set `indeterminate={true}` on a checkbox in @svelte.dev and it just works!

Another unmaintained (!!) dependency removed 🥳

Wallace's website isn't heavy on dependencies but I managed to replace 2 of them with a single utility function. 27 lines of well-tested code, tailored to my specific needs, 325 bytes (unzipped) vs. 2 dependencies to update monthly, totalling 5.7 kB

Currently 31.5 hours without internet without noteworthy updates from the provider. Guess who's going to contact their competitor once it's back up.

Full working day without internet at home so far and mobile bundle depleted. How's your Monday going?

Starting to explore Web Components. Does anyone have recommendations for learning resources or interesting blog posts? Also looking for best practices around managing state, emitting events (or not?), or do you pub-sub?

Doing a very similar trick on the CSS Coverage inspector: create an array of start/stop elements to render an entire range instead of a single DOM node per line. ❌ DOM size before: 3145 nodes ✅ DOM size after: 686 nodes (But gains depend on CSS size & patchiness of coverage of the selected file)

gradient.style has finally - come out of beta - offers multiple background editing - is open source 🎉 nerdy.dev/gradient.sty...

is it time to bring back the grunge yet?

Would be nice to have a CSS selector to target all or subset of highlights. Now I have to search for all the custom highlights in one file, paste it in my component styles and try to not forget about about updating it when one of them changes. gist.github.com/bartveneman/...

Found 2 interesting issues related to CSS Highlights: 1. Chrome and Edge do not `inherit` color 2. Firefox only updates the color after a forced paint/layout (whatever resizing the browser triggers) repro: codepen.io/bartveneman/...

WOW! Seeing massive performance gains when using requestIdleCallback() to clean up custom `CSS.Highlight`. Before: 500ms+ After: <1ms This is great because this cleanup would block the UI before moving on. Now the operation feels instant!

Reducing 10,000+ DOM nodes when rendering large reports on @projectwallace.com Previously I'd render a `<li>` for *every* line of code that would show up in the inspector panel. Now it's a *single* `div` with all the line numbers as text content with `whites-space: pre`.

Sorry to bother but @nerdy.dev or @bram.us do you have an idea if this is possible at all?

I'm stumped! How do I create this layout where the gutter with line numbers and the code scroll vertically together and the code scrolls horizontally with the line numbers still visible? Is it even possible without JS and/or shadow copies of the <pre> block?

A tiny little class I keep using across various projects: check if a potentially wEiRdLy cased string is in a set of keywords. Since most of CSS doesn't care about casing (🤬 NaN) I can yeet any user generated CSS property in here it'll check against my base set.

I appreciate all 18 of you! +1 rank gained is still a plus in my book. 2025.stateofcss.com/en-US/other-...

Honey, wake up, new speeding up the javascript ecosystem just dropped!

Some digging in Wallace's error logs and Sentry. So many devs trying to analyze `localhost`. I guess I'll need to add some custom error handling to tell them that it won't work...

Do I continue... ?

@laurieontech.dev hey, I just noticed a lot of new entries in your RSS feed! 🥳 Unfortunately all entries only show a summary and the 'visit website/read more' links all go to example.com 🥹

Today is a good day for another attempt to play with concepts of data oriented design.

Thinking of brightening up my home office with a custom LED sign, anyone got recommendations on where to order and do's and don'ts?

Doing some quick performance wins on @projectwallace.com: - wrap border radii in a 'show more' component that renders the first 15 items at first - same for colors-per-property - remove the double list of unique colors, just one is good enough - because of ☝️ removed a ton of intersection observers

Quick, everyone, @codepen.io Radio is back! 🥳

Debugging an issue with prefers-contrast: more, custom properties and cascade layers and I don't know how anyone would do that without project wallace. Not even mad, I just don't know how you get shit done.

Documented @projectwallace.com's CSS Scraper bot www.projectwallace.com/docs/css-scr... Haven't had anyone complain or ask yet but saw a similar page recently because I spotted an unusual user agent in the logs and felt like this is a good thing to do.

Hey @keithamus.social, do you think that in the future csskit may be a good choice to power some/most of the tooling on @projectwallace.com? I think there is some overlap in goals. Curious for your thoughts 😄

☀️ June 2025 release notes ☀️ 🔹 5 *new* features 🔹 20 production releases 🔹 3 bug fixes 🔹 4,200+ visitors / 8,300+ page views www.projectwallace.com/blog/june-20...

Writing another monthly Wallace roundup tonight. What's something you want to know?

Ah, so the design token spec had an update back in April and so my Design Tokens page has been incorrect for about two months and I need to figure out a way to support the new Color type 😐

My wife is watching Squid Games and it looks like a messed up, less fun version of Taskmaster.

Another new feature coming from the almanac outline, thanks to Chris Lilley: analyzing which color spaces a website uses. But how do we group color spaces? colorjs.io gives a whole tree (colorjs.io/docs/spaces) so which level do I pick to group by?

Lol, I actually found a bug at work because it showed me 1 entry being nested 3 levels deep which turned out to be a media query inside a media query. That one was hard to spot in the source code even when we knew it was there!

Still a week left to take the State of CSS survey! The survey hasn't got as many responses as last year, so any help sharing will be much appreciated :) survey.devographics.com/en-US/survey...