10 questions for bloggers and web designers

Whether you design web sites or just like to tweak themes for your WordPress blog, you’re mak­ing design deci­sions all the time (even if you’re just using a theme out-of-the-box, you chose it). This list of ques­tions isn’t meant as a guide to good design, but you might want to have a look at your site and see if any of these apply.

Here, in no par­tic­u­lar order, are some of my design pet peeves:

1. Why are fonts so small?

Designers are fond of small fonts, but when you have to squint to read a site intended for a more gen­eral audi­ence, you have to won­der what the designer was think­ing. Take Good Magazine, for exam­ple (pic­tured below, actual size). I’m a fan of Good, which in most respects is great. I sub­scribe. The print mag­a­zine is beau­ti­fully designed and the web site has a lot going for it, too—but it’s vir­tu­ally unread­able with­out zoom­ing the text. The body copy is 11px and the side­bar text is 10px, with no breath­ing space in the line-height.

Good Magazine detail

(Now that I’m done knock­ing the fonts, sub­scribe to Good. Really. It’s a great mag­a­zine and every penny of your sub­scrip­tion fee is donated to a wor­thy cause of your choice.)

You should be able to read a site with­out press­ing your nose against your mon­i­tor. That prob­a­bly means at least 12px fonts (which I’m using here, and which is prob­a­bly too small for most read­ers), and lead­ing of 140 or 150%.

2. Why are fonts so big?

You shouldn’t have to squint to read web sites, but that doesn’t mean they need to be read­able from across the room. Take the Stripped theme for WordPress designed by Ashley Morgan (who bought Upstart Blogger from me in December). The design works because there’s ample white space and noth­ing extra­ne­ous, but do the post titles really need to be 81px? I can read them from down the hall.

Selectively mak­ing some text larger gives your design hier­ar­chy; it cuts a path through your page and guides the eye to what is most impor­tant. But there are other ways to make ele­ments stand out (using caps, dif­fer­ent col­ors, or a heav­ier font weight, as examples).

Using large fonts, LIKE WRITING EMAILS IN ALL CAPS, is a bit like shouting.

Unless your site is geared toward the visu­ally impaired, avoid inflat­ing fonts indiscriminately.

3. What’s with the black backgrounds?

Black text on a white back­ground is arguably more read­able than white on black (it also tends to look more pro­fes­sional), though I know some peo­ple pre­fer white text on a black back­ground. But I’ve also seen many sites with black back­grounds and text in any num­ber of Dr. Suess col­ors. Even if there’s suf­fi­cient con­trast, read­abil­ity usu­ally suf­fers and, IMHO, most dark sites also look like hell. Worse, nav­i­gat­ing from a site with a black back­ground to a site with a white back­ground makes me want to have a seizure.

If you must use a black back­ground, take note of these tips from Mark Boulton:

When revers­ing colour out, eg white text on black, make sure you increase the lead­ing, track­ing and decrease your font-weight. This applies to all widths of Measure. White text on a black back­ground is a higher con­trast to the oppo­site, so the let­ter­forms need to be wider apart, lighter in weight and have more space between the lines.

—From Five Simple Steps to bet­ter typography

Here’s a site where the black back­ground works: Griffin & Hoxie (pic­tured below; I still find this site tir­ing to read, but the writ­ing is so out­stand­ing I’m will­ing to suf­fer). The design works as well as it does because the back­ground uses sub­tle gra­di­ents, the fonts are clean and con­sis­tent, and the text floats on a faint drop shadow.

Griffin & Hoxie

If you must read a site with a black back­ground, grab this book­marklet (drag it to your browser’s tool­bar), which makes it more read­able (via 456 Berea Street).

4. Why are your col­ors so garish?

Web 2.0 design is all green eggs and ham. Now, I know color is largely about taste (also about usabil­ity and acces­si­bil­ity), so any exam­ple I pro­vide is bound to pro­voke debate. But I don’t think web sites should look like children’s books. Unless they’re designed for children.

Green Eggs & Ham

5. Why is every­thing in 3-D?

Web 2.0 sites are fond of three dimen­sions. Perfectly fine for usabil­ity: if you can click or drag it, giv­ing an object some depth is appro­pri­ate. Otherwise, your web site shouldn’t look like it was made from extruded plastic.

