|
|
|
|
|
|
Posted: Wed Nov 26, 2008 3:53 am
Guidelines
To combat, screen space, and everyone having varying amounts, it is advisable in CSS, (when arranging the layout) to use percentages, instead of absolute values.
Always make a text only version
The most common colour blindness in men, is usually red and green. Try to make sure an alternative is available, or an alternative design at least that uses different colour schemes.
For those who can't see very well and need to hear it, make sure you put as much text as possible into the coding, when filling in content. Try not to use images without ALT.
Different browsers are an issue. We will be testing on: Firefox, Flock, Google Chrome, Internet Explorer, Opera, Safari. Try to test your self on IE, Safari, Firefox.
IE is the most common windows browser FireFox is the most common alternative windows browser Safari is THE most common mac browser.
Opera is the most efficient browser, and offers the best tech, thus it might be an idea to test on it, just to see if it runs.
|
 |
 |
|
|
|
|
|
|
|
|
Posted: Wed Nov 26, 2008 8:13 pm
Guidelines for Coding
HTML Structure
1. When nesting tags, indent them, so that the first and last of the outer nest, are the closest to the left.
2. Unless the tags can be placed onto one line (one line being 40 characters long) place the end tag, below the first tag with space between them, where you can enter data (following Guildeline 1)
3. All tags should be in lower case, except where there are two words in one tag, in which case, the first letter of the second tag, is capitalized.
4. Comment the code. No matter what it is, comment it, and explain what it does.
5. In the header, input a comment, stating the original author, and any authors who have amended it, followed by the date they last made amendments to it. Also in the header, place a description of what the webpage is about, and what adjustments have been made.
CSS Guidelines
1. In a comment, add the author, the date last ammended, files that link to it.
2. In order to make it easier to read, put every variable on a new line. So width, height, such each be on an individual line.
3. Place comment headers were needed to indicate different purposes for the css.
4. Comment the CSS to show what it actually going to be used for.
General Coding Guidelines
1. Always comment your code, as to what it is doing.
2. Always put your name on the author list, followed by the year if it isn't already there.
|
 |
 |
|
|
|
|
|
|
|
 |
|
|
|
|
|