design

Earlier this week, following much anticipation, we launched our website redesign (if you're reading this via RSS, check it out! http://affinitybridge.com), which has been in the works for several months. It began as a rebranding of the company logo, then new business cards, and finally the website. When we began this redesign process with Kirsti Wakelin, who did the design for all three, we had to spend some time considering and reconsidering what we wanted to convey with our logo and branding. Affinity Bridge has always tied itself to the imagery of bridges. We had to ask ourselves if that was something that still spoke to us, and that we felt still spoke to the people and organizations we work with.

You may have heard or read comments similar to the following about CSS frameworks:

"They are not flexible enough."
"It's too much useless code."
"I like to keep my CSS clean."
"Why do I need a framework if I know what I'm doing?"
"The site is not going to change, so we don't need a CSS framework."

A CSS framework cannot be expected to be the final solution to all your problems, but it can be a useful tool for structuring and theming your site more efficiently. Read on to learn more about what CSS frameworks are, pros and cons of using them, existing framework options, and related themes.

What exactly is a CSS framework?

Every time you start a new project there are several basic lines of code that you add to your CSS; you may want to remove the default margins added by the browsers, set the font size to 12px as the browser standard, create a popular layout, etc.