Okay, so I learned a thing about Grids today. Many of my components have these declarations to make spacing nice: `display: grid; gap: 2rem`. Apparently, `grid-template-columns` is now implicitly set to `auto`. Yada yada, 2018 @chriscoyier.net has my back! css-tricks.com/preventing-a...

Triggered by @patrickbrosset.com's talk at #CSSDay: Progressively enhanced data-dense layout with grid-lanes www.projectwallace.com/blog/using-g... Or, less keyword-heavy: how grid-lanes can be used for data-dense layouts and not just for fun/newspaper-like stuff for browsers that support it.

If you want to see if @matuzo.at's actual css layer architecture is exactly as advertised on #cssday, check out www.projectwallace.com/css-layers-v...

This article was also an opportunity to pay tribute to @donnie.damato.design, @projectwallace.com, @evilmartians.com, @samiamdesigns.bsky.social, @clearleft.com, @danmall.bsky.social and of course @designtokens.org 🫶 Let me know what you think ✌️

Dogfooding the Wallace stylelint plugin on an upcoming new page on the website. There's so much to improve: more granular error ranges, better error messaging, subtle bugs to fix. But it'll be good!

A sudden spark of inspiration yesterday and now we're waiting for the printing company to deliver these bad boys.

Few things give me more stress than some breaking changes just before a public release. Anyway, stylelint plugin is now 0.5.0 🥲

😇 Almost ready to publish my new stylelint plugin! It'll ship with ~70 rules (for now) and comes with presets for correctness, performance, design tokens and maintainability. Some of my favorite rules 👇

🥳 500 followers celebration time

Go fill the survey! Not just because you can confirm ✅ that you're using Project Wallace, but the output usually influences some of the decisions I make around CSS analysis!

Make that 3 mentions in 2 weeks! 🤪

somehow I missed this awesome report about CSS usage from @projectwallace.com Definitely worth checking out! www.projectwallace.com/the-css-sele...

Two mentions from @syntax.fm in one week! You guyssss... ✌️ Episode 999 is all about writing maintainable CSS. You _bet_ Project Wallace is your Swiss army knife for that!

Sounds like the @syntax.fm team are ready for a next step from Wallace! (see: syntax.fm/show/998/how...) Well, good news: I'm finishing up the stylelint plugin pack I've been working on for a long time. If you want a sneak peek: github.com/projectwalla...

Removed all twitter links from @projectwallace.com blog! Finally. Did a round previously removing them from all other places, but 8 years of blog took a bit more effort. Linking to people's personal sites now, cuz websites are cool

Some people get mad when we shout at you for having to many declarations in one rule, but what if you'd just organize it in more layers? 😇 www.projectwallace.com/css-layers-v...

"Your CSS has dirty secrets and Wallace knows them." is just a title that hits. Immediate guilt and fear flow through your veins. "Does it know about... the floats?", you ask yourself. Ha, who are you kidding, of course it does. And that tiny 8px font-size. Thought you'd get away with that, did ya?

Tried some wildly different fonts but I think Teko is just the best reflection of my border-radius:0 design. Added 2 gradients to the header at a late stage, quite like them. Added a lot more spacing to the homepage, but made the forms to submit URL a bunch smaller.

