Sign in

Project Wallace

@projectwallace.com
514 followers 73 following 117 posts

CSS analyzers that checks your complexity, specificity, performance, Design Tokens, custom properties and much more. Webmaster: @veneman.dev 🔖 projectwallace.com

PostsRepliesMedia
Project Wallace @projectwallace.com · 18/09/2026
Yeah, just look at the top keyframes names here www.projectwallace.com/the-css-sele...
projectwallace.com
The CSS Selection - 2026 Edition - Project Wallace
The CSS Selection shows real-world CSS usage from over 100,000 websites and looks at the most important metrics.
120
Project Wallace @projectwallace.com · 18/09/2026
From what I remember why doing analysis: spinners. Spinners everywhere.
120
Project Wallace @projectwallace.com · 18/09/2026
or, instead of writing valuable content, let me just release another shitty webpage with CSS tools
010
Project Wallace @projectwallace.com · 17/09/2026
I'll pop it in for next year, now I'm curious too and I think of % as a unit myself anyway.
020
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...
A portion of a page from project wallace. It shows three panels, two on the top, one at the bottom. The top left panel is titled "Baseline status summary" and shows a table and graph showing that 26 feaures are widely available, 2 newly available and 5 limited available. The top right panel is titled "Widely available features by year" and shows a table with all years since 2018 and each year has a bar graph of how many features of that year are used. The bottom panel shows a huge table with each used feature, the amount of usage, the dates fro when it became newly available, widely available, often a link to caniuse.com, and finally a column that indicates browser support for Edge, Chrome, Firefox and Safari.
0286
Reposted by Project Wallace
Bart Veneman @veneman.dev · 06/09/2026
Still some ways to go, but this is turning out useful.
A portion of a page from project wallace. It shows three panels, two on the top, one at the bottom. The top left panel is titled "Baseline status summary" and shows a table and graph showing that 105 feaures are widely available, 3 newly available and 12 limited available. The top right panel is titled "Widely available features by year" and shows a table with all years since 2018 and each year has a bar graph of how many features of that year are used. The bottom panel shows a huge table with each used feature, the amount of usage, the dates fro when it became newly available, widely available and a column for browser support with colorful browser icons.
3121
Project Wallace @projectwallace.com · 04/09/2026
the css-code-quality page is also dropping in popularity, which is pretty nice because I've never liked the page, nor the package behind it.
010
Project Wallace @projectwallace.com · 04/09/2026
looks like it's time to put my blogging cap on a write a bunch about the new stylelint-plugin that I'm hoping to make v1.0.0 soon.
110
Project Wallace @projectwallace.com · 04/09/2026
Never publicly posted anything, but our linter page is already in the top-10 of visited pages 🥰
120
Reposted by Project Wallace
Bart Veneman @veneman.dev · 31/08/2026
Pushed 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.com
CSS Analytics - Project Wallace
The best CSS Analyzer on the web. Check your CSS complexity, specificity, performance, design tokens and much more.
1205
Reposted by Project Wallace
Bart Veneman @veneman.dev · 19/08/2026
Mixing 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...
A bar chart titles "Widely available, by year". There are 12 columns for the years 2018 through 2026 and "not yet widely", "not baseline" and "untracked". The bars for these last three are grayed out.

Values per item: 

2018: 3560
2019: 1818
2020: 107
2021: 9
2022: 182
2023: 222
2024: 120
2025: 58
2026: 10
not yet widely: 8
not baseline: 49
untracked: 671
193
Reposted by Project Wallace
Bart Veneman @veneman.dev · 16/08/2026
Ahwyeeaaah :sexy-dance.gif:
Project Wallace stylelint overview. There are three errors. 1 is for an `if()` that contains only an `else` branch. 2 is for an `if()` without  an `else`. 3 is for an `else` that isn't the last condition in the `if()`.
021
Project Wallace @projectwallace.com · 07/08/2026
Update 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!
npmx.dev's view of the `@projectwallace/css-design-tokens` package. It shows a bright green/positive banner saying "Package size decreased since v0.11.8!🎉 Install size reduced by 93% (15.8 MB smaller)"
010
Project Wallace @projectwallace.com · 27/07/2026
🧢😎
A small boy seen from the back, from the shoulders up. He is wearing a black baseball cap, backwards. It has the classic Project Wallace "Chaotic Style Sheets" print on it.
011
Project Wallace @projectwallace.com · 03/07/2026
Ooooh, 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/2026
Our marketing team is on summer holiday, but luckily the @syntax.fm crew are filling in! youtube.com/shorts/tYvXx...
youtube.com
Your dirty CSS secrets
YouTube video by Syntax
021
Project Wallace @projectwallace.com · 27/06/2026
Related: the Stylelint plugin is coming along great. Many small fixes in wording error messages, locating the correct ranges etc. I think we're close to v1 now.
020
Project Wallace @projectwallace.com · 27/06/2026
Merged a big one today! 42 commits on a PR open since the end of March 😱
110
Reposted by Project Wallace
Bramus @bram.us · 22/06/2026
Reminder: 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!
Promotional Image for the State of CSS Survey 2026
1159
Reposted by Project Wallace
Bart Veneman @veneman.dev · 18/06/2026
A 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.
A woman sitting on a bench, seen from the back. She is wearing a black shirt with a large print. The print is 3 lines of big, bold text saying "chaotic style sheets". On top of that a graffiti-lime text in bright pink is shown, saying "project wallace".
193
Project Wallace @projectwallace.com · 14/06/2026
Defensive CSS also has a chapter on this defensivecss.dev/tip/grid-min... Turns out the stylelint plugin for that doesn't have a rule for that. Yet. github.com/yuschick/sty...
defensivecss.dev
Defensive CSS - Minimum Content Size In CSS grid
Practical CSS and design tips that helps in building future-proof user interfaces.
030
Project Wallace @projectwallace.com · 14/06/2026
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...
css-tricks.com
Preventing a Grid Blowout | CSS-Tricks
Say 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/2026
Apart from that I'm going to run a Playwright overflow test on every page. Already present on some interactive pages, but *apparently* I need to give myself more training wheels.
000
Project Wallace @projectwallace.com · 13/06/2026
omg 🥲
100
Project Wallace @projectwallace.com · 13/06/2026
Wow, hadn't noticed the massive horizontal overflow. @polypane.app would have caught this. I don't even... I'm so disappointed in myself right now.
110
Project Wallace @projectwallace.com · 13/06/2026
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.
133
Project Wallace @projectwallace.com · 12/06/2026
It was a nice test case to iron out some bugs as well.
000
Project Wallace @projectwallace.com · 12/06/2026
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...
A list of css cascade layers. At the top level we see layers named core, third-party, components and utility. Most of the layers also have sub-layers.
182
Reposted by Project Wallace
Louis Chenais @lucho.cool · 11/06/2026
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 ✌️
252
Project Wallace @projectwallace.com · 11/06/2026
Wow, that's quite a list to be mentioned in... 🥰
100
Project Wallace @projectwallace.com · 08/06/2026
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!
webpage with 3 columns. first column is really narrow and has radio buttons for presets: recommended, meintainability, performance and correctness. Second column shows a bunch of CSS with lots of red squiggly lines, indicating errors. Third column shows a table of all errors found and one row selected.
021
Project Wallace @projectwallace.com · 08/06/2026
A sudden spark of inspiration yesterday and now we're waiting for the printing company to deliver these bad boys.
Black t-shirt with small print of 10cm by 10cm on the chest. The print is in bold white font, saying "Chaotic Style Sheets". Over top of that a text in bright green graffiti text "Project Wallace".Black t-shirt with big print of 30cm by 30cm on the back. The print is in bold white font, saying "Chaotic Style Sheets". Over top of that a text in bright green graffiti text "Project Wallace".Black t-shirt with small print of 10cm by 10cm on the chest. The print is in bold white font, saying "Chaotic Style Sheets". Over top of that a text in bright pink graffiti text "Project Wallace".Black t-shirt with big print of 30cm by 30cm on the back. The print is in bold white font, saying "Chaotic Style Sheets". Over top of that a text in bright pink graffiti text "Project Wallace".
051
Project Wallace @projectwallace.com · 26/05/2026
Few 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
It all seems a bit much sometimes but, trust me, I've seen things, and you want all these rules in your toolbox. Or not. I'm not your boss.
010
Project Wallace @projectwallace.com · 22/05/2026
🚫 no-duplicate-data-urls ⚠️ max-embedded-content-size (don't let them data urls get away from you) ⚠️ max-comment-size / max-comments 🚫 no-useless-custom-property-assignment
110
Project Wallace @projectwallace.com · 22/05/2026
🎨 max-unique-colors/font-sizes/families/shadows/etc. ⚠️ max-lines-of-code (overall guard rail) ⚠️ max-selector-complexity (specificity is only part of story) ⚠️ max-spacing-resets (because @ohhelloana.blog a.blog is right and you shouldn't use excessive resets) 🌶️ no-property-shorthand 😈
120
Project Wallace @projectwallace.com · 22/05/2026
🚫 no-static-media/container-query => prevent `@media (width: 100px)` instead of `min-width` 🚫 no-unused-layers/custom-props/containers => once you define it, you should use it 🚫 no-atrule/property/value/selector-browserhacks (because @sturobson.com taught us well)
110
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 · 22/05/2026
🥳 500 followers celebration time
010
Project Wallace @projectwallace.com · 19/05/2026
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!
020
Reposted by Project Wallace
Bart Veneman @veneman.dev · 07/05/2026
Make that 3 mentions in 2 weeks! 🤪
161
Reposted by Project Wallace
Sacha Greif @sachagreif.com · 28/04/2026
somehow I missed this awesome report about CSS usage from @projectwallace.com Definitely worth checking out! www.projectwallace.com/the-css-sele...
projectwallace.com
The CSS Selection - 2026 Edition - Project Wallace
The 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/2026
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!
171
Project Wallace @projectwallace.com · 24/04/2026
Fight slop, one lint rule at the time. Or all the rules. I don't make the rules. Or, actually, I do.
Terminal output of using stylelint to lint an entire project's CSS as a whole. There are loads of errors: file size too big, too many different CSS units used, too much selector duplication, too much declaration duplication, unused custom properties, too many declarations per rule. The list goes on and on.
010
Project Wallace @projectwallace.com · 23/04/2026
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...
syntax.fm
How to Fix Vibe Coding - Syntax #998
141
Reposted by Project Wallace
Bart Veneman @veneman.dev · 27/03/2026
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
091
Project Wallace @projectwallace.com · 24/03/2026
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...
Project Wallace layer overview. Highlighted is one layer: `config.text.fonts`. Other layers can be seen in close proximity.
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 Wallace
Bart Veneman @veneman.dev · 01/03/2026
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.
Project Wallace homepage. A hero banner says "Your css has dirty secrets and Wallace knows them" against a mostly dark gray background. Project Wallace analysis page. The page header shows the page's title inline with toggles for choosing whether to analyze a URL, file or pasted CSS. The same gradient dark background is used.
171
Project Wallace @projectwallace.com · 27/02/2026
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!)
021