In reply to Sami Keijonen.

To better illustrate my point, if I am working with a framework and I want to change the layout of a given row using for instance Foundation, I can simply read the classes applied and change them or replace them. For instance if I see "large-4" and "large-8" which means a 4-column followed by 8-column grid in a row, it would be easy to change that to "large-6" and "large-6" making two even columns, or I could reverse the original order the classes are used in to move a sidebar to the right instead of the left. In contrast, without a framework, that same change may require reading 500 lines of CSS in order to identify the way in which a sidebar has been floated, to find out how the row has been cleared, to find out what logic is holding it all together. The code applicable may be found in as many as 20 different locations in the style sheets broken down according to what area of the template it applies to, or different media queries. And possibly, it will take 10, maybe 20 experiments with different CSS or different div placements to find a solution to the same problem I described above. I might find for instance that a certain column is created by a class that reads "width: 70%; max-width: 750px;" but when I change those values, the layout breaks and now the search begins for what other changes need to be made to keep the layout held together.