meets Tuesday and Thursday from 0800-0915
office hours in Manning 112
Class Schedule
10 Jan | intro
15 Jan | clients
17 Jan | servers
22 Jan | networks
24 Jan | basics lab
29 Jan | structural layer
31 Jan | presentational layer
05 Feb | working with layers
07 Feb | behavior layer
12 Feb | images & design
14 Feb | website lab
19 Feb | document markup
21 Feb | tools that read markup
26 Feb | document markup lab
28 Feb | spreadsheets
05 Mar | formulas & functions
07 Mar | data display
19 Mar | database tools
21 Mar | spreadsheets lab
26 Mar | relational databases
28 Mar | tables
02 Apr | relationships
04 Apr | input & output
09 Apr | SQL
11 Apr | complex queries
16 Apr | databases lab
18 Apr | presentation design
23 Apr | presentation delivery
25 Apr | presentation lab
30 Apr | 0800-1100 | final in class presentation
This work
is licensed under a
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
home & schedule | class blog | syllabus | contact | grades
Once you are comfortable with hard coding,
you will create a web site for this class and, possibly, for your future use.
Follow the guidelines on this page to create a site
that will include separate pages for each of your succeeding tasks (03, 04, 05, and 06),
as you will link those completed tasks to their page, when you have completed them.
You may use any applicable tool to do this task. You may hard code your site using only a text editor, like Brackets or Notepad ++. You may use a familiar tool, like Microsoft Word, to create your site, paying close attention to the peculiarities of using a tool optimized for text as a tool to create web pages. You may use an html editor - any free editor or commercial editors such as Dreamweaver.
You may use this as an opportunity to try out different things because the requirements for task success are fairly constrained and provide you ample experimental leeway.
We will consider several models to look at for ideas. You may make your site exactly like the examples if you wish, but I hope that you will find this task useful enough to custom-build your sites to meet your own needs and design ideas.
You may build upon your hard-coded initial page, or you may use a template to create an entirely different look. But the site must meet the conditions specified for this task.
You will create a web site for use in your work with this and other classes. In its structure, your site will look something like this diagram (which, coincidentally, is an image map so you can click on any page and go directly to it).
Keep your site consistent in look. If you don't choose to use a template, at least ensure that all the pages share a similar look in terms of backgrounds, font style and color, and use of bullets.
Don't overload your home page. Keep it simple so that it loads quickly
Every page should have some way to alert users when the page was last updated
use hyperlinks (either as text or as linked image objects) to ensure the user can navigate throughout your site.
Add at least one example of a server side script and at least one example of a client side script somewhere on your site.
At a minimum, your home page needs to meet W3C validation for HTML and for CSS. It must validate in order to get any points for this component. If it doesn't validate, the W3C tool will point out the line of code where the invalid code is located.
When you create this site, create it to a folder on your computer give the folder the name you want for your site.
When you publish it to Opal, publish the entire folder.
After you have published your web site, send me a note telling me that it is ready for viewing
and tell me your site's URL so I can find it.
When I type in http://opal.ils.unc.edu/~yourOnyen or http://opal.ils.unc.edu/~yourOnyen/yourFolderName
I should open up your home page.
This means your home page should be named index.htm or index.html.
The task 02 gradesheet in your Sakai dropbox contains the specific standards and their weighted values.