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.
Hi,We're currently evaluating two content management systems - Drupal and Concrete5. We're very familiar with Drupal and also like the appeal of Concrete5, but know that Concrete5 isn't widely used. Is anyone here using Concrete5? I'd greatly appreciate any insight that can be shared.Thanks so much!Sarah GagneThe Dartmouth Institute for Health Policy & Clinical PracticeSee More
NewCity (a web design agency that specializes in higher ed) is doing some research on how web teams at higher ed institutions manage their websites. We want to find out what works for real situations and real people. We’re asking our previous clients and contacts in higher ed to consider participating, and we'll share the results so that we can all (anonymously) learn from each other. Feedback could also end up in a presentation of…See More
"Spelling errors, broken links, weak SEO, and accessibility issues can negatively affect your site visitors’ user experience. Learn how OU Insights continually monitors these areas and helps keep visitors on your site in today's blog post!
HighEdWeb is very pleased to announce our outstanding 2016 Annual Conference keynote speakers: Kimberly Bryant, Aspen Institute Fellow and founder of Black Girls CODE, and LeVar Burton, actor, director and educator.We’re also excited to share our full presentation schedule, which includes more than 70 presentations given in 7…See More