Smashing Magazine conducted a detailed survey of 50 popular websites to see answer questions like Serif or sans-serif? Large or small font? Light or dark background? and more.

Though the findings aren’t scientific, the study shows a clear set of common practices and guidelines for setting type in Web design. Granted, these points should serve only as rough guidelines (not hard and fast rules):

1. Either serif or sans-serif fonts are fine for body copy and headings, but sans-serif fonts are still more popular for both.
2. Common choices for headlines are Georgia, Arial and Helvetica.
3. Common choices for body copy are Georgia, Arial, Verdana and Lucida Grande.
4. The most popular font size for headings is a range between 18 and 29 pixels.
5. The most popular font size for body copy is a range between 12 and 14 pixels.
6. Header font size ÷ Body copy font size = 1.96.
7. Line height (pixels) ÷ body copy font size (pixels) = 1.48.
8. Line length (pixels) ÷ line height (pixels) = 27.8.
9. Space between paragraphs (pixels) ÷ line height (pixels) = 0.754.
10. The optimal number of characters per line is between 55 and 75, but between 75 and 85 characters per line is more popular,
11. Body text is left-aligned, image replacement is rarely used and links are either underlined or highlighted with bold or color.

Of course, every website is unique, and few people want their sites to look like everyone else’s sites. But it’s always great to keep in mind that following these guidelines could make your website feel more familiar to your readers. (If you are a data and spreadsheet nerd like I am, check out the spreadsheet of the study and export its data for further analysis.)Similar Posts:

• CMS Fridays: When “Too Much Content” Is Really Too Much, And How To Plan For It
• Consultant Thursdays: What If Your Client Asks You To Implement A “Crazy” Enhancement?
• Silly Saturdays: Cheese or Font?

The opportunity is for a temporary to permanent mid to senior level Information Architect that lives local to  San Francisco.

The company is a high-end fashion retailer in Union Square area of San Francisco. Office is in the heart of everything: shopping, restaurants, transportation, and is housed in a heritage-style office building with exposed brick walls, big open spaces, and a cozy, close-knit team.

Must be able to lead initiatives and make recommendations, and be proactive the user experience process. Experience working on major site builds in an e-commerce environment is required. Experience in fashion a major plus, but not a requirement.

Please be able to have the full range of information architect skills like building wireframes and writing personas, understand shopping cart functionality, and an ability to evangelize your user experience ideas to a greater team. Having a great sense of humor, and a collaborative team spirit is great too.Similar Posts:

• Career Mondays: Information Architect — Los Angeles, CA
• Career Mondays: Web Product Manager – Los Angeles, California
• Do You Know The User Experience Process? Here’s A Good Place To Start
• Want To Get Started As An Information Architect? These Are Last Books You Will Ever Need.
• Agile and UX: July 8, 2009 in Los Angeles, CA

You’re implementing Drupal, SharePoint or something else that’s a “content management system”, and you’re getting the client involved in creating the content. One problem — getting them to use the content management system is impossible.

Seriously, I’m all for putting power in the client’s hands, but they have to be prepared for that power, and most of the time the person “given” that power has many more things to do than edit content in a website or extranet.

Here’s a few more truths about content management system and how they affect clients.

Sometimes what you wish for is what you get

All clients love the idea of editing their own site, but have no idea what it takes to create content. It means sitting down, opening up Microsoft Word and actually putting thought into the words that you are going to write. And that’s a lot of work, and they usually have no one on staff to do that task. I can’t tell you how many times I’ve had clients wanting to edit their sites because it’s been sitting for months, and they’ve forgotten the password.

Once they get in, they usually get out as quickly as possible, and ask you to add the photo or make the change.

Having that power and using that power are two different things, and many a time the client just throws up their hands and expects the company that implements the CMS to add the content.

What to avoid? Write in the contract that you aren’t responsible for content until you are responsible for it when the client is footing the bill.

The client has no one adept enough to use the CMS technically

Some CMSes, like SharePoint and SilverStripe, are straightfoward to use and for the most part don’t require extensive training to get the ball moving; within five minutes of each, I can train someone on how to add a page, how to edit content, and how to upload files.

Some of the other CMSes? I would never want my mom opening up Joomla.

Ever.

The reason they’ve brought you in for the project is not only for your design skills, but for your technical skills. The reality is that most companies small enough to want to go open source are also too small to maintain a site if it gets much further than changing out some text because their staff isn’t technical enough. Open source doesn’t mean free, and that free sometimes comes with technical overhead.

What to avoid? Put in time for training. A lot of it.

Open source is still open source — buggy and sometimes hard to use

When you use “free software”, you sometimes get what you pay for, and the client will never understand why you’re using it, other than, “you’re billing me for this, why doesn’t it work?”

