Forum Moderators: open
(edited by: Dpeper at 2:28 am (utc) on May 21, 2002)
WebmasterWorld is full of folks willing to help you if you've got a question but site reviews are not a part of WebMaster World. You might want to review the charter for more information.
[webmasterworld.com...]
>Forgive
No problem, happens all the time.
Now, to your problem, perhaps you could rephrase your question in a more generic format and I am sure you will get lots of help. As you can see, there is a wealth of information here and a community of top people who will no doubt give you some very good pointers and ideas.
Welcome to Webmasterworld.
Onya
Woz
Most definately Welcome to WebmasterWorld!
There are many reasons why we do not specifically do site reviews, not the least of which is "reviews" are subjective at best.
We all have strong opinions regarding color schemes, graphic use and coding styles, and that is good! It makes for some very interesting (and insightful!) conversations.
You might try asking about a particular color combination, or about the advantages (or disadvantages!) of right-side menus.
If you have a specific problem, just post it. You will find plenty of helpful responses in no time at all.
Once again, Welcome to WebmasterWorld!
We've all learned that the second we start considering ourselves experts on anything webmaster related, there is always someone comes along and reminds us of humility.
That's part of the reason we aren't fond of urls and specific code problems. We'd rather teach people how to find the answers themselves through authoritative sources. It's the old teach a man to fish thing.
We don't want to quote joe's site down the street for an answer to a CSS/HTML problem, we want to show people where the answer is in the appropriate w3c standards recommendations. When we do that, we all learn from it - not just the guy with the problem.
We could set here and answer "do my homework - give me an answer on a silver platter" type posts all day long;, but who learns from that? If we instead talk about where the answer is in the appropriate specification or manual, we all brush up on it. Whether that is the w3c, a browser manual, or an equally authoritative source, we all know where to go next time. Educators and tutors first - code assistants second.
A few weeks ago, I had a friend email me with a specific css problem. He's built hundreds of sites over the last few years and is a huge commercial success at it. Not being the CSSguy, I deferred to the CSS2 manual on the problem. He said he would buy the CSS2 recommendation, but couldn't find it on Amazon ;-) After my intial shock wore off and I started explaining the w3c too him, he was a bit stunned that he didn't know a thing about it.
