The dangers of using temporary visual layouts
Sunday, November 12, 2006 at 9:10PM So early on in the development, I pick a template that has the basic features I'm looking for -- two or three column, header and footer. More often than not, two column is good enough and I wind up cargo-culting the design from [Bulletproof Web Design](http://www.simplebits.com/publications/bulletproof/), a book that taught me a lot about building flexible pages that cope with people's weird browsing habits.
The trouble is that, when I demonstrate these applications to clients while we're building them, and they think the design looks really, really good. They don't want to then hire a designer to produce a custom look -- the one I've come up with is perfectly good. It's difficult to explain that actually I borrowed it from elsewhere and I'm sure I'm not the only one. Wouldn't you rather have your own unique branding?
So if you see me launch a number of sites over the next couple of months that look remarkably like they should be selling bagels, you'll know why...
Geekery,
Ruby and Rails,
Work
Reader Comments (5)
Hey, diversification is important. Perhaps they really should be selling bagels?
How about using a grayscale/bleached layout for preliminary development. That way, you have the basic structure but no real design.
Jamie: That's a really good idea. Use something that gives me the features I'm looking for while making sure it looks butt-ugly. Ah, what I should do is choose the colour scheme myself -- lots of bold primary colours. :-)
mathie: yeah.. you could try a dafodil yellow scheme
:-P
annbel: They'd definitely go for something as nice as that, particularly with an orange footer...