March 23, 2005 8:47 PM GMT
#3 is way good..
tweaking the CSS... um... has anyone else actually *looked* at the code that builds these pages....
Firstly we have a range of javascript, that would be better hived off into an external source file so you download it *once* not every time you view a page.
now t-web does indeed have a seperate CSS file... tis pretty big, but this is the point.. put this stuff here and not in the main page.
so now we move onto the page itself, i'll avoid preaching about using a table to hold the whole page
.
the site proceeds to override many of the CSS styles on the page, and provide extra ones. its *that* that will make a face lift to be serious work.
This page alone defines table background colour directly. and how many pages use tables?
now we have a big in-line style block as well, not totally sure as to why, but hey it works.
some more javascript, that again would be better off in a seperate file, or files even.
we also have a huge amount of in-line style code, which again will be a big problem to adjust.
The way foreward:
To start with while people work on the graphics etc they would like to use the current site needs some serious work to get ready for it. *all* the inline style code needs removing to the external stylesheet file, or adding to a second one. ditto the javascript (though thats more to save bandwidth than anything else).
once this has been done the stylesheets control the basic appearence of the site. naturally the stylesheets are designed *first* and then the individual pages are purged of the in-line style code bit by bit, with the pages being tested each time to make sure nothing breaks. Somewhat labourious but perfectly possible. While doing this controls are allocated a style 'class' that makes logical sense where it is not already present.
Its not a case of having one style for buttons.. have one for submit buttons, another for cancel etc.
Now the pages are CSS compatable. trouble is all locations are still hard coded. thus the colours and borders etc can be changed fast, but actually moving things is still not possible.
a move to XHTML 1.0 removes all the formatting code to the stylesheet as well. now the layout *and* colours are controlled bya single file (possibly a few such files) for the *whole site* changing the stylesheets in future is thus a simple way of changing graphics and colours etc.
this is 100% comatible with having the pages written out by scripts, though the scripts themselves may require some adjustment.
Overall this is worth doing, even just to the degree of changing the colours and graphics, while leaving the layout alone, the whole hog is more complex but allows vastly greater flexability in future.
As an aside xhtml 1.0 should render on anything, even if they drop the CSS totally the data is still all there.
Finally i wish i was even 1% as good with photoshop. I'm nowhere close.. them samples are amazing.
code monkey signing off...