Mark Hensler — Tue, 27 Feb 2001 06:58:19 +0000

good point...
If/When I do it to mine, I'll probably do as much as possible using the server-side language. Using a cookie to store a userID, I'd query a DB for that users preferences. Then print table colors accordingly.

bhorstkotte — Mon, 26 Feb 2001 06:36:02 +0000

I was doing that on my site a month or so ago, but decided to drop it: the upkeep on the CSS files and images for each style just wasn't worth it, and I decided one of my "schemes" was a lot better than the others, so I got rid of my scheme selector.

Anyway, if you want to do it, here's how I did it (one possible way, surely there are other more clever ways):

- I had a schemes directory, with a subdirectory for each of my supported schemes; these directories contained a css file, and a few image files (logos changed when the scheme changed, for example)
- I had a select in the navigation bar that listed the available schemes, and when a selection was made, would save the scheme name in a cookie, and do a location.href = location.href
- each page (via an include file, and by the way, this was all in ASP, you need some kind of server side script to do it, or at least it seems that way to me) would read the cookie, and create a "link href" statement in the page according to the selected scheme path
- references to the variable images was also created by script, using the value of the selected script directory
- Obviously, the entire site is CSS-aware, so that the UI paints according to the selected scheme (CSS and image files)

I finally decided to pitch it when I came to the conclusion that I needed multiple css files for different browsers (one for IE, one for NS4, one for NS6); just too much upkeep with n browsers x n schemes

Mark Hensler — Sun, 11 Feb 2001 23:04:01 +0000

Hey klerner, welcome to TWF!

This is a big project. Especially if you want to change fonts and graphics. CSS is probably the best way to do this, as you can dynamically change everything (colors, fonts, and images) with JavaScript. With JavaScript, you would be able to set cookies, and keep the layout for each page, etc. etc.

I will be doing a souped up version for my site. (I may even include moving content around like Excite and Altavista). But I will be doing it all server-side with PHP and databases. That way, I can keep relational DBs, and track users.... They're color scheme, content scheme, what pages they frequent, their browsers type, OS, and more and more...

I would suggest looking for a prefab you can use, unless you have knowledge of JavaScript (or PHP), and the time to work with it.
try http://hotscripts.com and http://resourceindex.com

Good Luck,

Maverick — Sun, 11 Feb 2001 01:15:46 +0000

My 2 cents: (and that's all this advice is probably worth )

Adding a layer of complexity like that (especially if you're not 100% confident of how to implement it) is just asking for a headache. Letting the user pick a color scheme is little more than a useless toy. It does nothing to improve a site and I'd be willing to bet that very few visitors would use it. At least, they wouldn't use it beyond trying it once, saying "wow, kewl" and then never giving it another thought. You'd be a lot better served in the long run be devoting that energy to improving site content.

That said, actually doing it isn't too hard. There are probably a bunch of different ways to do it, and all would involve heavy use of style sheets and the most efficient would also use cookies although you can work around that with some sort of scripting like PHP or ASP. In a nutshell, the HTML code for a given page stays the same and the elements are defined with the various .css files. Whatever color scheme the user picks, the appropriate style sheet is loaded so that the appearance of the page changes without the underlying code changing. The style sheet choice is then saved in a cookie so that it "follows" the user from page to page and will stay set for repeat visits. To make that happen, just get yourself a good style sheet editor (I like Bradbury Software's TopStyle [url]http://www.bradsoft.com/topstyle/index.asp)[/url] and read a quick tutorial on simple cookies. Hopefully, by the time you're done you'll have given up on the idea, but you will have gained some valuable knowledge

The idea of changing graphics makes things quite a bit harder. I could explain a way to do it with PHP, but it involves yet another layer of complexity (as well as creating multiple graphics sets) that just wouldn't be prudent without a real firm grasp of what's involved. Sorry to sound like a broken record, but in case you couldn't guess, I'm a die-hard member of the substance over style crowd and have found that tricks like that are usually a mask to cover poor or nonexistent content.