If we're going to use namespaces in classnames, we should be consistent. `.action` is a pretty generic classname, and if we are worried about conflicts with other CSS libraries (I assume we are because there is a push for namespaces), this kind of thing would make them likely.

We could do `.bb-action`, but to avoid this problem altogether I suggest creating class taxonomies by "ux unit". For example, an app is a unit of ux, meaning you might have a suite of classnames like:

    .app-header { ... }
    .app-actions { ... }
    .app-toolbar { ... }

Highly unlikely to conflict.