2 weeks ago I attended my third and supposedly the final New Adventures Conference in Nottingham. NaConf has been one of my favourite conferences over the last few years, hence my attending of all three, however this years event managed to come out at the top.
For the second time in as many weeks, I have found myself talking to business owners about the lack of care they have been shown by their agency. I’m pleased to say neither related to projects we had delivered!
Although similar in terms of principle and process, there are different rules that should be observed when designing for the web as opposed to designing for print. These new rules came as a bit of a revelation after 10 years of designing with printed media in mind. Luckily, team moresoda have been on hand to gently suggest how I might better change my mindset from print to web.
At some point in most web projects there comes a point where we have to present our designs to a client. This can be quite an emotional stage because, as a team, we feel we’ve arrived at a design that ticks all the boxes: it’s innovative, usable and will deliver on the project goals. We’ve become attached to this design and want everyone else to like it as much as we do. Ultimately however, we realise they just might not like it and this makes the whole process quite nerve-wracking.
Over the last few years CSS grid systems have become very popular. Frameworks like blueprint, 960.gs and YUI Grids CSS seemed to pop up out of nowhere, providing us with a way of easily building balanced, well structured websites. Most well designed websites you browse these days are built around a grid system of some kind, although it might not seem obvious at first, an underlying grid structure will be there somewhere.