IT-130 Checklist

 

Here is a checklist you can use as you go through the course.

 

The first time you view this page, most of them will not mean anything to you.  Various requirements will be added as we progress. In other words, you are NOT required to meet a requirement if it has not yet been discussed in class. However, once a topic has been covered in lecture, you must meet that requirement.

 

1.       All pages must include the html, head, title, body, doctype, and, charset-meta tags.

2.       Use whitespace (but don’t overdo it!)  For example, you rarely need more than one blank line between sections.

3.       Naming convention for file names:  all lower-case,  spaces should be separated with underscores.

4.       Images must always include the ‘alt’ attribute.

5.       Web pages should be divided into sections using <div> tag.

6.       All <div> tags should be named using the ‘id’ attribute. This attribute should describe the section of the page, not the content (e.g.  <div id=”title_section”> is good,  <div id=”travel_agency”> is NOT good!).

7.       Colors should be specified using their HEX codes (e.g. #FF0000).

8.       All form elements must be named.

9.       Name form elements using the proper conventions (i.e. camel case, prefixes).

10.   <style> tag should always include the attribute: type=”text/css”

11.   All images must be stored in the ‘images’ subfolder of your site. NOT required until we have discussed creating subdirectories.

12.   All web pages should be stored in the it130 folder of your site. – NOT REQUIRED UNTIL SPECIFIED IN THE ASSIGNMENT

13.   Every time you read in a numeric value from a form, you must invoke the parseInt()  (for integers) or parseFloat (for decimals) on that value.

14.   All classes and contextual selectors should be named in a way that describes what you are trying to accomplish. They should not be named in a way that describes the style itself.  For example, ‘highlight’ would be a good name for a class.  ‘yellow-background’ would not.

15.   Naming conventions for Javascript variable and function names: camel-case (e.g. thisIsOneVariable); Be sure to follow official JS rules as well such as not beginning with a digit, etc.

16.   <language> tag should always include the attribute: type=”text/javascript”

17.   All pages should include the keywords metatag.

18.   All pages should include the description metatag.