Created
May 25, 2013 17:37
-
-
Save chriseppstein/5649985 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mymodule { | |
@at-root { | |
.#{&}-header { ... } | |
.#{&}-footer { ... } | |
.#{&}-body { | |
a { ... } | |
span { ... } | |
p { ... } | |
} | |
} | |
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.mymodule-header { ... } | |
.mymodule-footer { ... } | |
.mymodule-body a { ... } | |
.mymodule-body span { ... } | |
.mymodule-body p { ... } |
Can someone please give another example of how namespacing might be used--thanks @aceofspades, I just would like to see it in another context.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Has there been any discussion to do something more unobtrusive? For me, the value of namespacing comes in when integrating, where it's not possible or edit and maintain the source. For example, bootstrap and foundation both use
.table
which to me is too generic.With styles.css:
Then
Would compile to