This one goes with No. 4, since both are a byprod­uct of over zeal­ous Web 2.0 design­ers. For tips on how to do Web 2.0 design right (if you like this style), see the Web 2.0 how-to design guide.

Oh, and while it might be fine in Second Life, please don’t design your site to look like every­thing is sit­ting on a desk­top, or in room, or whatever.

6. Why is there so lit­tle white space?

You don’t need to pack every pixel with ads and gal­leries and Twitter updates and news feeds and com­ments and blogrolls and… Sites like The Unofficial Apple Weblog are crammed with use­ful infor­ma­tion, but is it really nec­es­sary to list the categories—all 70-something of them—on the side­bar of every page? I love TUAW, but I find the side­bar overwhelming.

Test your site in Crazy Egg. If you aren’t get­ting many clicks in a par­tic­u­lar sec­tion of your site, get rid of it. Or, move it to a dif­fer­ent page (for exam­ple, move your cat­e­gories to an Archives page). Give your con­tent some room to breathe. Leave a lit­tle empty space in your design for the eye to rest.

7. What’s with all the widgets?

Too many sites look like they’ve been spend­ing too much time on Widgetbox. It’s bad enough to fill your site with clut­ter (see No. 5 above), but half the time these wid­gets don’t work and they’re slow to load. And wid­gets suf­fer from an addi­tional prob­lem: a high inter­face to con­tent ratio. If you want to add a news feed to your site, don’t use a wid­get like this (the logo prob­a­bly takes up 25% of the space):

Instead, use some­thing like SimplePie to suck the feed into your site and style it to match.

Too many wid­gets on your pages is like lit­ter­ing your front lawn with polit­i­cal signs and pink flamin­gos. Be selec­tive or move them to a sin­gle page (for exam­ple, put your Twitter wid­get on your About page).

8. Why are you dis­play­ing full posts on your home page?

I don’t have any­thing against scrolling or scan­ning, but putting your full posts on an end­lessly unrav­el­ing home page makes me dizzy. I’d much rather scan a shorter list of titles with short, descrip­tive excerpts than hunt through con­tent I’m not inter­ested in. TAUW does it. I love Lorelle, and Lorelle on WordPress is a must read for any WordPresser, but I don’t find it easy to peruse. And it’s not just about read­abil­ity; too many posts on a page makes your site slow to load, espe­cially if there are lots of images.

Here’s one site where this sort of works: 3quarksdaily. But it works because the posts them­selves are, for the most part, excerpts from other publications.

You home page should look like the front of a house: a door and a few win­dows. Don’t turn your house inside out and dis­play all the rooms on the facade.

9. Why do you resize my browser?

There are too many exam­ples of this on the web, mostly the sites of design­ers or pho­tog­ra­phers. I get it. You want to show off your work in the best pos­si­ble way. But you wouldn’t grab the steer­ing wheel when some­one else is dri­ving and you shouldn’t grab someone’s browser either.

If you want to offer a fullscreen dis­play, at least let your vis­i­tors know what to expect. Better yet, give them a choice.

Here’s a site that gets it right: Richard Serra at MoMA.

MoMA: Richard Serra

10. Why are you still design­ing entire sites in Flash?

I don’t have any­thing against Flash, or flashy sites. But you’re design­ing for fel­low design­ers. If your site takes more than 10 sec­onds to load, I’m out of there.

I’m not say­ing that Flash can’t work for some sites, but your site bet­ter be fast. This Levi’s site is almost fast enough, but I still didn’t get past the first few screens. And this one for the Hyundai SantaFe is stun­ning, but who has time for every new screen to load?

I’d rather surf on my iPhone.

ThemeMeme
Looking for a host that does’t suck? I’ve been with probably 20 different hosts. The best, hands down, is AN Hosting. They offer unlimited storage, unlimited bandwidth, unlimited mySQL databases, unlimited websites, and a free domain for life. Only $5.95/mo! Plus, 3 months free hosting! Sign up with AN Hosting now!

