Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modular state-based classnames #5

Open
andi1984 opened this issue Jul 8, 2014 · 0 comments
Open

Modular state-based classnames #5

andi1984 opened this issue Jul 8, 2014 · 0 comments

Comments

@andi1984
Copy link

andi1984 commented Jul 8, 2014

Hi,

first of all, I really want to say that I like what you have collected so far, because I think a lot of frontend devs daily working with SASS and CSS think about these issues, at least they should.

What I still miss is some naming-convention discussion about state-based classnames inside modules.

What do you think about it?

I highly recommend Jonathan Snook's talk at BeyondTellerrand this year. He was pointing out that he moved from .is-btn-active state classes (which seem to be formulated as a question) to .btn-is-active.

I think this should be also pointed out to readers of this project.

Also pointing out to prefix every state class name with the corresponding module it belongs to, avoiding any clashes with other state classes of other modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant