public inbox for [email protected]  
help / color / mirror / Atom feed
From: Omar Kilani <[email protected]>
To: [email protected]
Subject: Re: "Stretchy" vs. Fixed-width
Date: Sun, 21 Nov 2004 18:10:07 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E407B44D@ratbert.vale-housing.co.uk>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Hi,

> Yes it is a fixed width site. I was just making comment to your 
> Microsoft comment :). Also I prefer fixed width sites. A fixed width 
> site is much easier to maintain, sets specific guidelines for you 
> content presentation and makes you actually think about how you are 
> going to layout the site.

Upon further consideration of the fixed width vs. "stretchy" issue, we 
have decided that there is one part of the site that would benefit 
greatly from a stretchy design, and that is documentation.

See the example we've created:

http://postgresql.tinysofa.com/files/docs.html

The reason that we believe that variable width is a better approach for 
documentation in particular is that people have different viewing 
preferences when referring to manuals or books online. The readability 
of online docs is improved if it is possible for the user to resize the 
text and the width of the browser window to accommodate their viewing 
preferences. Some may want to use all of their real estate while reading 
the docs, while others may only want to use 1/4 of their screen so that 
they can refer to the docs whilst coding at the same time.

(Having said that, it's worth noting that while our example page has no 
*minimum* width for text, it does have a sensible maximum (IE tweaks 
pending) to stop it from scaling and becoming unreadable on huge screens.)

However, while there are compelling reasons for docs to be variable 
width, we don't believe that people would be reading the rest of the 
site in the same way. It is most likely that somebody visiting the 
PostgreSQL website would be viewing it with their window maximized, and 
it is unlikely that they would want to refer to content outside of docs 
whilst performing another activity (as in the example above). Therefore, 
it's unlikely that someone would want to view the site in a width 
smaller than the minimum of 800.

We don't believe there is much of a case for allowing the site (apart 
from docs) to expand beyond the fixed layout width of 800. As mentioned 
by others on this list, variable width produces unpredictable results on 
a carefully designed layout. We believe that being able to control the 
layout from a design perspective, and the ability of the user to view 
the site as the designer intended (the way the majority of users would 
want to view it anyway) are good arguments for fixed width design and 
why so many designers choose this option.

Omar and Emily




view thread (24+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: "Stretchy" vs. Fixed-width
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox