At a recent conference, the pro's and con's of fixed, liquid, and elastic layout was the topic of a lively debate. I'm interested on what the uwebd members think, along with any good references. Here are a couple references I have:
In my opinion, it's not really about choosing one. I think each has its benefits. As long as it is compliant with coding standards, use which ever layout best suits the needs of the site and its audience.
I like Molly's answer - "it depends" ;) I don't see how you can take a stand without taking the rest of the design into consideration. I tend to prefer a stretchy layout with a max-width and min-width set, especially since IE6 use is declining. But I've made fixed-width sites because it made sense with that particular site & design.
I remember reading that the site visitor tends to prefer dynamic layout (but I can't remember where). Graphic designers prefer the static width because it doesn't take so much effort to design for something that stays the same size all the time.
I go back and forth on this issue. We use a fixed width at case.edu because:
1) Liquid is more complicated and we distribute templated designs to users of varying skills who might easily break a liquid layout. (They're actually regular HTML files rather than Dreamweaver templates.)
2) We want to ensure our maintainers don't build pages with line lengths that are too long and thus harder to read.
3) We try to limit the space available because people have a tendency of filling up whatever space is available. If they have large monitors they could really overcrowd a page not realize how messy it gets on smaller displays.
As you can see the bulk of these issues relate to the fact that our sites are distributed and build and maintained by people of varying skill levels. If I were working on one site alone and I was doing the coding then I'd base the decision on goals, content, etc.
If the site will be better in liquid layout, I do it...
If the site will be better in static layout, I do it...
I spend more time to do a liquid layout, but it is necessary sometimes. The studies of architeture information and users decides what I will do.
I'm really hot on base line grid design these days (maybe too much) but fluid width site design pretty much rules that out. The other issue I have with purely fluid design is that it tends to not look so good on my really gargantuan monitors :) But like others have said, it really all depends.
"Implementing a content governance plan, complete with workflows and approvals, is essential when building a digital strategy for your site. Register for our upcoming webcast with Stamats to learn best practices for content governance. "
"Change is inevitable, and you want to make sure your content is still consistent after you reorganize your site. Check out the importance of using dependency tags in OU Campus to make sure both your site visitors and search engines can still find…"
"Planning a dream kitchen is like redesigning a website. It's easy to change the colors, but if the content doesn't provide what users need, your site visitors will not find value. So where do you start?"
"Your website’s voice helps drive your brand and deliver consistency across your site. In our latest blog post, Jim Heiney from Lock Haven University shows how to keep that consistency using OU Campus."
Just a brief note to inform all University developers that we have just published a new ranking of the top 200 Universities in Facebook based on the number of likes (fans count) each Facebook page has. Visit http://www.4icu.org/top-universities-facebook/For the US listing of all Universities in Facebook and their fans count popularity please visit…See More
So way back in "the day" (eight or so years ago), our employee/student email inboxes were routinely deluged with 40+ individual email messages per day due to the "campus-wide" email lists being open for anyone here to send messages to.Enough people eventually decried the situation, so we came up with an email/website "publication" that was basically akin to a "daily digest email" of what were originally individual messages.This was highly successful and took a large part of the burden off of…See More
Just a suggestion regarding a sustainable future for UWEBD (software platform). When I was at OmniUpdate we migrated from Ning to SocialEngine. SE has a Ning 2 import tool: http://get.socialengine.com/ning/ The process was pretty smooth for…"