2 improvements shipped today! - denser analysis view (if you're on Firefox, or you have experimental grid-lanes enabled in chromium) - analyze custom element selectors, like details-utils, is-land, pagefind-search, etc. etc. (h/t @bkardell.com for the idea!)

Over 10,000 views so far and traffic is only slowly declining. One of the best things I've ever made and it's only going to be better next year!

Did they have an entire novel in there?!

Come read the biggest-ever article we've ever done!

align-content: home-stretch! Working on the last few bits so this beast can be released on Friday! 🫶🫶 Shoutout to @polypane.app for making this first edition possible. Imagine having incorporated several links to Polypane in the content already, and then @kilianvalkhof.com stepping up. 🫶🫶

Did you know @projectwallace.com has a CSS Complexity calculator? It's a fun complement to CSS Specificity. It doesn't measure the impact a selector has but the number of parts that it has. more parts: harder to understand for humans. www.projectwallace.com/selector-com...

We're progressing! Hoping to launch The CSS Selection later this week, maybe before the weekend if all goes well. Also hoping that the estimated reading time of 45-60 minutes won't scare people too much 😅

Making a very long checklist of what needs to go in before this goes live. Most content writing is done now. Need a lot of accessibility checking to make sure charts and tables work. Then making raw data available for download. Social images, maybe baseline data. The lot!

More CSS analysis more better!

First metrics are in! 21,000+ websites analyzed. The `max` column is absolutely bonkers. Plaintext table of attached screenshot here: gist.github.com/bartveneman/...

The dust of decades settles on your keyboard as you push aside lines of vendor prefixes Your fedora casts shadows over cryptic CSS hacks from another era. "This belongs in a museum" you mutter ReliCSS: The front-end archaeologist's tool for navigating legacy CSS www.alwaystwisted.com/relicss/ 🙏🖤

Do you ever use or look at the browserhacks analysis that we provide? Old IE hacks like `*zoom: 1`, or others like old Webkit stuff `.selector:not(*:root) {}`, etc. etc. Considering removing it from our analysis to speed it up and reduce bundle size.

How to calculate CSS code coverage with @playwright/test 🎭 www.projectwallace.com/blog/how-to-...

BIG shoutout to @netlify.com to allow projectwallace.com to run on an Open Source sponsered plan. This allows me to keep shipping many updates for free to everyone to use 🫶

How to calculate CSS code coverage with @playwright.dev www.projectwallace.com/blog/how-to-...

It looks like the folks at cssstats.com did a massive overhaul. Lots more stats, comparing websites and saving snapshots, for free! 😱 It looks like it's still early days because I've encountered many issues but they've taken a giant leap.

If you really hate looking at unused custom properties, maybe clean them up? 😇 I know looking at unused custom properties not applied in devtools is not the same as potentially flawed static analysis on a large chunk of CSS, but hey...

Open sourcing css-code-coverage github.com/projectwalla... It is *very* early stages, it needs a ton more tests, docs, cli tool etc. but is for the folks who want an early look.

We're experiencing some DNS issues while we're moving away from Vercel. Please hang on tight. Fingers crossed that analyzing your CSS isn't the most important thing you were going to do today 🤞

Thinking of cooking up something to compare sets of CSS. Most likely for before/after sort of stuff, but perhaps other use cases too. Visualisation of that will be tough, I guess. Rendering stats for a single site easily ends up with thousands of DOM nodes. Would you use it?

Gave the ol' CMD+K menu a fresh lick of paint and added a search bar. Much more useful this way 😍

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)

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

How to create a Naked CSS theme without removing CSS www.projectwallace.com/blog/how-to-...

🥵

enjoying all the recent (or not so recent) updates to @projectwallace.com's (free) CSS analyser page, including a dedicated 'design tokens' section, like this – www.projectwallace.com/design-token... lovely stuff @veneman.dev 🙏 🖤

🧛 Anyone up for counting the depth of your CSS nesting? Could be interesting to spot deeply nested and hard to debug rulesets, declarations, etc.

🆕 Spacing reset analysis Sparked by @ohhelloana.blog's enthusiasm, this turned out to be a relatively simple feature! 🥳 A few gotchas: - a gazillion ways to write 0 (scientific notation, floats, signed numbers) - many spacing-related properties, potentially vendor prefixed (although unlikely)

#CSSDay was a blast and the first act of applying quick wins was improving scrollbar styling after watching @nerdy.dev's talk. Still recovering from the energy.

At #cssday where @miriam.codes is speaking truths

🌟 Release notes April & May www.projectwallace.com/blog/april-m... ☀️ NEW Light theme 🍑 NEW CSS Naked theme ⚖️ NEW Website Analytics 🛠️ Added new devtools to several pages

🆕 Container names. Because we all sometimes forget to name a thing, or forget that we named it and never used it 😇