Aha. So...maybe I could figure out those server side includes and solve my nested template issue. Hmmm...I'm glad to hear that it isn't difficult, though I guess it depends on what you're used to and your general level of comfort and knowledge. As noted, the more I get into it, the more I realize I DON'T know. I did various Google searchs on templates before I posted, wondering if I was missing something - seems I didn't search on the right topic and so came away still thinking that this was harder/more complicated than I thought.
I've been meaning to dig up a good server side include for the "last modified" bit on each of my pages, because the Javascript one I'm using now works fine in everything but Netscape. Now I know where to begin looking.
GoLive has all sorts of Dynamic Content abilities, but because I assumed that I didn't need them for most of what I'm doing, I hadn't really investigated them. However, I think I'll start with the simple script in the code approach, as I've done with any Javascript. Handcode. Then I understand what I've done (or at least there is a greater possibility of same). Of course, this all comes back to my need to get the content out there, which was more important, and remains a priority over the time I would love to devote to understanding the options more fully. Sigh. I need a clone!
I can also see Jim's great big grin from atop his soap box (giggle)...funny thing though...I'm ok wih letting GoLive do my HTML for me, and quite sure that, for me, it is faster than doing it by hand and I've learned how to edit the source code with BBEdit and by hand, but when it comes to stuff I have no clue about (scripts of all sorts) my comfort level disappears - I've had GoLive create some real lulus (some of their proprietary "actions") which don't validate and don't work in all browsers.
So, I can see both sides of it. The stuff that GoLive hides "under the hood" (proprietary stuff, like Diana referred to) I try to stay away from - that stuff I feel I DO need to learn, if only to maintain better control of it. And it's a slow process.
Enzo, I had no idea that the creator of the CSS site was a TS reader! Welcome to TS! I think what you've done is a great exercise - don't get me wrong. My comments about looking at sites with as many different browsers still stands - even if you get on someone else's computer to do it. I have a Pentium 1 machine rescued from the recycling that I use entirely for the purpose of being able to check my sites on PC browsers, since all my work is done on Macs. We're more than happy to send you screen shots of "what happens" in different browsers, if you'd find that helpful. We've done it for those who don't have the capability of running the various OS X browsers.
Of course, looking at the site statistics for my most-visited site, the North Andover school district main site which gets just over 100 unique visitors per day right now, it is very clear that at least 85% of the world is using some flavor of IE - though almost 13% of the browsers can't seem to be identified by GoStats, so I'm not sure if that means they're using later versions of NS, which GoStats doesn't seem to recognize. And 90% of them (my visitors anyway) are doing it from a non-Mac platform - largely some flavor of Windows. So, making the CSS work in IE is absolutely essential - and the problems that occur in other browsers may have more to do with the non-compliance of the browser than any error on your part.
Enzo, I now plan to spend some time at your extremely useful-looking site - the server side includes is where I'll start!
Any other suggestions Diana? (Now you've done it...those photos ain't gonna get edited and online for a few more hours!)