I’ve been getting a little excited about Flexbox recently, so two weeks ago I wrote an introduction to it. Since then, I’ve used Flexbox to solve a problem that I used to see a lot.
At Clearleft, we occasionally work with clients right here in Brighton, but that’s the exception. More often than not, the clients are based in London, or somewhere else in the UK. In the case of Code for America, they’re based in San Francisco—that’s eight or nine timezones away (depending on the time of year).
Sharing is caring, especially when it comes to front-end development in the age of responsive design. We’re sharing the front-end style guide that we worked on for the Code for America project.
While doing some browser testing this week, [Mark](http://clearleft.com/is/mark-perkins) come across a particularly wicked front-end problem. Something was triggering compatibility mode in Internet Explorer 8 and he couldn’t figure out what it was.
Pattern portfolios are a great way to deliver modular, flexible and responsive design systems. They also offer huge benefits to both clients and technical partners when compared to traditional page-by-page static page template deliverables.
Performance considerations in responsive design should be a holistic part of the shaping of a site, right from the initial UX work. Using the concept of a ‘size budget’ can help avoid making it just a development issue that gets tacked on at the end.