20 Comments on "10 questions for bloggers and web designers"

  1. Amber says:

    A lot of per­sonal blogs owned by teenagers and those just get­ting into blog­ging and/or design tend to do small because they think that’s what “in”. I’ll admit I did the same for a long time mainly because I didn’t like the way the sans-serif fonts looked like at a larger size. Also, news­pa­pers and mag­a­zines (not great exam­ples, I apol­o­gize) cram a lot of infor­ma­tion in with really tiny print, so design­ers might think that if peo­ple can read that, then they can read the same fonts on the screen. (I know, not true, but some design­ers don’t know any better.)

    On the same token, I think design­ers are some­what afraid to use larger fonts because it might alien­ate users. I stayed away from overly large fonts until I perused some really good designs. Large title fonts don’t have to trans­late to large type fonts and I think that is where there is con­fu­sion (at least, there was for me). Once I got it fig­ured out, mak­ing the title big­ger than the body text just seemed like the right thing to do.

    I don’t see a lot of sites though that use the white text on a color back­ground scheme much any­more, so I think peo­ple are real­iz­ing there is a read­abil­ity issue with that choice. Or maybe I’m just going to the wrong sites. ^_^

    Really great article!

  2. Amber, I think you’re right. People think small fonts are cool, and younger peo­ple don’t have any prob­lem read­ing them.

    Larger fonts are fine, if used selec­tively. But there’s really no rea­son to go much big­ger than, say, 50px. A web site isn’t a poster. The larger your fonts, the less infor­ma­tion that fits in a win­dow, so the visual impact is often lost. With few excep­tions, I just find large fonts annoying.

    The white text on a black back­ground isn’t very com­mon, but I always find it jar­ring when I stum­ble on a site that uses it. It’s fine for image-heavy sites (it’s great for the Richard Serra at MoMA site men­tioned above), but it doesn’t work very well for text-heavy sites.

  3. Amos says:

    Great list Robert. How I like my lists, fleshed out with pic­tures. Well done. In the spirit of “let’s talk about me some more” thanks for putting my site in a pos­i­tive light.

    I’m pretty much with you. I don’t usu­ally like dark back­grounds, espe­cially for weblogs. They can work for homepages/startups with big images and not a ton of text, but I think they usu­ally end up con­fin­ing and hard to read on weblogs. I much pre­fer white based sites.

    However, because I’m a spaz and can’t sit still with one design, I went dark for the hell of it. I haven’t read that Mark Boulton quote before but he’s spot on, and that’s been my expe­ri­ence try­ing to get a light on dark theme approach­ing some­thing I can live with.

    A tad more line height, big­ger font size (some­thing like 12px is usu­ally too small), and not a ton of bold. It’s why I ended up choos­ing Helvetica Light as the pri­mary font. Works bet­ter for those that have it on their sys­tem. Text-shadow also helps lift the text a lit­tle. Makes it more bear­able, but again, not every browser sup­ports this. When I pop the site open in, say, Camino or Firefox, it’s not nearly as appeal­ing to me. Comes of as flat. The writ­ing gets lost a little.

    Anyway, you’ve made my day Robert. The line “I still find this site tir­ing to read, but the writ­ing is so out­stand­ing I’m will­ing to suf­fer)” makes me happy. Not your suf­fer­ing per se, but the fact that my writ­ing is good enough to suf­fer for, in your opin­ion. It’s always been the writ­ing for me. The design­ing is fun, but not the point.

    Love your new themes by the way. You always were my favorite theme designer, not that there aren’t some other greats, but your style and cre­ative use of weblog space res­onates with me. Keep up the great work.

  4. Amos, your cur­rent design is the best white-on-black site I’ve ever seen. You’ve done a num­ber of sub­tle things to make it more read­able and it looks superb in Safari.

    I know you’ll prob­a­bly change it soon, which is why I included the pic­ture so peo­ple will know what I was talk­ing about after it dis­ap­pears. Seems nei­ther one of us can sit with the same design for too long.

    I meant it about the writ­ing. When’s the novel com­ing out? Sometime soon?

    Glad you like my themes. Everyone should check out your themes, too.

  5. Amos says:

    Thanks for the kind words Robert. I gotta dust off some of those bug­gers you link to. Gettin’ alit­tle crusty I think. But the novel, and thanks for ask­ing, is a mess, just a big fat mess. I don’t write in a lin­ear way, A to B to C. I have chap­ters in a jour­nal, some on the com­puter, a bunch on yel­low legal pad pages crum­bled in my lap­top bag. And I lose a lot of it. Don’t ask how, but I do. And I don’t really care because I do it over, but dif­fer­ent. It’d be funny if I wasn’t mine.

    What I need to do is hun­ker down for five-six months, spend twenty to thirty hours a week on it and it’ll be good. But I’m such a spaz I can never stick to a sched­ule. Schedules are hard for me.

  6. Amos, you need to do NaNoWriMo. (Haven’t we talked about this before?) I did it a few years ago and banged out 50,000-odd words, then had a sin­gle copy printed through CafePress. No one else will ever read it, but hold­ing that book in my hand was a rare plea­sure. I also printed my NaNoWriMo jour­nal in the back.

    Seriously, you should try it. But you don’t have to wait until November. You might also try putting some of it up on Zoetrope. It’s fas­ci­nat­ing to have peo­ple actu­ally read your stuff. I’d like to read it.

  7. I’m guilty of #2 since I am run­ning the Stripped theme. I pretty much have zero work­ing knowl­edge of design. I try to go for a sim­ple look using red, white, black and gray(s). I just want to be able to dump ran­dom thoughts on the net in an attempt to amuse my friends. Are there any good starter sites to learn a few design ideas?

  8. Rob, there’s noth­ing par­tic­u­larly bad about Stripped. It’s fine for your Tumblr-like blog.

    As far as sites to learn design, SitePoint might be a good place to start. It’s a lit­tle tech­ni­cal, but there are also some good, basic design arti­cles. These look good:

    The Principles of Beautiful Typography

    The Principles of Beautiful Web Design

  9. zakoops says:

    You don’t need to pack every pixel with ads and gal­leries and Twitter updates and news feeds and com­ments and blogrolls and…”

    Alas, the web is like enter­ing a crowded city with eye-catching big ads, with honks-honks and police car sirens as the background.

    In the mean­time, your site as well as the themes you are offer­ing is like being inside a museum of peace and beauty.

    The dis­tinc­tive designs are like yours whereas the rest is just annoy­ing flash­ing lights. Someday, peo­ple will see!

    And keep up the good work (I’m actu­ally on a vari­a­tion of my own based on Aperio)!

  10. Thanks, zakoops. Post your URL so we can have a look.

  11. Great list, Robert. Mac users can save them­selves burned reti­nas on black-background sites by press­ing control-option-command-8. It inverts your screen col­ors. I use it all the time. That and Shift-Command-S with the Web Developer Toolbar for Firefox. It removes all stylesheets and makes every­thing per­fectly read­able bare HTML. Sad, but use­ful on standards-aware, “over-designed” sites.

    (Control-Option-Command-8 is also great for April Fools Day)

  12. Great Mac tip, Ian. Thanks!

  13. I agree with you on most points, though I think there are instances in which full posts, rather than excerpts, are sim­ply more user friendly. You’re absolutely right that a list of long posts can quickly become a mess; just as excerpts can quickly become a usabil­ity nightmare.

    In my case, I went with full posts because much of my audi­ence are skim­mers; they won’t go father than the home page until I’ve already proven to be a good read. I may yet change that for­mat, but for now, I think it works well.

    I’d also like to speak up on behalf of light-on-dark web­sites. Yes, like so many other things, it can be done poorly – maybe it often is. However, a white screen isn’t nec­es­sar­ily easy on the eyes, either. After a while, it can feel like look­ing into the sun.

    In fact, one of my favorite site designs hap­pens to be guilty on both counts: the famous Daring Fireball.

  14. Javier says:

    Great list. I agree with yo in all the items. Regarding num­ber nine (red­i­men­sion­ing of the browser win­dow) I’ve come across a very inter­est­ing tech­nique that you might imple­ment in you future designs. The site where I saw it has many of the def­fects in your list (dark back­ground and not enough empty space for starters) but this ‘trick’ it uses I find very amus­ing. He has fluid columns that when the win­dow gets to be to small merge together to form a sin­gle col­umn of text, man­tain­ing its pro­por­tions all the time. I think that for some­one pas­sion­ate about grids as you are this could be inter­est­ing:
    http://blog.persistent.info/

  15. @Andrew: I think full posts on the home page can work, but only if you limit them to five posts or so. Better yet, have one full post and sev­eral recent excerpts. I’m against full posts pre­cisely because most read­ers are skim­mers; it’s eas­ier to skim excerpts and then go to the posts you really want to read. Most of your new vis­i­tors prob­a­bly come to you via Google any­way, so they’ll decide from that land­ing post whether or not you’re a good read.

    I agree with you about white screens. There’s some con­tro­versy about what is more read­able (see On the read­abil­ity of inverted color schemes, for exam­ple). The prob­lem is that most design­ers don’t know how to do white on black prop­erly, or they use other, less read­able, col­ors on a black background.

    Daring Fireball doesn’t use a black back­ground. It works because the back­ground color is softer and eas­ier on the eyes, and there’s ample line-height (1.8em).

    @Javier: That’s an inter­est­ing idea, but I’m not a fan of liq­uid lay­outs. Liquid lay­outs change the length of the line, which can affect read­abil­ity, and they break eas­ily. Your exam­ple works as well as it does because there are no images and it cre­ates addi­tional columns as the width increases, but still, I think it’s a bit of a gimmick. :)

  16. I’ve actu­ally been con­sid­er­ing keep­ing only the most recent post, and dis­play­ing the rest as excerpts. It’s a great com­pro­mise to the usabil­ity problem.

    Still, one of the rea­sons I chose to dis­play entire posts is that many peo­ple, or at least those I’ve talked to, pre­fer it that way. For all the pseudo-science and the­ory we can try to apply to design, it still comes down to the seem­ingly arbi­trary pref­er­ences of the user.

    Oh, and I think I’ll add Griffin and Hoxie to my list of places to visit for inspiration.

  17. Both for the writ­ing and the design.

    (Sorry for the dou­ble post.)

  18. Andrew, you’re absolutely right: every­thing comes down to pref­er­ences. There’s no one design that’s going to please everyone.

  19. Griffin & Hoxie is great. The writ­ing and design are superb, and Amos is as rest­less a designer as I am, but far more tal­ented. He refreshes often and it’s always inter­est­ing to see what he comes up with.

  20. M-RES says:

    Robert I think you’re right about a lot of points, but from a designer’s point of view the web is a paradox.

    It is both a prison of con­strict­ing lim­i­ta­tions (you can’t use any font you like unless you stick to graph­ics and then they bump page loads, aren’t as eas­ily indexable/searchable et al), and a plain of enlight­ened free­dom (you don’t need to WORRY about get­ting those line-breaks per­fect, or man­u­ally styling every aspect once you’ve built your (tedious) stylesheets, you’re not locked to the phys­i­cal dimen­sions of sheets of paper and so on.

    When print design­ers first move to the web they fall into the ‘guilty party’ list in terms of forc­ing browser win­dows to a spe­cific size, forc­ing smaller font sizes, try­ing to use odd for­mats for lay­out — basi­cally fight­ing AGAINST the tech­nol­ogy that they see try­ing to remove their absolute design control.

    After a while they see how lib­er­at­ing it can be to let go of that obses­sive need for con­trol and work WITH the tech­nol­ogy. Using CSS to give them the intri­cate con­trol they desire with­out restrict­ing their users to a spe­cific win­dow size. They see how the user should be able to look at a page in the way that suits them best for their device, OS, browser, graph­ics card.

    One of the issues I have with some web­sites is that they use small fonts because the site is designed with ONLY Windows users in mind, so when view­ing on a Mac with it’s inher­ently higher default res­o­lu­tions, the same num­ber of pix­els takes up a smaller space.

    What I try to do these days is avoid px mea­sure­ments in my CSS and revert to print-terms such as ems, picas and points — which look great in rela­tion to each other and will dis­play much more con­sis­tently. Plus they’re eas­ier to visu­alise from a print designer’s per­spec­tive with­out hav­ing to con­tin­u­ally check the effects of changes to a stylesheet. For instance you KNOW what 11 on 16pt Verdana is going to look like with 0.5 pica para­graph padding.

Got something to say? Go for it!

 
Share be a pal and share this would ya?
10 questions for bloggers and web designers