Hello, all, Well, you've got me sold on tableless layout with CSS, thanks to the excellent links some of you pointed out last week. Now I have another question. In your experiences, what are some guiding principles for deciding when to use Server-Side Includes to include common sections over multiple pages? As a programmer, it is very attractive to only maintain a common element such as a navigation bar in just one location, but I don't see it used as often as I would expect, especially in combination with CSS. (At least by looking for the .shtml extension, which I know is not always required.) On most of my sites, and even on subsites of larger ones, I can imagine having all sections but the primary content area be included this way. On the other hand, I know SSI is frowned on in some circles as placing more burden on the web server. (But why - isn't it just another request like a graphic or external CSS file? Or is there more to it than that?) I suppose this is only really an issue if you are manually coding and maintaining a site. If you are using content management software, you can just set up the common elements as part of a template, and if you change the template, all pages change automatically, either because they are built dynamically already, or maybe are rewritten when their dependencies change. Comments? - John Following disclaimer automatically added by my company, sorry. This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like.