Bart Veneman

Partially solved in https://github.com/projectwallace/css-code-quality/commit/e398bd334c6dbb1e8d17dabea4318e1b62faa08e

I'd love to test [my library](https://github.com/projectwallace/css-design-tokens)'s output against a sort of 'official'-ish checker, @romainmenke has a very good point there. The opening post clarifies for me that I'm not the...

That feels like a very legit use case that I've run into myself as well. Based on the current implementation we'd need some work to make it happen but it's...

First we need changes in https://github.com/projectwallace/css-analyzer, because currently is calculates the size of rules by [looking how many children it has](https://github.com/projectwallace/css-analyzer/blob/master/src/index.js#L282). I haven't decided yet how I'd want to reflect...

Another option is to remove this rule entirely: we have another rule to [check for a low enough average](https://github.com/projectwallace/css-code-quality/blob/main/src/maintainability.js#L43-L62), so maybe we should leave it at that? All these rules...

I read https://css-tricks.com/organizing-design-system-component-patterns-with-css-cascade-layers/#aa-defining-button-state-styles last week and I'm now leaning towards keeping this rule as-is. You can break up large rules with dozens of custom properties like this: ```css :root {...

Hi, creator of [projectwallace.com](https://www.projectwallace.com/) here. I'd love to contribute in some form as a reviewer or analyst. Especially since last year's CSS chapter got scrapped. The almanac has shaped some...

One thing I hadn't really accounted for is the level of SQL knowledge required for the analyst role. Upon reading the role descriptions I think I'd be a better author...

I've added the outline to the [planning doc](https://docs.google.com/document/d/1FtntjUvqNT_66XtKQamZDPy0gI_kLZhkBaK7JJwE2ww)

I've had very little comments so far, so I'm unsure how to move forward with this chapter. I'd really hate it if we'd miss deadlines or not get a chapter...