Part of the challenge when crafting new markup is coming up with semantic class names that are descriptive but not restrictive. This article can’t help you come up with a base name, but it can help make applying those names to your markup and SASS quicker, easier to understand and modular.
There have been quite a few nice posts in the blogosphere about SASS and BEM and how to make them work together nicely. I have seen different ways that people prefer hyphens before elements or underscores, but that doesn’t really matter. What matters is that you have a system and you stick to it. Here is a real-world example that I have from a recent project.
I like to compare web design to architecture. I think it is an apt metaphor and will expand upon that idea later in a full article. For now, though, I'd like to share a quote from Mark Simon about the architect and teacher Charles Moore (my replacements in brackets):
@brad_frost does it again with "The Principles of Adaptive Design" http://t.co/lsFGE8O6e4 Great ills, too: RWD is the tip of the iceberg
We’ve been quiet for a time, I know. Heads down, working hard… not making time for ourselves and for self-promotion. Sometimes, when the projects are large and the problems are difficult to solve, it’s unavoidable.
It’s been a bit bumpy, I can tell you that. We treat everyday as a learning opportunity, so that keeps us ready for change, however tumultuous it may have been. As I look back at the past six months, though, I can’t help but think we’ve accomplished quite a bit. While the road has been long and bumpy, we have survived and gotten stronger and hopefully smarter. If we don’t learn a little bit everyday, we must be doing something wrong.
Designers — myself included — tend to love, love, love controlling the user experience. We call it “design”, but it is really a form of control. We anticipate how a user will interact with a website or application, and design/control the way they go from one task to another, find the useful buttons, read the content, etc… Its not so easy to control that experience anymore — or even predict it.
Web design workflow changes as often as there are new tools and methods, which is to say, practically every day. It's tough to keep up. I have been helped out a great deal by other teams that share their knowledge and their own internal best practices, so, through a local MeetUp group, I was inspired to do the same.