Then reset the Current as you wrote & it worked.

Thanks!!!

in my _variables.sass partial I write:
$picturesTemplate: “.bigproject.our_products.product_x.product_x_pictures”

in my partial _picturesHeader.sass, that describes this particular element:
body
&#{$picturesTemplate}
.element_x

Doing so you can have both “library” for typical .element_x styles as well as be able to write alteration easily. If I have to differenciate between many nearly–the-same elements on one page (what is very rarely), I can alway simply put one more level to the selector and use descending selection. Or, if the elements are too different, just handle them as different elements and give them different names.

Sorry for the grammar – English is not my strength :)

I wanted the first one to have:
<div class=”media comment”>…</div>
<div class=”media”>…</div>

And the second to have:
<div class=”comment”>…</div>
<div class=”menuItem”>…</div>

For example, instead of this CSS and HTML:
.media { … }
.comment { … }
…
…

Have this?:
.media, .comment, .menuitem { … }
.comment { … }
…
…

Being a preacher of building a project styleguide, I was OOCSS before OOCSS was a thing. But now becoming a more experienced Ruby developer, I am coming to the same conclusions as you are with the coupling of OOCSS and SASS. In fact, I can’t see any other way of doing it.

A great example. I am working on a project where I have aside bubbles for additional information. Going with OOCSS I would need to have a class of something like “more_information” appended to both to cover the simular UI cases. Then to adjust for the delta between the two, I then would add the class of ‘call_to_action’ and ‘white_papers’.

But using SASS, I can simply use the single semantic class and then using the similar UI as a mixin within SASS, I can reuse that style without copying and pasting.

So in essence, I guess what we are saying here is in principal the same thing, build re-useable elements within your CSS and have a way to easily re-use that code.

I guess you could say, OOSASS?

Faster development time and faster download times are prizes that are worth having at the expense of pedantic markup and if somebody says it’s not semantic, I think the correct response is to shrug the shoulders.