After a long absence of no blog posts on this website, I’m back.
Here is the main reason…
Joel is an adorable excuse! in a non-biased way of course.
So after much thought, I’ve decided that I want to focus on writing more about WordPress and general web development. As well as experimentation with using new technologies, I want to test web tools that help workflow and productivity.
I’ll revisit my past posts and comment on how I’ve applied these technologies in real life projects.
At the time of writing, Foundation 6 has been released so I’m keen on experimenting with this framework even though I’m an avid Bootstrap fan.
I’m attempting to compile a comprehensive list of how developers and front-end engineers structure their CSS using the SMACSS (Scalable and Modular Architecture for CSS) approach.
What is SMACSS?
“SMACSS stands for Scalable and Modular Architecture for CSS, and is more a style guide than a CSS framework. On a high level SMACSS aims at changing the way we are turning designs into code. Instead of working in a page mentality where you try to turn a single page design into code, SMACSS aims to identify repeating visual patterns. Those patterns are then supposed to be coded into flexible/re-usable modules, wich should be independent as possible from the individual page context. This is not a revolutionary point-of-view for a programmer, but in the web design world this is indeed a newer way of thinking.”
I really wanted to point out the reasons why web developers should start using Sass and I came across the Clean out your Sass junk drawer slides by Dale Sande. It shows just how much the thought process of well structured CSS has changed over the years. So if you still work with fellow front-end web developer/engineers who aren’t using any CSS Preprocessor, point them to these slides.