Assignment Checklist for IT-130
Here is a checklist you should always refer to before
you submit any of your assignments. It will keep you from making many small
nitpicky mistakes that you would otherwise lose points on.
Two important notes
1. Some of the items here are NOT official HTML-5 requirements. However,
many of them are adhered to by professional programmers and are considered to
be both good habits and good conventions. So please adhere to these conventions
as if they were part of the official standard. One example is the 'alt' attribute
The first several times you use this checklist, most of
the items 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 the course. However, once a topic has been
covered in lecture, you must meet that requirement.
- All pages must include the html, head, title, body, doctype, and, charset (meta) tags.
- Use whitespace (but don't overdo it!) For
example, you rarely need more than one blank line between sections.
- Naming convention for file names (this includes all file names such as your html files,
images, css files, etc): Name should be all lower-case, spaces should be
separated with underscores.
- You should not name your files 'index.htm'
(or 'index.html'). That particular file name has a special usage and
should only be used in particular situations.
- Images must
always include the 'alt' attribute.
- Web pages should be divided into sections
using <div> tag. (Begins around week 2 or 3)
- All <div> tags should be named using the
'id' attribute. If possible, your value for this attribute should
describe the section of the page, not the content. For example, <div
id="title_section"> is good. However, <div
id="travel_agency"> can be used if that
is really the only appropriate name for that section.
- Colors should be specified using their HEX
codes (e.g. #FF0000).
- All form elements must be named using the id
- Any time you have an 'id' attribute, you
should identify it using the proper conventions (i.e. camel case,
prefixes). E.g. id="txtFirstName". Note:
Do not confuse this convention for naming ID attributes, with our naming
convention for file names!
- <style> tag should always include the attribute: type="text/css"
- 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.
- 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
and function names: camel-case (e.g. thisIsOneVariable); Be
sure to follow official JS rules as well such as not beginning with a
- All images must be stored in the 'images'
subfolder of your site. This is NOT required until we have discussed