Hi Viktor, Very informative article, really like it.
Marcin Sękalski

Thanks for the feedback!

I’ll look into providing you with more examples.

  1. Sure, makes sense :)
  2. sure
  3. I can elaborate on that in the article, it’s mostly meant to mean that you don’t need the cascade for OOCSS methodologies, but you can still work with it if you want. (Albeit I think once you get used to BEM, you rarely need it, hence the warning to avoid it.) I’ll update the article.

On folder structure:
Don’t get me wrong, I’d never just dump everything in a simple directory, that’s why I outlined what I usually go with. Saying “it doesn’t matter” != “put everything in the same directory level”.
Also: I did not try to imply, that you should have a single css file for all cases, but it is what in most cases works for me for small projects.

I didn’t elaborate on this, but when I work with bigger projects, I usually defined so-called “areas” in the website.
For example: “main” and “admin”, where the two is sufficiently different, that it justifies separating them.
In such cases, I would have a “css/” folder, inside which a “main/” and an “admin/” folder, where both of these can have their own blocks defined.
These can be mutually exclusive, but for example if the admin area uses a lot from main, then it can be defined as a set of extra blocks on top of main, and be used together. (Be careful though, not to override blocks from main accidentally however.)

I might add an extra section about this, since your question shows I might’ve gave the wrong impression.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.