Differentiating between objects, utilities, components, skins etc.

[tachyons-css]

Differentiating between objects, utilities, components, skins etc.

[mrmrs]

@colmtuite - For pros - I think for some people it makes a directory easier to navigate if they have an existing concept of what utilities, components, skins, etc. are. I don't find this to be too much the case with tachyons. There isn't really a notion of components vs. utilities. The majority of the classes are single purpose. I don't find that name-spacing classes by type has helped me with readability - or with information wayfinding. I.e I know what .cf does as a class. I don't need to know anything else. Labeling it as a utility doesn't aid me in any way. I don't think it's a bad practice per se, I just have not
found it to be representative of information I personally need while developing.

I have thought about dividing up the files into directories along the lines of

- base
- type
- structure
- skins

But I haven't found anything I'm 100% happy with. I would mainly just like to show relationships between which modules are most often used together. i.e widths, floats, display, and the clearfix module. Generally I use all of them together if I use floats at all. I would like a better way to visualize / illustrate that information. Basically until I am happy with an organization system - having them all bundled together in one directory seems better than a poorly thought out system that I change every two weeks :)

I think naming conflicts in classes are best maintained with a combination of an automated build-step / some manual review and isn't something I'm too worried about here. Eventually I'll have a custom name-space function as a part of the build step similar to how http://basscss.com and http://topcoat.io work.