[SCornelius7mufc]

Evening.

Ive run a website for my football team for a while now, improving it whenever I get time.

Today, my domain name purchase came through, so now Im really hoping to keep working on it.

www.sherbourneidentity.co.uk is the site, would be grateful to hear any opinions about it.

and like what you see? then feel free to add yourself to the visitor map on the main page.

[foot-loose]

It was all going so well until I was redirected to an old site and a billion popups opened. I didn't like that.

[SCornelius7mufc]

It was all going so well until I was redirected to an old site and a billion popups opened. I didn't like that.

where was that?

since i know i had problems with ftp and transferring my files for this new domain

[SCornelius7mufc]

>players >appearances

someone had already told me doesnt work, dont know why as the file appears on my ftp connection.



also, is the green to bright for anyone

one person has said its too bright to look at, but i dont know if its just their monitor not setup right, as it looks ok to me

[foot-loose]

It is very green.

You should speak to Viv for any HTML questions. She is our resident expert.

[catherine]

Can I have the captain's number? Hubba, hubba.

[Console]

>players >appearances

someone had already told me doesnt work, dont know why as the file appears on my ftp connection.

That page contains a frameset, as well as some bloody awful Frontpage code.

also, is the green to bright for anyone

one person has said its too bright to look at, but i dont know if its just their monitor not setup right, as it looks ok to me

The shade of green will appear different depending on whether you have a CRT, LCD or Plasma monitor, what video card you have, what drivers you're using and, in some cases, what version of drivers you're using.

For me, it's not too bright, just a little too plain. Solid green rarely looks good as a background.

May I recommend this site as a brilliant tool for checking the validity of your HTML code. It'll bring up errors for the site added advertisements at the bottom, but you'll just have to ignore them. You may also want to check all of your pages for consistent styles and broken tags, at least one page looks to have all the text in H1 (Old News) and the opening page is missing a '>' on the main image. There's also numerous examples of spaces next to equals signs which shouldn't be there.

Can I also suggest a <noscript> alternative to your DHTML menu, or just use an CSS implementation, that should at least automatically fall back for non-compatible browsers.