The open source CMSes are what they are: developed by programmers that have a love of developing software, but sometimes do things their own ways or they aren’t thoroughly tested. Some clients don’t understand this, and figure the CMS should be bug free right from the get go.

Whatever system you select, explain to the client there’s going to be an upgrade path, and associated costs with it. This may mean some kind of maintenance deal in the future that’s like dependent on the upgrades coming out.

What to avoid? Have a very real conversation with the client about what open source means, and explain to them all software is buggy. Seriously.

CMS sites don’t plan themselves, and a bad information architecture can set you back years

The client is fully engaged, learns how to use tool in a way cavemen learned how to use fire, then “burns” themselves the first way through.

Bob down the hall in accounting can barely spell information architecture, much less construct one, and a single workshop over an hour isn’t going to give someone enough training when some of us have been honing our craft for years. It’s about planning, and poor planning for some CMS implementations can be death for user adoption. Or, how’s your company intranet holding up?

What to avoid? Book an information architect all the way through the project. If they are engaged, they can give the guidance needed for the site, and it will save time and money in the long run.Similar Posts:

• CMS Fridays: Why Should You Use A Content Management System?
• CMS Fridays: Showing Progress And Managing Content In A SharePoint Implementation
• CMS Fridays: The Ugly Truth About CMS Migrations
• CMS Fridays: Picking A Content Management System
• QuickTip Sundays: SixRevisions And The Lack Of Search

Is there a product that screams more for competent Information Architects and User Experience experts than SharePoint?Similar Posts:

• CMS Fridays: Design and Planning Worksheet
• CMS Fridays: Do End Users Really Care It’s SharePoint?
• CMS Fridays: Content Management Isn’t Cheap
• CMS Fridays: SharePoint Permission Dependency Chart
• CMS Fridays: Site Maps Vs. Meta Data Information Architecture

After that explanation, during which her eyes glazed over, the response was, “How about just telling me what books to read.”

Here are five books I like a lot.

Note that none of them (well, one) is written by one of the user experience experts that are most often cited in blogs. There are many authors out there that present equally valid points that should get equal time, and I found these books to be extremely useful and valuable. Most of the books describe the patterns and theory of information architecture and user experience, but a couple of them go into detail about the tools we use to communicate, and how we fit into the software development and web design process.

The last five books I would read if I wanted to learn about information architecture

Why We Buy: The Science Of Shopping

By Paco Underhill, Why We Buy is a great read on the observational study of why people shop, how they shop, and what they buy. Most importantly, it sets the stage for triggers for the motivations of completing an action, which is the basis of all interactive interactions.

This book is not too scientific, but honestly, you can look other places for that; what we’re seeing through the eyes of Paco is the emotions of browsing and shopping in the real world.

Don’t Make Me Think

By Steve Krug, Don’t Make Me Think is the cut-and-dry version of information architecture and the best methods of web navigation. Covered in 216 pages are enough screen shots, design patterns and quick points that just about anyone can get started on building their own websites or improving them dramatically.

What I like most about this book is that Steve doesn’t talk down to the reader like some other specialists, he informs the reader in a very comfortable, friendly tone.

Designing Interfaces

By Jenifer Tidwell, Designing Interfaces most importantly shows exactly what is most important about designing software and web sites: that all applications should follow a very well defined set of a patterns so the user interactions follow exactly what the user expects.

Jenifer’s book goes into excruciating detail of what interface widgets to use when, and why the widget should be used, how to use them, and examples of how the widgets were used in other applications.

Web ReDesign 2.0: Workflow The Works

By Kelly Goto and Emily Cotler, Web ReDesign works through not only examples of wireframes, site maps, and how to quote projects, but looks at the project management process of web development. What I like best is that the book shows exactly how Information Architects, Web Designers, Programmers and the client fit together in an orchestra of what happens before, during and after a site launch.

Kelly and Emily also do a masterful job of including other expert voices and opinions like Christina Wodtke and Lynda Weinman about what it takes to launch a successful and user-friendly website.

Grids for the Internet & Other Digital Media

By Veruschka Götz, Grids is a out-of-print but very valuable publication that goes into amazing detail about the usage of grids for interactive applications (not just the Internet but also for multimedia applications and print design).

The book also covers the lost art of typography, how it should be used in websites, and usage of type on a grid. Even if you aren’t a designer, you’ll appreciate the clear and concise examples displayed in a very modern fashion of this title.Similar Posts:

• Interaction Design Patterns: Why Re-invent The Wheel?
• Cool Website Tuesdays: Template Monster
• Grids: Both A Good Design and Usability Idea
• CMS Fridays: Site Maps Vs. Meta Data Information Architecture
• Designing an Effective MySpace Open Social Application