Project Wallace @projectwallace.com · 18/09/2026or, instead of writing valuable content, let me just release another shitty webpage with CSS tools 010
Project Wallace @projectwallace.com · 14/09/2026🍾 NEW: Baseline overview Quickly scan the Baseline status of your website's CSS! 🩻 www.projectwallace.com/baseline-ove... 0286
Reposted by Project WallaceBart Veneman @veneman.dev · 06/09/2026Still some ways to go, but this is turning out useful. 3121
Project Wallace @projectwallace.com · 04/09/2026Never publicly posted anything, but our linter page is already in the top-10 of visited pages 🥰 120
Reposted by Project WallaceBart Veneman @veneman.dev · 31/08/2026Pushed two big performance wins on projectwallace.com yesterday. Next up: attempting to virtualize syntax highlighting with the Highlight API additional elements for lines etc. 🤞projectwallace.comCSS Analytics - Project WallaceThe best CSS Analyzer on the web. Check your CSS complexity, specificity, performance, design tokens and much more. 1205
Reposted by Project WallaceBart Veneman @veneman.dev · 19/08/2026Mixing web-features with wallace's CSS analysis and you get... a new tool for CSS archeologists! h/t @patrickbrosset.com for pointing me to github.com/web-platform... 193
Project Wallace @projectwallace.com · 07/08/2026Update color-sorter and css-design-tokens packages to replace colorjs with colordx to increase performance and decrease install size. 12MB had always been too much, but no longer! 010
Project Wallace @projectwallace.com · 03/07/2026Ooooh, it looks like some of you have found the new linter page on our website already. Let me know what you think! 000
Project Wallace @projectwallace.com · 02/07/2026Our marketing team is on summer holiday, but luckily the @syntax.fm crew are filling in! youtube.com/shorts/tYvXx...youtube.comYour dirty CSS secretsYouTube video by Syntax 021
Project Wallace @projectwallace.com · 27/06/2026Merged a big one today! 42 commits on a PR open since the end of March 😱 110
Reposted by Project WallaceBramus @bram.us · 22/06/2026Reminder: The State of CSS Survey is closing *SOON*, so **NOW** is the moment to complete it. stateofcss.com/en-US/ This survey directly influences efforts like Interop and feature planning, so this is **YOUR** moment to let browser vendors know what you find missing on the web! 1159
Reposted by Project WallaceBart Veneman @veneman.dev · 18/06/2026A couple of months ago @ohhelloana.blog was complaining about the lack of choice in women's wear in developer clothing. I agree. Made this. My wife wears it now and it's *really* nice. 193
Project Wallace @projectwallace.com · 14/06/2026Okay, 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...css-tricks.comPreventing a Grid Blowout | CSS-TricksSay you have a very simple CSS grid layout with one column fixed at 300px and another taking up the rest of the space at 1fr. 131
Project Wallace @projectwallace.com · 13/06/2026Triggered 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. 133
Project Wallace @projectwallace.com · 12/06/2026If 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... 182
Reposted by Project WallaceLouis Chenais @lucho.cool · 11/06/2026This 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 ✌️ 252
Project Wallace @projectwallace.com · 08/06/2026Dogfooding 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! 021
Project Wallace @projectwallace.com · 08/06/2026A sudden spark of inspiration yesterday and now we're waiting for the printing company to deliver these bad boys. 051
Project Wallace @projectwallace.com · 26/05/2026Few things give me more stress than some breaking changes just before a public release. Anyway, stylelint plugin is now 0.5.0 🥲 030
Project Wallace @projectwallace.com · 22/05/2026😇 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 👇 131
Project Wallace @projectwallace.com · 19/05/2026Go 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! 020
Reposted by Project WallaceBart Veneman @veneman.dev · 07/05/2026Make that 3 mentions in 2 weeks! 🤪 161
Reposted by Project WallaceSacha Greif @sachagreif.com · 28/04/2026somehow I missed this awesome report about CSS usage from @projectwallace.com Definitely worth checking out! www.projectwallace.com/the-css-sele...projectwallace.comThe CSS Selection - 2026 Edition - Project WallaceThe CSS Selection shows real-world CSS usage from over 100,000 websites and looks at the most important metrics. 0144
Project Wallace @projectwallace.com · 27/04/2026Two 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! 171
Project Wallace @projectwallace.com · 23/04/2026Sounds 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...syntax.fmHow to Fix Vibe Coding - Syntax #998 141
Reposted by Project WallaceBart Veneman @veneman.dev · 27/03/2026Removed 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 091
Project Wallace @projectwallace.com · 24/03/2026Some 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... 052
Project Wallace @projectwallace.com · 01/03/2026"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? 010
Reposted by Project WallaceBart Veneman @veneman.dev · 01/03/2026Tried 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. 171
Project Wallace @projectwallace.com · 27/02/20262 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!) 021
Project Wallace @projectwallace.com · 20/02/2026Over 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! 020
Reposted by Project WallaceKevin Powell @kevinpowell.co · 13/02/2026Did they have an entire novel in there?! 3141
Project Wallace @projectwallace.com · 06/02/2026Come read the biggest-ever article we've ever done! 031
Reposted by Project WallaceBart Veneman @veneman.dev · 04/02/2026align-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. 🫶🫶 083
Reposted by Project WallaceKilian Valkhof @kilianvalkhof.com · 03/02/2026Did 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...projectwallace.comCSS Selector Complexity Calculator - Project WallaceQuickly calculate the complexity of your selectors, including :where(), :has(), :is() and friends! 061
Project Wallace @projectwallace.com · 01/02/2026We'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 😅 000
Project Wallace @projectwallace.com · 30/01/2026Making 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! 020
Reposted by Project WallaceBart Veneman @veneman.dev · 07/01/2026First metrics are in! 21,000+ websites analyzed. The `max` column is absolutely bonkers. Plaintext table of attached screenshot here: gist.github.com/bartveneman/... 3101
Reposted by Project WallaceStuart Robson @sturobson.com · 04/01/2026The 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/ 🙏🖤alwaystwisted.comReliCSS - Web Interface 34517
Project Wallace @projectwallace.com · 02/01/2026Do 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. 110
Project Wallace @projectwallace.com · 09/12/2025How to calculate CSS code coverage with @playwright/test 🎭 www.projectwallace.com/blog/how-to-...projectwallace.comHow to calculate CSS code coverage with @playwright/test - Blog - Project WallaceCollect and analyze CSS coverage using Playwright tests to detect and prevent unused CSS in production. 000
Project Wallace @projectwallace.com · 07/11/2025BIG 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 🫶media.tenor.coma man with long hair and a beard is smiling and saying thank you .Alt: a man with long hair and a beard is smiling and saying thank you . 070
Reposted by Project WallaceBart Veneman @veneman.dev · 31/10/2025How to calculate CSS code coverage with @playwright.dev www.projectwallace.com/blog/how-to-... 3104
Project Wallace @projectwallace.com · 23/10/2025It 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. 040
Project Wallace @projectwallace.com · 21/10/2025If 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... 010
Reposted by Project WallaceBart Veneman @veneman.dev · 12/10/2025Open 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.github.comGitHub - projectwallace/css-code-coverage: Generate useful CSS Code Coverage report from browser-reported coverageGenerate useful CSS Code Coverage report from browser-reported coverage - projectwallace/css-code-coverage 032