Build your own CSS Framework: Background

So you have been doing them stylesheets for quite some time or you might just be starting up, no matter who you are. If you haven’t been residing under a rock for the last couple of years you know there are some great CSS Frameworks out there. I like some of them more than others, especially the 960.gs which I’ve used once. You might say that using a framework once isn’t enough, but that comes down to how you use them and who you are. Personally I unzip the framework and first head over to their demo-html to get a good grip of what they are doing and then just take it apart one file/stylesheet at the time.

Why you might think, and I’m with you, but for me as a professional xhtml/css/javascript-developer I’m really picky about my stylesheets, structure of documents, naming conventions of classes and nine times out of ten handcode pretty much everything in my projects. That might be time consuming, but as a developer you learn what to do when something isn’t working properly and get the right fix from the last project you worked on where you were struggling with the same annoying Internet Explorer-bug (yes, it’s mostly IE, for me as a mac-user/developer anyway).

So, you have the experience dealing with problems and found the solutions. My friend, you are closing in on your very own CSS Framework. And this is where I will start my little series on CSS frameworks. In the next part I will cover some basics you should think about when you are starting your journey towards your own CSS Framework and then move on the to more juicy stuff like reset, grid and typography-stylesheets and something you will not get from a framework you download.

So, get my RSS-feed to know the second I publish the next post in the series or just swing by in a couple of days or so.