After having created folder structures for my SCSS files many times for many different projects over the years, I decided to create a Github repository so that it’s easier for me to get started and improve; hopefully it can be useful to somebody else trying to wrap his/her head around it as well.
First of all, here is the repository that you can clone to get started, and here below is an image that shows how the folder structure looks like.
The main ideas behind the organization of these files come from a couple of resources with a few tweaks, and 99% of the credit goes to them of course.
I am basically merging the two approaches, in order to have something that makes a lot of sense yet is easier to understand than the resources above. During the years I always found that the first approach was great but could have done with a bit more modularity, while the second one is a bit too technical to wrap one’s head around.
So these are my folders:
Here you can find mixins, extends, placeholders and variables and all that code that doesn’t actually outputs CSS.
In this folder you can put generic reset styles like normalize.css, starters like Bootstrap or Bulma, typographic starters, stuff like fontawesome, and so on.
This folder contains styling for simple basic elements like buttons, links, titles, inputs. These are “units”. If more elements are merged, they go into the next folder.
UI components are composed of elements. This means these components made up of elements. An example of a component is a group of buttons, a form, a header. This is where majority of our work takes place.
This folder contains code specific to certain pages. For example, some custom styling for the layout of the customer account.
Utilities are very specific classes used to change appearance of some element. They should be prefixed with “u”. For example, .u-center could be used to center some text, u-uppercase to make it uppercase, u-floatLeft to float some image on the left, and so on.
This folder contains print specific CSS.
Here you can add third party code for plugins like slideshows, for example, while Bootstrap would go in the “02-Base” folder because it acts like a reset.
This folder contains code for older browsers.
Overrides for any of the folders above go here, however this is mainly for plugins. It should not be abused.
So far this file organization has proved to be quite good, easy to understand yet complex enough to allow for enough flexibility. Let me know if you have ideas for improvements.