↳ In-reply-to » Despite my earlier rant, today is a pretty lucky day. I've got a job as a tester, that'll start soon. Still a little nervous about it, but really looking forward to it!

@lyse@lyse.isobeef.org all my project are entirely standalone.

If I want to share parts then those become encapsulated entities to be included is said projects.

The reason to build it scalable with only classes is to have a logic structure that can be read in both HTML and CSS to understand quickly how they work as a block, even though I use lot of classes I often have at most one or two of them per element.

The other reason is that it helps me find the right part to work on on older projects, just yesterday I had to extend a part for a client project and I did it by finding the needed classes like this:
.ProductList > .ProductItem > .ProductItem-price
(The arrows are how I looked for them in HTML)
Then I can append the new element to have a note on the price.

Another thing that helps me is that I have only one level deep selectors with only pseudo selectors and utility classes as exceptions.