Building this for a client. Napa Parts store, they want it to show their history, what they do (i.e. machine shop), employees, and contact info, etc. I have it roughed out atm, colors are the way they are just to distinguish where shit is (for me, and them). It's built in pure css, with a touch of javascript (for the tabs).

I need ideas on graphics for it, as I suck at graphic design, and I usually just farm that out to friends that can do it better than me.

Constructive criticism is good. As my brain is fried, and I cannot think if there is anything that Ive done wrong (except port it to work with IE6, as of right now, it looks good in IE7 and FF, havent checked the other browsers yet)

Here is the demo site set up on my test server:

http://www.braapster.net

Jason|1997 Eclipse RS

I contributed to the wiki!

happy p'ple

You set up the favicon before you did anything else, didn't you. You were all, "I don't feel like writing code, so I'll just make a favicon and FTP that to the server."

lulz

Looks decent, but there's not much to look at...

Hahaha.

No there isnt much to look at atm, I basically wanted to get a wide variety of people looking at it, to make sure it looks good on all screens, and in (most) browsers. Because its built with no tables, some browsers won't render it right.

Jason|1997 Eclipse RS

I contributed to the wiki!

happy p'ple

It's spelled "y'all".

other than that, it's a nice layout. Wish I had your CSS skills. 2gnt.com would benefit

______________________________
If a sentence found online has 35% misspellings or greater and includes at least two racially charged expletives, chances are it is a YouTube comment.

'95 Eclipse TurboGS (garage deco)
'95 TSi AWD (restoring a survivor)
'97 Talon ESi-T (poor impulse control)
'99 Eclipse RS-T (daily beater)
'13 Evo X (mostly stock)
'17 Sienna (Middle Aged Dad Mobile)



Factory Service Manuals: http://nawdu.de/files/

Heh, thanks Dino. As of now, I'm just waiting on the client for the go ahead with this layout, then I'll start prettying it up. And it's only coded for IE7/FF/Opera(I think it looks ok in opera, should at least). I haven't begun to tackle making it look good in IE6. That's a whole nightmare in itself.

What exactly would you do with CSS to 2gnt? Or should I say, what would you want to do?

Jason|1997 Eclipse RS

I contributed to the wiki!

happy p'ple

______________________________
If a sentence found online has 35% misspellings or greater and includes at least two racially charged expletives, chances are it is a YouTube comment.

'95 Eclipse TurboGS (garage deco)
'95 TSi AWD (restoring a survivor)
'97 Talon ESi-T (poor impulse control)
'99 Eclipse RS-T (daily beater)
'13 Evo X (mostly stock)
'17 Sienna (Middle Aged Dad Mobile)



Factory Service Manuals: http://nawdu.de/files/

I am the exact opposite. I'm horrible with syntax, and just general framework of a site. Which is why I use Notepad++ to code in, as it lets me know of many syntax errors I make. I actually did make this one w3c compliant for once

It took a little snippet of javascript:

onload = function() {
var e, i = 0;
while (e = document.getElementById('container').getElementsByTagName ('DIV') ) {
if (e.className == 'on' || e.className == 'off') {
e.onclick = function () {
var getEls = document.getElementsByTagName('DIV');
for (var z=0; z<getEls.length; z++) {
getEls.className=getEls.className.replace('show', 'hide');
getEls.className=getEls.className.replace('on', 'off');
}
this.className = 'on';
var max = this.getAttribute('title');
document.getElementById(max).className = "show";
}
}
}
}




To get the tabs to work right, but all that does is call on one div to replace another. (I wish I had your programming skills, in addition to my css skills )

Jason|1997 Eclipse RS

I contributed to the wiki!

happy p'ple

Originally posted by cc8balla
(I wish I had your programming skills, in addition to my css skills )

______________________________
If a sentence found online has 35% misspellings or greater and includes at least two racially charged expletives, chances are it is a YouTube comment.

'95 Eclipse TurboGS (garage deco)
'95 TSi AWD (restoring a survivor)
'97 Talon ESi-T (poor impulse control)
'99 Eclipse RS-T (daily beater)
'13 Evo X (mostly stock)
'17 Sienna (Middle Aged Dad Mobile)



Factory Service Manuals: http://nawdu.de/files/

Originally posted by DarkOne

Originally posted by cc8balla (I wish I had your programming skills, in addition to my css skills )

That's why you find my site code littered with shit like this: // Whoaly fuck it works?! and this: //wiki link - no idea if this is gonna work. and //i straight up stole this from dcforum+ bitches. Fuck yo couch. //Ouch. Why grab everything? //Fuck this is complicated...

_______

BPU'd skittle

from a function standpoint, it works well and does what it's supposed to and that's great. using css actually does work better, but can put a slight strain (in relative terms) on servers since the server is loading a single file. granted, a simple site to show the history of the store probably won't be too big of an issue, but if you start trying to pull in other stuff (like the photo gallery that you mentioned) could get a bit.. ugly since it would be loading a ton of pics in the background. the graphical part will probably end up making you want to kill once the client realizes that they can get picky about such things.

it's a good start though and the code can probably handle some abuse pretty well. however, if you plan on the site getting larger and more interactive, I'd start readying a 2.0 version and looking into something like php for future growth.

I'm pretty much ignoring the Wiki

Originally posted by gadkins1974
from a function standpoint, it works well and does what it's supposed to and that's great. using css actually does work better, but can put a slight strain (in relative terms) on servers since the server is loading a single file. granted, a simple site to show the history of the store probably won't be too big of an issue, but if you start trying to pull in other stuff (like the photo gallery that you mentioned) could get a bit.. ugly since it would be loading a ton of pics in the background. the graphical part will probably end up making you want to kill once the client realizes that they can get picky about such things. it's a good start though and the code can probably handle some abuse pretty well. however, if you plan on the site getting larger and more interactive, I'd start readying a 2.0 version and looking into something like php for future growth.

Jason|1997 Eclipse RS

I contributed to the wiki!

happy p'ple