When asking someone to help you with a problem you are having with your website there are several things you should do.
1, Always give a link to the website you are having the problem.
2. Give the name or source of the software you are using to build and manage the website with.
3. Make sure your questions are clear and direct to the problem.
The main thing to deffinately do is supply the link to the website!
This will aid the person, trying to supply help, a visual aid to the problem. If the question is about a site you are building and have not published, supply the part of the code that you are having problems with.
You can do something on your site in many different ways, having something to look at helps.
Example: you can build a "Comment Box" with tables or floats. Each can inherrit certain problems. The problem may have the same sympthoms but require different procedures to correct. These fixes can be a long drawn out procedure. I, for one, do not want to explain two diferent procedures for the same problem so that I cover all possibilities.
If you are worried that others may think your site is "Simple" or "Stupid", don't think that way. Not all of us are design genius and none of us know everything. Well, maybe Mark knows everything, I haven't seen him stumped yet but most of us fall short of being expert.
To those that are reading this that give advice, here's the rule!
I am in several groups that deal with design and development of websites. I have seen site critiques that would make the hair stand up on the back of Satan's neck. This type of critique is not productive. You want to slam someone, go to a professional wrestling match and slam a continder and get the reward you deserve.
Sorry about that, I'm a littl immotional about this. I just saw a critique, where someone told the person asking for the site critique, that this person "has no business trying to design a site!" This is not constructive, it's destructive and has no place in learning.
Anyone have any other ideas?
JB



Facebook
Twitter
LinkedIn
RSS
votes