Out of curiosity, what did you write the page with? Some of it looks hand-written (mainly because of the mistakes) but some of it looks generated (as there's inconsistencies in the coding style, and it looks like Frontpage code).

Site Optimized for browsing with Mozilla Firefox

You may want it to be, but with all of that IE specific Frontpage code, it really isn't.

[SCornelius7mufc]

>players >appearances

someone had already told me doesnt work, dont know why as the file appears on my ftp connection.

That page contains a frameset, as well as some bloody awful Frontpage code.

also, is the green to bright for anyone

one person has said its too bright to look at, but i dont know if its just their monitor not setup right, as it looks ok to me

The shade of green will appear different depending on whether you have a CRT, LCD or Plasma monitor, what video card you have, what drivers you're using and, in some cases, what version of drivers you're using.

For me, it's not too bright, just a little too plain. Solid green rarely looks good as a background.

May I recommend this site as a brilliant tool for checking the validity of your HTML code. It'll bring up errors for the site added advertisements at the bottom, but you'll just have to ignore them. You may also want to check all of your pages for consistent styles and broken tags, at least one page looks to have all the text in H1 (Old News) and the opening page is missing a '>' on the main image. There's also numerous examples of spaces next to equals signs which shouldn't be there.

Can I also suggest a <noscript> alternative to your DHTML menu, or just use an CSS implementation, that should at least automatically fall back for non-compatible browsers.

Out of curiosity, what did you write the page with? Some of it looks hand-written (mainly because of the mistakes) but some of it looks generated (as there's inconsistencies in the coding style, and it looks like Frontpage code).

Site Optimized for browsing with Mozilla Firefox

You may want it to be, but with all of that IE specific Frontpage code, it really isn't.

1. The players>appearances page is an excel file saved to htm.... it used to work, not sure why now, will have to take a look
2. Yeah the green was just a quick fix, looked better than white.
3. Thanks, I'll check the validator out.
4. An alternative to the DHTML menu is at the very bottom, the text links.... what would you suggest as an alternative?
5. All my pages are raw HTML coded... never used Frontpage/ Dreamweaver etc ..... all I have done is apply the DHTML menu i found on a website.
6. There have been problems with the menu appearing in the wrong place in IE..... hence why I have written "Optimized for Firefox" ... as that is what I have tested it in most and have had least problems with.


Thanks everyone for the helpful advice, will try to get some time and start working on it to make the improvements.

[Console]

1. The players>appearances page is an excel file saved to htm.... it used to work, not sure why now, will have to take a look

Ah, I was wondering why I couldn't figure out which version of Frontpage you were using - it's Excel, which is actually even worse for HTML than Frontpage is.

As for that page not working, the entire lge_app_files directory, that the page refers to for frame sources, seems to not exist on the server. Your cssverticalmenu CSS and JS files also appear to be missing.

2. Yeah the green was just a quick fix, looked better than white.

Having just tried both, white does look bad, but it does look better than the lime green. Try halving the green, #008800 looks quite nice.

4. An alternative to the DHTML menu is at the very bottom, the text links.... what would you suggest as an alternative?

Well, the alternative at the bottom could be made complete, that appearances page, for example, isn't on there. However, I would do as I suggested before, either a noscript alternative, which would probably be a simple table layout (looking much like the DHTML menu, but without the hover effects), or an entire CSS based hover menu, which wouldn't need a noscript alternative.

5. All my pages are raw HTML coded... never used Frontpage/ Dreamweaver etc ..... all I have done is apply the DHTML menu i found on a website.

Except the one you made in Excel you mean. Actually, are you sure about this, there is a lot of non-W3C code that only seems to be created by MS Web tools in there. Take the numerous uses of bordercolorlight and bordercolordark. Those are almost exclusively created by Frontpage.

6. There have been problems with the menu appearing in the wrong place in IE..... hence why I have written "Optimized for Firefox" ... as that is what I have tested it in most and have had least problems with.

Yeah, it just happening to work in Firefox doesn't make it optimized for Firefox.

[Boboff]

It needs more naked ladies or girls in Bikini's, a Waggs page would add a bit of interest I think.

[SCornelius7mufc]

1. The players>appearances page is an excel file saved to htm.... it used to work, not sure why now, will have to take a look

Ah, I was wondering why I couldn't figure out which version of Frontpage you were using - it's Excel, which is actually even worse for HTML than Frontpage is.

As for that page not working, the entire lge_app_files directory, that the page refers to for frame sources, seems to not exist on the server. Your cssverticalmenu CSS and JS files also appear to be missing.

2. Yeah the green was just a quick fix, looked better than white.

Having just tried both, white does look bad, but it does look better than the lime green. Try halving the green, #008800 looks quite nice.

4. An alternative to the DHTML menu is at the very bottom, the text links.... what would you suggest as an alternative?

Well, the alternative at the bottom could be made complete, that appearances page, for example, isn't on there. However, I would do as I suggested before, either a noscript alternative, which would probably be a simple table layout (looking much like the DHTML menu, but without the hover effects), or an entire CSS based hover menu, which wouldn't need a noscript alternative.

5. All my pages are raw HTML coded... never used Frontpage/ Dreamweaver etc ..... all I have done is apply the DHTML menu i found on a website.

Except the one you made in Excel you mean. Actually, are you sure about this, there is a lot of non-W3C code that only seems to be created by MS Web tools in there. Take the numerous uses of bordercolorlight and bordercolordark. Those are almost exclusively created by Frontpage.

6. There have been problems with the menu appearing in the wrong place in IE..... hence why I have written "Optimized for Firefox" ... as that is what I have tested it in most and have had least problems with.

Yeah, it just happening to work in Firefox doesn't make it optimized for Firefox.

1. Yeah, there was a problem with the ftp connection, so it was inevitable some files never made it across.
2. Thanks for the colour suggestion, I'll take a look.
5. Everything is raw HTML... everything has been researched by me using google.... so those bordercolourlight and dark .. .are they depreciated tags which shouldn't be used now?? I had no prior knowledge of web building before building this, so everything has been cobbled together by whatever tags I could find on the net.
6. Well the menu didnt work in IE for a while, so that was just there whilst I was fixing the issue... I think I'll remove it.

[Console]

Everything is raw HTML... everything has been researched by me using google.

Ah, that could possibly explain the mixed coding styles within the pages then. However, some of the pages still look generated.

those bordercolourlight and dark .. .are they depreciated tags which shouldn't be used now?

They're not depreciated, they've never been in any official HTML or XHTML spec. They're attributes that Microsoft made up (as well as many other attributes and tags) during the browser wars in order to leverage users away from Netscape. While some other browsers do now support them, there are far better cross-browser methods to produce the same effect (namely, CSS), and they're certainly not Firefox optimizations.

[S4B]

It needs more naked ladies or girls in Bikini's, a Waggs page would add a bit of interest I think.

He ignore this suggestion Boboff?! How rude of him!

[SCornelius7mufc]

It needs more naked ladies or girls in Bikini's, a Waggs page would add a bit of interest I think.

He ignore this suggestion Boboff?! How rude of him!

apologies... didnt notice this one

erm WAGS.... I think I'll pass

and maybe I could but in some girls if their wearing football shirts, and make it topical