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.
Apply at https://jobs.wheatoncollege.edu/PRIMARY PURPOSE:The Senior Web Developer serves as the technology lead for Wheaton’s Web Strategy team. This person will guide the implementation and support of our digital channels, working with the team and other stakeholders across campus to define, create, and implement digital projects. The incumbent is responsible for managing the technical resources that support the college’s primary websites and…See More
"At the time we had 2 full-time employees and a temp on the web team. We had over 150 users trained to do the migration; some departments assigned more than others. Each department was required to assign someone. As far as I know only a few had any…"
The more I learned about Sanmita, the more I was convinced of an incredibly capable, intelligent, and fully featured web firm, with design, development, and hosting all available. Sites with great flexibility, yet with sensible navigation... fully scalable, all with painless content management after launch. I tested sites they developed on my iPhone, and they automatically adjust (responsive)... no need for an app version. I'm specifically focused on a brilliant new CMS bundle, AcademicsWeb,…See More
It was a process, but yes. Once we had approval from leadership to pursue a new website, we presented to our idea for a CMS to the Web Advisor Committee to get their buy-in. We further presented to the executive committee, provost and deans,…"
"For us 'buy-in' came from the top-down. All websites are required to be in T4. That being said we conducted over 100 training sessions including using T4, writing for the web, how-to migrate content, and migration workshops. We conducted…"
"We finalized our conversation from a 50,000-page, static, Dreamweaver-maintained site into a T4 CMS-driven site in 2014. We trained 250 campus staff as content providers. We also trained the content providers how to migrate their own content. We now…"
"Hi all - we implemented T4 in November 2014. So far the tool is working very well for us. I recently trained 21 people across different departments and they're now empowered to update their own content. The tool was relatively easy for most to…"
Missouri State University is accepting applications for a full stack developer/engineer.Position comes with superior benefits, including group health insurance, life insurance, retirement, tuition waivers, wellness programs and professional development opportunities. Learn more about benefits.ResponsibilitiesServes as technical lead to guide Web applications…See More
"Calling all OU Campus users! Learn more about the relaunch of the OmniUpdate Community Network where members share tips, tricks, code, and more in this blog post, or see it for yourself at ocn.omniupdate.com