IT-238 Checklist

 

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

 

The first time you view this page, some 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.

 

A few items are labeled as ‘CHANGED’. I have done so for the benefit of students who took IT-130 with me in the past. When you see ‘CHANGED’ it is a warning that we are doing something in this course that is a little different from how I asked you to do it in IT-130.

 

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

2.      Your code must be ‘neat’

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

·         Use indentation

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

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

<img src="basketball.jpg" alt="Picture of basketball">

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

6.      All <div> tags should be named using the ‘id’ attribute.

7.      Whenever you close a div, be sure to write a comment immediately afterwards indicating which particular div was just closed. The reason is that you may find down the road that you have many, many nested divs. In this case a random </div> somewhere on your page can be (will be!) very confusing.

<div id="about_staff">

  Blah blah blah

  Blah de blah blah blah

</div><!-- End of about_staff div section -->

8.      CHANGED: You do NOT have to specify colors using their HEX codes (e.g. #FF0000). That is, if you want to use ‘red’ instead of ‘#ff0000’ that’s fine with me. Just be aware that many programmers consider hex codes to be more ‘professional’.

9.      CHANGED: In this course, we will typically use single quotes for Strings (as opposed to double quotes). 

·         var name = 'Bob';   is GOOD.           

·         However:    var name = "Bob";  --> AVOID.   Though the use of double quotes here is perfectly fine, we will typically use single quotes around strings throughout this course.

·         That’s not to say that double quotes are illegal – they are not. However, you will see that there are good reasons for defaulting to single quotes around your strings.

·         NOTE: Around HTML attribute values, we still use double quotes. Look at the example below in which the values for the src and alt attributes are placed inside double quotes.

<img src="basketball.jpg" alt="image of ball">

10.  CHANGED: <script> tag does NOT always have to include the attribute:  type="text/javascript".  Many programmers feel that it should always be in there, but since you may be peppering your code with several of these tags in a single page by the end of the course. I will not require you to include the type attribute.

11.  CHANGED: Form elements should be named using the ‘id’ attribute. In IT-130, we usually used the ‘name’ attribute.

·         There is a subtle difference between the two. For this course, you should ALWAYS use the ‘id’ attribute unless you have a specific reason for doing otherwise.

12.  All form elements must be named using a ‘prefix’ naming convention:  ID names for your form elements should have a prefix indicating what the element is. For text boxes, use txt (e.g. txtFirstName, txtPhoneNumber).  For buttons, use  btn (e.g. btnSubmit); For radio buttons, use  rad (e.g. radPizzaSelectionType); For checkboxes use  chk  (e.g. chkMushrooms). For other form elements, you may use your own convention – but be consistent!

<input type="text" name="txtFirstName">           BAD: Uses ‘name’ instead of ‘id’

<input type="text" id="firstName">                       BAD: Uses ‘id’ but neglects prefix

<input type="text" id="txtFirstName">                Ahhhh… much better

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

14.  Every time you read in a numeric value from a form, you MUST invoke the appropriate parsing function parseInt()  (for integers) or parseFloat() (for decimals) on that value. In some cases, you may use the ‘Number()’ function.

15.  Naming conventions for Javascript identifiers (i.e. variables, function names, etc):  We will be using "camel-case" notation to name our identifiers. For example:  var thisIsOneVariable  or  function doSomethingInteresting() .  Be sure to follow official JS rules as well such as not beginning with a digit, avoiding reserved keywords, etc.

16.  Do NOT have any file named ‘default.htm’ or ‘index.htm’ or any other default filename in the web folder that you will be using this course. The reason is that I may want to examine your web folder to see the files you have stored there and how you are organizing your site. If you have one of these default filenames, then I will not be able to do look at your file structure.