• 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15

Page Description

The official online schedule for Jonathan Bass's web authoring course at Rutgers University, Spring 2012. For each week you can find a listing of the work due; special announcements; an overview of the discussion topics and assorted supplementary material; a description of in-class exercises, tutorials, and demonstrations; and a breakdown of the homework assigned for the following week.

The schedule updates weekly over the semester, with the weeks displaying in reverse chronological order. Use the strip menu of photographic vignettes at the top of the page to jump to a particular week.

At the top of the page you can also find links to extended descriptions of major assignments, such as the End of the World project and the Location Documentary project; the class forum (mainly for submitting online work); and a variety of resources. These include a printable version of the web authoring syllabus, HTML and CSS templates, frequently used applications such as Firebug and Adobe Kuler, and demonstration models for some of the assigned pages projects.

Week Fifteen

Wednesday, May. 2
Where is the picture? A picture is on its way.

Work Due

Final Project

Due: 9 PM, Wednesday, May 2.

Upload all your final project files to a new "final" folder in your "425" folder on Eden. Check that all your links (e.g., site nav) work properly, all your images display, all your scripts function, etc.

Then in a reply to the "Final Project" thread on the Class Forum, post a link to your home page inside your "final" folder. Check that this link works properly and that your folder is not "forbidden."

In your reply, list all uses of jQuery and/or other scripts in your project. Specify the script and the page(s) it works on.

Note: After you have submitted your project, leave the work online and unchanged for at least one month after the semester ends. (If you wish, you may continue to work on a different version of your project in another folder or on another server. Just remember to leave the submitted version in your "final" folder unaltered.)

As with the midterm: If you need to make changes to any of your "Final Project" files, contact the instructor for permission before making any changes. Files modified without the instructor's permission will be excluded from the final project.

Announcements

Final Office Hour

4:30 – 5:30 PM, Wednesday, May 9, in Loree 010 on Douglass Campus. Stop by for grades, feedback, and conversation.

top

Week Fourteen

Wednesday, Apr. 25
Where is the picture? A picture is on its way.

Announcements

Late Start

Class will begin slightly later this week, at 11:30 pm. (This should give those of you with trouble arriving a chance to arrive on time.) I'll have semi-extended office hours following class.

We meet again in Loree 023.

Work Due

Final Project

Progress on the final project.

Revised Reviews

If you need to resubmit your review(s) and haven't done so already, this week is your last chance.

Discussion

Of Interest

A number of final projects are portfolio sites of one sort or another. As with the other projects, you should be looking aggressively for models and advice on the web. Here are some links that might be of use. As with any website offering advice, take the advice in context and consider your own needs as well as the requirements of the assignment.

CSS Bugs & Hacks

Web pages that display properly in Firefox or Chrome don't always display properly in IE. To resolve this problem: Use Conditional Comments to get your site to display accurately in Internet Explorer.

Related reading: 9 Most Common IE Bugs and How to Fix Them.

Here is another explanation of conditional comments.

Basic conditional comment for an IE-specific external CSS file:

<!--[if IE 7]> <link rel="stylesheet" type="text/css" href="ie.css" /> <![endif]-->

You would insert this special comment into the HEAD of your HTML file.

You should AVOID using hacks based on browser bugs; but you should familiarize yourself with the following hacks so that you recognize and understand them when you encounter them in older or less-than-bautiful code:

  1. Star HTML Selector Bug (will not work in IE7)
  2. Underscore Hack (should still work for IE7)
  3. Easy Hacks for IE7

Final Project Requirements: Updates and Clarifications

TBA in class

Activities

EWP Interactive Grid

Just a quick check on how this is working out. I've added a demo connecting two sortable lists using the jQuery UI sortable feature.

PHP: Getting the Feedback Page to Send Data

Like Javascript, PHP is a scripting language. Unlike the other two. which run in the browser, PHP runs on a server (e.g., on Eden or RCI).

For your final project, implement the Show Form PHP script (or a more recent equivalent script). This will generate a new page containing a table that presents the feedback information from your Feedback/Form Page.

Basically you can cut and paste the code into Notepad and save it with a .php extension. Then, in your FORM tag on your Feedback Page specify the file name as the action value (e.g., action="showform.php").

Note: PHP is a server-side script, so it will only work from a server with PHP installed (Eden does), but it will not work on your desktop or other personal computer. So you'll need to check the script online.

For a demo: see the still provisional final project checklist.

On PHP, see W3 Schools' PHP Tutorial, etc.

Ian Jennings, a former web-authoring student, offers this PHP script for sending your feedback data to a specified email address. He's added helpful instructions/comments in the source code.

Final Project Prototype Workshop

We'll focus on all parts of the project. Also, some focus on styling and wording your link blurbs (we didn't get to this last week).

With regards to the coding (and design) of the survey page: once again, refer to Louis Lazaris's Tips for Coding and Designing Usable Web Forms; the advanced form tutorial on HTML Dog; and Duckett's chapter on forms.

Homework

Final Project

Complete the final project. Due online by 9 PM, Wednesday, May 2. Additional instructions covered in class and in the Week Fifteen update.

top

Week Thirteen

Wednesday, Apr. 18
Where is the picture? A picture is on its way.

Announcements

Class Location

We meet in Loree 023. Start time is 11:10 am.

Work Due

Final Project

Add one additional page of essential content to your prototype (not an about or contact page, or anything secondary like that). Add the page. Integrate it into your site nav. Upload to your "prototype" folder.

Fill in any gaps in your protoype. E.g., make sure that your blurbs are complete, that your visual page has enough images, that any images not of your own making are CLEARLY CREDITED and their use reasonable under fair use guidelines; that the CRAP principles are happily applied.

Also: be sure to STYLE the table. Again, take a look at this article of table design with CSS.

Be ready to discuss ideas for your second visual section and for a writing intensive page.

Discussion

Final Project Requirements

Pages of the final project should include:

  • Home page with title, visual focus, site nav, introductory text, and preview of site content
  • Two main text pages/sections: (1) A reviews section with two or more reviews and a 7+ item links sidebar; and (2) second text page with one or more texts totaling no less than a mere 1200 words and in a genre that fits your project (tours, tutorials, creative non-fiction, critical analyses, research papers, project statements, and so on)
  • Two different visual sections (e.g., portfolio gallery page and project photo-documentation page; an illustrated tutorial and an inventory of equipment; a set of related graphs quanitifying a phenomenon and a set of photographs documenting the real-life effects of the phenomenon quanitified by the graphs)
  • Two supplementary pages (each must be a different genre)
  • Feedback/User Survey Page and related Showform PHP Page (or equivalent) with multiple questions
  • About page = about the site and its author
  • Contact Form = this may be on its own page or incorporated into one or more of the other pages; whichever works best (note: this is distinct from the Survey)

So ten (or more) different pages altogether, plus a main external CSS file. Note that content for a given page requirement, such as your reviews or a portfolio, may be distributed over several pages. For instance, a drawing gallery consisting of 21 images might present seven per page or a page of portraits, a page abstractions, a page of still lives. A research proposal satisfying the second text page requirement might present each of its major sections on a different page.

Note on visual sections: As discussed previously, a standard portfolio gallery should have 14 images at minimum. (Stronger galleries will have more images.) Each image needs a title and descriptive caption. The gallery as whole needs a short introduction explaining the selection of work and its role on your site. (E.g., what in particular is it that you want users to see in the images you present?) And stronger, B+ and A level galleries, again, will use grouping and ordering to organize the material.

Non-gallery visual pages, such as illustrated timelines or maps or visual narratives, will have different requirements. In such cases, it's best to consult with the instructor.

Note on second text page: Text should be non-fiction. If you have an idea for a suitable fictional text (e.g., short story, parody, satirical piece), you'll need to clear the idea with the instructor. If approved, in most cases, you'll need to preface the text with an introduction situating the writing within the context of the project. Moreover, a fictional text will usually need to be balanced with a diversity of non-fictional writing elsewhere on the site.

Note on jQuery: You should use jQuery or its equivalent for at least one of your visual sections. You should make at least two further uses of the scripting framework. The two additional uses, however, do not include using jQuery to open links in new tabs (a separate design requirement) or dropdown menus (optional but recommended where needed).

CRAP Analysis

Combined Midterm and Prototype Review/Critical Discussion

We'll go over the graded midterms in some detail. Some pages to begin with:

Activities

EWP Interactive Grid

A final part of the EWP: an interactive version that allows users to build their own End of the World stories from the images you provide. Uses a nifty jQuery plug-in that you'll need to incorporate into your final project.

Note: I've annoted the source of the demo version to help you to adapt the code to your own EWP and other uses. In the demo, fieldset elements replace the "figure" divs used in other versions of the EWP. That's because the interactive gallery is essentially a kind of form.

PHP: Getting the Feedback Page to Send Data

Like Javascript (and the Actionscript underlying Flash), PHP is a scripting language. Unlike the other two. which run in the browser, PHP runs on a server (e.g., on Eden or RCI).

For your final project, implement the Show Form PHP script (or a more recent equivalent script). This will generate a new page containing a table that presents the feedback information from your Feedback/Form Page.

Basically you can cut and paste the code into Notepad and save it with a .php extension. Then, in your FORM tag on your Feedback Page specify the file name as the action value (e.g., action="showform.php").

Note: PHP is a server-side script, so it will only work from a server with PHP installed (Eden does), but it will not work on your desktop or other personal computer. So you'll need to check the script online.

For a demo: see the still provisional final project checklist.

On PHP, see W3 Schools' PHP Tutorial, etc.

Ian Jennings, a former web-authoring student, offers this PHP script for sending your feedback data to a specified email address. He's added helpful instructions/comments in the source code.

Final Project Prototype Workshop

We'll focus on the Review Page, Survey, and Visual Section(s). Also, probably, some focus on styling and wording your link blurbs.

With regards to the coding (and design) of the survey page: once again, refer to Louis Lazaris's Tips for Coding and Designing Usable Web Forms; the advanced form tutorial on HTML Dog; and Duckett's chapter on forms.

Homework

Reading

TBA

Final Project

Progress. Two weeks to go.

top

Week Twelve

Wednesday, Apr. 11
Where is the picture? A picture is on its way.

Announcements

Virtual Class

There is no in-class meeting this week. However: work is still due for this week (the final project prototype by Thursday, 9 PM; see work due below) and new work is assigned for next week (seen homework below).

Note, also, that I've clarified the final prototype instructions in light of last week's discussion of them.

Work Due

Final Project Prototype (Part 1)

The first part of a prototype for your final project website is due in a new "prototype" folder inside your "425" folder by 9 PM, Thursday, Apr. 12. Post a link to this folder in a reply to the "FP Prototype" thread on the Class Forum.

The first prototype for the FP will consist of the following parts:

  • Home page
  • Revised review page – with sidebar of seven link blurbs (etc.)
  • First visual section (expanded) (if a gallery, then 14-plus images with introductory text explaining the content and purpose of the page and captions identifying each image)
  • User survey page: nine or more questions, at least three of which should be multiple choice and three of which using options

The pages should use a standard header with site identification (logo, graphic, etc.) and navigation. Each page should also use a distinct title element, identifying the page, and a distinct ID attribute in the opening tag for the body element.

The site will need to use a single CSS file for the general styling. JQuery plug-ins may use separate CSS files, if necessary, to keep things simple.

Again, for the user survey, you are trying to find out what your users think or know (etc.) about the topic of your site. Also: what they might contribute. You're trying to get fresh content from them that you can use for your site.

What you are NOT trying to get are (1) demographic information (age, gender, income, education, place of birth, etc.) or (2) site feedback (what you like, what you don't like, what to change). NONE of that.

The page should consist of a single FORM element, divided into three or more (labeled) fieldsets grouping related questions. Refer to the HTMLdog advanced form tutorial, the Duckett chapter on forms, and other resources. This page should use a variety of types of input rather than just one or two.

. . .

Notes on Visual Section

As you work on your visual section: Keep our discussion of the Letterpool London example in mind. Use the discussion to avoid the problems (the missing parts) that page exhibits:

  1. Introductory or "about" text (which, like the Letterpool example, can be on a separate page)
  2. Information about each image (which, other than the creator credit, the Letterpool page lacks): the more supplementary data the better.
  3. Organization: the Letterpool page presents a single grid of images. Consider how grouping and ordering, dividing the images and related content into several distinct groups and ordering the groups and the images within each group, will enhance the usability and usefulness of the page(s).

Interactivity, which the Letterpool page has (click on any of the images), is also a plus.

Here are some rough evaluation guidelines for the (final draft of the) visual section, using a gallery section as the example:

  • Low B or C level: A gallery with a sufficient number of good images (16 or more) that fit together, with minimal labeling but not much else.
  • High B or B level: A gallery with enough images, introduction, and supplementary information.
  • A level: As above but with effective grouping and ordering.

. . .

For next week (week 13): You'll need to add one additional page of essential content to your prototype (so not an about or contact page, or anything secondary like that).

Homework

Reading

Duckett. Re-read chapter 10, on design. Take a look at chapters 11 and 12, on working with Javascript. Take a look at appendixes D and F, on color names and special characters, respectively. These should prove useful.

Read Williams, on color.

Final Project

As noted above: you'll need to add one additional page of essential content to your prototype (so not an about or contact page, or anything secondary like that). Add the page. Integrate it into your site nav. Upload to your "prototype" folder.

Additional work TBA.

top

Week Eleven

Wednesday, Apr. 4
Where is the picture? A picture is on its way.

Announcements

Class Location

We meet in Loree 023. Start time is 11:10 am.

Work Due

EWP Slideshow

Complete and upload to your DRAFTS folder. Reply to the "EWP - Slideshow" link in the Class Forum.

First Visual Page for Final Project

Introduction, some supplementary text, at least nine images (if a gallery or collection of images). (Note: Your final version will need to have more images.)

Presentation, for now, can be a simple linear format. A more developed mode of presentation will be required for the final version.

Upload to your "drafts" folder. Supply a link a reply to the "First Visual Page" thread on the Forum.

Discussion

Proofreading, Troubleshooting, and Debugging

Many of the problems with markup and styling result, not from the wrong coding, but from typos, missing punctuation, missing closing tags, that sort of thing. We'll review some tactics and techniques for tracking these down. But beyond this: proofreading your code will be up to you (and any other pairs of eyes you can persuade to help you). If things aren't working on your page, assume a typing or similar error and locate the problem. More often than not, at least in the early stages, this will be the cause.

For the sake of demonstration: this page.

Grouping Images for Better Comprehension

We'll look at different modes of image grouping as ways for organizing visual content.

But let's first take another look at an example from last week, Letterpool London.

Also these two on reserve in case we need to look at them again:

Midterm Review/Discussion

We'll go over the graded midterms in some detail. Some pages to begin with:

Activities

EWP Slideshow Review

We'll check on your EWP slideshows to see if anything needs fixing.

Final Project Prototype: Review Page and Visual Section Workshop

Should we have time today: some workshopping of the review page of your final project.

Note: One of the things we'll need to do with this page is STYLE the table. To get started, take a look at this article of table design with CSS.

This will be part of your review page (at least initially) Essentially, you're finding and recommending SEVEN websites for visitors to your site to also visit and then providing links to these sites.

In terms of HTML, this will be a list. Each list item will contain the name of the site (or a phrase describing the site) in a heading. The name will also double as a link to the website. Then for the site, write three to four sentences telling your user the value of the website for their experience or enjoyment of the location. For example (on an LDP site devoted to Vorhees): "You've probably noticed that Vorhees has lots of trees. Want to climb them? TreeClimber covers the lastest climbing techniques and gear. Climb safely."

For an example of style and design for link blurbs, see Veerle's Approved list.

Here are additional guidelines:

  • Be specific in your link name. If you're linking to a page other than the home page of a website, then use the page title (or h1 content) or a modification of one of these rather than the global site name.
  • Focus on site features rather than the site topic. Telling your user how awesome Prince is when linking to a site about Prince is not very helpful. Instead, tell your users (Prince fans?) about the site's key features that would be of special interest to them.
  • The list of blurbs needs a good title; "Links" is not a good title. Give the list a title that goes with your location and/or that makes the list's function on your page clear to the user.
  • Good headings for the blurbs help.
  • Avoid really long URLs. Either "tinify" them or find a better link.
  • Avoid linking directly to downloads; link instead to the page offering the download; if you do link to the actual download, warn your user (specify the download type; e.g., "PDF").
  • Group related blurbs; at the same time, diversify your links. Nine links to nine magazine sites or nine art gallery sites is kind of boring.
  • Remember: you're blurbing about web places. So talking about how great, e.g., a museum is rather than about how great its website is will miss the point.
  • Where it works, you can include one or more secondary links/sub-blurbs within your main blurb. (E.g., EMC Twitter Page in a a blurb about the main EMC site.)

Related Exercise: Link Blurbs in a Floated Sidebar

More practice with floating elements. This time we'll use it to integrate your list of link blurbs more elegantly and efficiently into your layout. We'll create a sidebar, near the top of your content area, sidebars being a very common feature of many pages.

Use the following code as template. Note that I've modified it slightly from what outlined at the end of class. Partly, I've tried to bring it closer in format to the tutorial linked below. Again, you're basically dividing your "content" div into two parts, a "main" div for your review and a "sidebar" div for your blurbs.

The code for each blurb might then look something like this:

<li>
<h3><a href="URL" rel="external">site name</a></h3>
blurb text...
</li>

Here is a tutorial that shows one possible way of achieving simple 2 column CSS layout. Note: Some of the HTML and class and id names used in the tutorial will differ from those we use class. For instance, the "main" and "sidebar" divs in the tutorial need to go inside the "content" div used in our basic template. (As discussed in class, part of this exercise is to practice adapting code from a tutorial to the structure you're using for your own work.)

Homework

Reading

Duckett. Re-read chapter 10, on design. Take a look at chapters 11 and 12, on working with Javascript. Take a look at appendixes D and F, on color names and special characters, respectively. These should prove useful.

Read Williams, on color.

Final Project Prototype

The first prototype for the FP will consist of the following parts:

  • Home page
  • Revised review page with sidebar of seven link blurbs (etc.)
  • First visual section (expanded) (if a gallery, then 14-plus images with introductory text explaining the content and purpose of the page and captions identifying each image)
  • User survey page: nine or more questions, at least three of which should be multiple choice and three of which using options
  • One additional page of essential content (so not an about or contact page, or anything secondary like that)

The site will need to use a single CSS file for the general styling. JQuery plug-ins may use a separate CSS file, if necessary, to keep things simple.

Again, for the user survey, you are trying to find out what your users think or know (etc.) about the topic of your site. Also: what they might contribute. You're trying to get information that you can use.

What you are NOT trying to get are (1) demographic information (age, gender, income, education, place of birth, etc.) or (2) site feedback (what you like, what you don't like, what to change). NONE of that.

The page should consist of a single FORM element, divided into three or more (labeled) fieldsets of related questions. Refer to the HTMLdog advanced form tutorial, the Duckett chapter on forms, and other resources. This page should use a variety of types of input rather than just one or two.

Due in a new "prototype" folder inside your "425" folder by 9 PM, Thursday, Apr. 12. Post a link to this folder in a reply to the "FP Prototype" thread on the Class Forum.

Requirements covered in class. Check back later for more details.

top

Week Ten

Wednesday, Mar. 28
Where is the picture? A picture is on its way.

Announcements

Class Location

We meet in Loree 013. Start time is 11:10 am.

Work Due

Final Project: Short Reviews

1. Bring a printed copy of your two reviews and comparative table to class. About 450 words each (not including title and product information). Include a wordcount at the end of each review. Bring a printed copy to class. 12-pt SERIF font. 1.15 to 1.5 line-spacing. Double-sided printing is fine.

2. Upload the simple webpage presenting this content to your "drafts" folder. Then post a link to this page in a reply to the "Review Page" thread on the class forum.

EWP and LDP Midterm

Due online this Friday at 7 PM.

The LDP midterm should include the general project home page; the main page for your location; the grid gallery with fancyZoom functionality; your survey; and a contact page. You're welcome to add anything else to enhance the site.

The EWP midterm should include the homepage; the linear, grid with fancyZoom, and dynamic versions; and the feedback/survey/questionnaire (asking users to consider the different uses of the different modes of presentation).

The EWP sitenav should include links to the slideshow and interactive versions, although these pages won't be required for the midterm.

Discussion

Of Interest

Web ethics, aesthetics, and symbolism: Curator's Code.

Copyright and Fair Use (Continued)

Important resources: Take a look at the Center for Social Media on Fair Use and related Best Practices.

And a point of reference: a painting by Francis Bacon.

Visual Pages

Visual Page Examples:

The Atlantis page above uses Lettering.js, a jQuery plug-in.

Free and lovely science art and photo library: Conceptual Diagram Symbol Libraries.

Below is an interesting variation on the comparative timeline (see below) found in a magazine. This is the kind of thing that would not be out of place on a designer's or artist's portfolio site. (A few more visuals, of course, if it was to count as a visual page.) A timeline doesn't need to to measure in years or centuries. Scale your timelines to the topic of interest.

Comparative Timeline

Grouping Images for Better Comprehension

We'll look at different modes of image grouping as ways for organizing visual content.

Activities

LDP and EWP Homepages: Review

Review and revision workshop.

EWP Slideshow - Dynamic Gallery with Javascript

For this page, you'll develop a slideshow version of your EWP material that uses the jQuery framework and one of the numerous jQuery slideshow plug-ins. See, for instance, 15 jQuery slideshow/gallery plugins and 37 Fresh jQuery Image And Gallery Display Solutions.

Continue reading on the assignment page.

Review Page Workshop

Should we have time today: some workshopping of the review page of your final project.

Note: One of the things we'll need to do with this page is STYLE the table. Tutorials, models, and discussion for this on its way.

Homework

EWP Slideshow

Complete and upload to your DRAFTS folder. Reply to the "EWP - Slideshow" link in the Class Forum.

First Visual Page for Final Project

Introduction, some supplementary text, at least nine images (if a gallery or collection of images). (Note: Your final version will need to have more images.)

Presentation, for now, can be a simple linear format. A more developed mode of presentation will be required for the final version.

Midterm

Upload all the required EWP and LDP files to your "midterm" folder by Friday, March 30, 7PM. Then supply a link to this folder (or your midterm home page) in a reply to the "Midterm" thread on the Class Forum.

Once you've supplied the link, make no further changes to any of the files added to your midterm folder. If you need to make any changes, first get permission from the instructor. Changes made without written permission will result in the categorical non-passing of the work.

NOTE: Your "midterm" folder should include your design company homepage. Both the LDP and EWP page footers should contain credit/links to this page.

All your EWP pages should use a single CSS file. All your location-specific LDP pages should use a single CSS file. Your LDP homepage may use a separate CSS file.

You can either copy your image and JS files to your "midterm" folder or link to them in your "drafts" folder.

top

Week Nine

Wednesday, Mar. 21
Where is the picture? A picture is on its way.

Announcements

Class Location

We meet in Loree 023. Start time is 11:10 am.

Work Due

EWP and LDP Homepages

Make homepages for both projects. Upload to your "drafts" folder. Post links to both pages in a reply to "EWP and LDP Homepages" thread on the Class Forum.

Discussion

Of Interest

Things we can learn from: M.I.A. Takes on Anderson Cooper in Twitter Feud.

Dots used for the interactive index image demo. The code uses background image positioning to switch between the different states/colors of dot. The image can be replaced with alternative image(s).

Website example: Garen Ewing's Rainbow Orchard. Genre: web comic.

Visual Example: Tom Phillips, 20 Sites n Years

Designer Profile: Paul Rand. Lots to look at on this page. Note, in particular, how the images fit the width of the main column. Notice also the use made of the secondary column.

Other things on the web: Gabriel Florit's Water and the ChronoZoom project.

Copyright and Fair Use

Important resources: Take a look at the Center for Social Media on Fair Use and related Best Practices.

And a point of reference: a painting by Francis Bacon.

Proofreading, Troubleshooting, and Debugging

Many of the problems with markup and styling result, not from the wrong coding, but from typos, missing punctuation, missing closing tags, that sort of thing. We'll review some tactics and techniques for tracking these down. But beyond this: proofreading your code will be up to you (and any other pairs of eyes you can persuade to help you). If things aren't working on your page, assume a typing or similar error and locate the problem. More often than not, at least in the early stages, this will be the cause.

Grouping Images for Better Comprehension

We'll look at different modes of image grouping as ways for organizing visual content.

Activities

Midterm Folder Setup

In preparation for submitting the LDP midterm (after the break), you'll set up a new "midterm" folder in which you'll collect the final version of your LDP and associated files.

Once the folder is created, copy your (mostly still empty) LDP homepage into the folder. This file should have a name like "ldp_home.htm". Next: add a link to this file in your "midterm" folder in an edit of your post to the "Design Company" thread on the the Class Forum.

EWP – Dynamic CSS

We'll finishing working on the dynamic CSS gallery version of the EWP. As noted: Some useful concepts for controlling layout are encapsulated in the exercise.

LDP and EWP Homepages

Review and revision workshop.

Homework

Reading

Graphic designers are ruining the web

Edward Tufte, Envisioning Information, chapter 1 ("Escaping Flatland"). Available on Sakai, under Resources.

Final Project: Short Reviews

First work for the final project: write two short reviews of products (books, films, places, activities, events, etc.) that would be of likely interest to a user interested in the topic or focus of your final project website. The reviews should be of different kinds of thing: e.g., a book and an event but not two books or two events.

Look at the many short reviews on Amazon or the longer, more detailed reviews on sites such as CNET for guidance.

Each review should be accompanied by two images: (1) of the object under review and (2) of a metaphorical or similarly figurative association.

The images may be photographic, drawn, painted, digitally produced; but must be of your own creation.

Each review should be headed by a summarizing, headline style title, and basic product information (will depend on what is being reviewed: again look to models widely available on the web).

About 450 words each (not including title and producgt information). Include a wordcount at the end of each review. Bring a printed copy to class. 12-pt SERIF font. 1.15 to 1.5 line-spacing. Double-sided printing is fine.

Follow the review with a table comparing at least eight properties/features/facts about the two products. Try to be as diverse as possible.

Include all this content (two reviews with images plus the table) in a simple webpage. CSS is not required. Save page as "reviews.htm" or something like that. Upload to your "drafts" folder. There should be a forum thread requesting a link by the next class.

EWP and LDP Midterm

What is due, by when and where, in what order, etc., will be (have been) discussed in class.

top

Week Eight

Wednesday, Mar. 7
Where is the picture? A picture is on its way.

Announcements

Class Location

We meet in Loree 013, sadly the less pleasing of the two rooms. Start time is 11:10 am.

Work Due

Design Company Homepage

Make a homepage for a fictional design company. Represent yourself on this page as the principle desinger (or creative director) of the company.

First, read Kayla Knight's article for some guidelines. Then take a look at as many examples of design company pages as you can.

Upload your page to your "drafts" folder and post a link in the "Design Company" thread on the Class Forum.

Discussion

EWP Parts

I've modified the list of pages a little since we started. Below are the recommended link names (for the site nav buttons), file names, and body ide attributes for the pages (seven in total). I'm renaming the "feedback" page as "Survey" because that label better describes its function within the project. I'm also dropping the separate designer/author page, since we'll integrate its content into the home page.

My recommendation, then, is to update your material in accordance with the table's breakdown. Or, at least, to keep things consistent.

PageFile nameBody id attribute
Homeewp_home.htmhome
Linearewp_linear.htmlinear
Gridewp_grid.htmgrid
Dynamicewp_dynamic.htmdynamic
Slideshowewp_slide.htmslide
Interactiveewp_interactive.htminteractive
Surveyewp_survey.htmsurvey

Once we've completed the dynamic page, we'll work on the home page, which'll probably become a separately graded entity. We'll get to the jQuery intensive slideshow and interactive pages after the break.

My recommendation, then, is to update your material in accordance with the table's breakdown. Or, at least, to keep things consistent.

PageFile nameBody id attribute
Homeldp_home.htmhome
About, Overview, etc.ldp_main.htmmain
Galleryldp_gallery.htmgrid
Surveyldp_survey.htmdynamic
Contactldp_contact.htmcontact

A link to an external designer page will be integrated into the site but not as part of the site navigation (since the design company homepage, while part of the assignment, is not really a part of the LDP site itself [the LDP being only one of the many fine projects your company has pursued in its recent history]).

Project Ideas Review

Further discussion of final project ideas via the Class Forum.

LDP Design and Content Review

We'll look at the latest iteration of your project via the Class Forum.

Proofreading, Troubleshooting, and Debugging

Many of the problems with markup and styling result, not from the wrong coding, but from typos, missing punctuation, missing closing tags, that sort of thing. We'll review some tactics and techniques for tracking these down. But beyond this: proofreading your code will be up to you (and any other pairs of eyes you can persuade to help you). If things aren't working on your page, assume a typing or similar error and locate the problem. More often than not, at least in the early stages, this will be the cause.

Web Typography

As noted last week: good typography is essential to the success of any web page, site, or service. With reference to the special typography reading for this week, we'll spend a little time on the subject.

Home Page Design

Here, again, is an example of a design company home page: MetaLab. And another: Voll.

And here is another example: Veerle's Blog 3.0.

Activities

Midterm Folder Setup

In preparation for submitting the LDP midterm (after the break), you'll set up a new "midterm" folder in which you'll collect the final version of your LDP and associated files.

Once the folder is created, copy your (mostly still empty) LDP homepage into the folder. This file should have a name like "ldp_home.htm". Next: add a link to this file in your "midterm" folder in an edit of your post to the "Design Company" thread on the the Class Forum.

EWP – Dynamic CSS

We'll finishing working on the dynamic CSS gallery version of the EWP.

LDP and EWP Homepages

At last: we get to really working on these.

First, with the EWP in mind, let's take a second look at the design of Veerle's Blog 3.0.

Next, with the LDP in mind, let's take a look at the Cape Town Postcard Map Project. Here is a simplified interactive map demo I've adapted from the preceding example.

Homework

Reading

TBA

EWP and LDP Homepages

Make homepages for both projects.

EWP Homepage

As covered in class, base your design on the structure of Veerle's Blog 3.0. Your page should include site title and logo; sitenav; three preview links consisting of heading, preview image, and page description; a descriptive headline summarizing the site's purpose; introductory text explaining the purpose of the site in more detail; and a footer with credit, copyright, and sponsor information. (The footer is where you link to your design company home page.)

Upload to "drafts". Post link in reply to "EWP - Homepage" thread on the Class Forum.

LDP Homepage

This page should introduce users to the CLASS project (not to your individual LDP). That is: it should explain what all the LDP pages are doing together and, ultimately, link to each of them.

As covered in class, your LDP homepage should make use of the interactive image script used on the Cape Town Postcard Map Project. However: use the simplified (and better-labled) demo version as your model.

The demo uses a map as its central organizing. You're welcome to use a map as well, but, if so, it should be an old or unusual map. Using a screenshot of Google maps or any other digital map is not allowed.

Instead of a map, you may use a scenic photograph or some kind of non-photo image to illustrate and organize the page.

Images of your own production, where successful and appropriate, always get more credit.

Inaddition to the interactive image with links, your page should include a site title and logo; backup sitenav (a list repeating links to the locations); a descriptive headline summarizing the site's purpose; introductory text explaining the purpose of the site in more detail; and a footer with credit, copyright, and sponsor information. (The footer, again, is where you link to your design company home page.)

Make one. Upload to "drafts". Post link in reply to "LWP - Homepage" thread on the Class Forum.

top

Week Seven

Wednesday, Feb. 29
Where is the picture? A picture is on its way.

Announcements

Important Message about This Week's Class and Homework

Due to your instructor's "compromised state," this week's class is cancelled. HOWEVER: (1) the homework for this week is still due; and (2) there is new work assigned for next week.

The main work for next week is to prepare a home page for your fictional design company (the company fictionally responsible for developing the location documentary project). See below for more information on both the homework for next week and the work due this week.

Next week's class will be a busy one so get plenty of rest.

Work Due

EWP

1. Completed zoom version of the grid page. Upload to your "drafts" folder.

Note: The "Grid" link in your EWP site nav should link to this most recent version of the grid layout, not to your old, non-zooming version.

2. A draft of the dynamic CSS gallery version of the EWP. Ideally, it works. If not, then not. But at least have the HTML and images set up. Then we can review any problems in class. (Again: I've revised the intstructions a bit since class).

Whether working or not, upload the page to your "drafts" folder and make sure that the site nav on all the pages links correctly to this page.

3. An EWP Feedback page. The feedback page should contain a form element and its sub-elements in the "content" div. The form should ask your user questions about the different ways that the EWP presents the material. Ask them to explain the different advantages and disadvantages of the different layouts and modes of presentation. Combine text answer questions with other kinds (checkbox, multiple choice). Consider enhancing your questions with visual material: screenshots, diagrams of the different layouts.

Complete and upload to your "drafts" folder.

LDP Diagram

When finished: Add the diagram to your main LDP page. give the diagram its own section. Preface the diagram with descriptive heading. And complete the section with a caption explaining the diagram and its value for the page (the purpose it is intended to serve).

Discussion

EWP Parts

I've modified the list of pages a little since we started. Below are the recommended link names (for the site nav buttons), file names, and body ide attributes for the pages (seven in total). I'm renaming the "feedback" page as "Survey" because that label better describes its function within the project. I'm also dropping the separate designer/author page, since we'll integrate its content into the home page.

My recommendation, then, is to update your material in accordance with the table's breakdown. Or, at least, to keep things consistent.

PageFile nameBody id attribute
Homeewp_home.htmhome
Linearewp_linear.htmlinear
Gridewp_grid.htmgrid
Dynamicewp_dynamic.htmdynamic
Slideshowewp_slide.htmslide
Interactiveewp_interactive.htminteractive
Surveyewp_survey.htmsurvey

Once we've completed the dynamic page, we'll work on the home page, which'll probably become a separately graded entity. We'll get to the jQuery intensive slideshow and interactive pages after the break.

Activities

. . .

Homework

Reading

Kayla Knight, Essential Tips for Designing an Effective Homepage.

Lee Munroe, Essential Tips for Designing an Effective Homepage.

Design Company Homepage

Make a homepage for a fictional design company. Represent yourself on this page as the principle desinger (or creative director) of the company.

First, read Kayla Knight's article, linked above, for some guidelines. Then take a look at as many examples of design company pages as you can.

Here is an example of a fairly straightforward design company home page: MetaLab. Here is a fancier one: Voll.

The page you design should have among other features:

  • Company name and logo
  • Site navigation (since the HP is the only page you're making the links are not expected to work)
  • A sidebar or other feature with your image and a short professional bio.
  • List and/or description of recent projects
  • Optimally readable typography (refer back to this week's special reading)
  • Good use of the footer

Zoomify LDP Grid

You don't need to do this by next week. However: the final version of the gallery page will need to incorporate the FancyZoom functionality (or its equivalent).

top

Week Six

Wednesday, Feb. 22
A picture is on its way.

Announcements

Meeting Time and Place

This week we're back in Loree 023, where we'll remain until early March. Start time is 11:10 am.

Work Due

EWP: Grid

Complete the grid version with beginner CSS and intermediate CSS styling and site navigation. Upload to your "drafts" folder. You should now have two versions there: the linear version saved as "ewp_linear.htm" and the new grid version, saved as "ewp_grid.htm". You should also have the mostly blank home page, "ewp_home.htm," and site nav linking all three pages.

Note: Re-save older versions with numbers (or distinguishing names, such "ewp_linear_old.htm"); use the unnumbered file names for the current versions. Keep all versions in your "drafts" folder.

LDP

Note: The instructions for this part of the homework have been clarified a bit in light of what was said in last week's class, so I repeat them here in full.

1. Gallery: A web page presenting a static grid format image gallery. Use your nine DETAIL images and associated short captions (edit these as needed). You should have the images in both preview and large sizes. Build a gallery page using these images. Model the page on the EWP grid gallery we built in class. Add a short introductory section that will help users to understand what they are looking at and the role of the page in the project (e.g., if they come to this page without reaching it via the main page). Finally, add site navigation (see below).

2. Survey Questions: Prepare six or more questions. These should not be biographical or demographic questions (name, age, place of birth, etc.) or polar (yes/no) questions. You're trying to discover what people think about the location, what they do there, how it fits practically into their lives. Also: what they know or have noticed about the location that others might not. Try to make the questions as specific to the location as possible. E.g., possibly ask them questions about particular features of the place or particular activities.

3. Survey: Interview at least four people who use the location. Ask them the questions you prepared above. Take their photos. Add the questions, responses, and photos to a new "Survey" page for your LDP site. Add a short introduction explaining the purpose of the page and when and where the questions were asked. Upload the finished page to your "drafts" folder.

4. Site Navigation: The Gallery and Survey sections will each have their own page. Add links to these pages to the site navigation, so that you'll now have links to four pages: Home, Location (the main page), Gallery, and Survey. Add links for two additional pages: Designer and Contact (we'll get to making these page in the next week or two).

Note: Use the float method to style the site nav horizontally.

When all this is done and uploaded to your "drafts" folder, post a link to the HOME page (more or less blank save for the header with name and sitenav) in a reply to the "LDP - Second Draft" thread on the Class Forum.

Discussion

Copyright and Related Matters

We'll refer to the intellectual property reading for this week and begin a series of conversations on copyright, plagiarism, and related matters.

Extra reference: Stanford Copyright & Fair Use Center.

Project Ideas Review

Discussion of early project ideas via the Class Forum.

Some sample projects:

Activities

Taking Credit for the EWP

You'll add a "byline" div or p to your EWP.

A Little More with the Floating

Floating methods and peculiarities demonstrated on demand as needed (or not).

Here are the miserable remnants of last week's float demo.

End of the World Project - Static Grid with FancyZoom

Before proceeding to the next version of the EWP gallery, we'll enhance the static grid version with jQuery and the FancyZoom script. This replaces the "enlarged" link method with something a bit – fancier.

This will be a new, official version of "ewp_grid.htm". So before you start: Save the current version (completed for this week) as "ewp_grid_old.htm", or something like that. Then re-open "ewp_grid.htm" and follow the demo.

1. To begin: you'll need to add the "fancyzoom.js" script to your "js" folder and a link to this script in the HEAD of your HTML file.

<script type="text/javascript" src="js/jquery.js"></script>
<script type="text/javascript" src="js/fancyzoom.js"></script>
<script type="text/javascript" src="js/basic.js"></script>

2. Don't forget to credit the fancyZoom script.

This gallery uses Steve Smith's jQuery-adapted version of FancyZoom. The code was accessed via http://orderedlist.com/blog/articles/fancyzoom-meet-jquery/ on [current date].

Include the credit information both in an HTML comment near the start of your "gallery" div and in a p element in the "footer" div of your EWP grid page.

3. Next, modify the HTML structure for each of your "figure" divs. As with the plain static grid, each "figure" div contains the preview size image contained inside a link. However, whereas the link in the previous version is to the large size version of the image, the link in the zoom version is to an element located in the same file (i.e., a div on the same page identified by a unique id attribute).

<div class="figure">
      <a href="#ewp1"><img src="images/ewp/ewp_01_prev.jpg" alt="Falling" title="Click to see larger view" /></a>
     <p><span>Image title</span> Three word caption.</p>
</div>

Note: The rel attribute (="enlarged")is no longer included in the link. Be sure to remove this attribute from your code to avoid a conflict with new script.

A few feaures to look at here: (1) id (#) link in the anchor element; (2) the new title attribute in the anchor element; and (3) the span element in the caption.

4. With the "figure" div set up, the next step is to add the divs that contain the large size images. Add these after the closing tag of the "gallery" div.


<div id="ewp1">
     <img src="images/ewp/ewp_01_large.jpg" alt="Falling 1" />
     <p><span>Image title</span> Five or more word caption.</p>
</div>

Note: You may want to enclose this second group of images in a single "zoom-figure" div to help keep your HTML organized. As for styling the large images, keep in mind that the script adds id attributes when the zoom takes effect. We'll use Firebug to understand what happens when it does.

5. Next, add the follow script to the HEAD of your HTML file. This activates the zoom script.


<script type="text/javascript">
     $(document).ready(function() {
          $('div.figure a').fancyZoom({scaleImg: true, closeOnClick: true});
          });
</script>

Location Documentary Project Design

You should now a good bit of diverse content across several pages. The next thing to do is work on the design.

Start with fixing the HEADER. Then:

  • Body background: darker than wrapper color
  • Fonts: must use a font stack with fully styled typography, not the browser default
  • Wrapper width: 900px
  • Wrapper (or content div inisde wrapper) should have padding
  • Wrapper color: white or near white
  • Wrapper should be centered inside body
  • All images need to be saved at (or very close to) their display size.

Hover state of links should NEVER change the layout of the links (as they do on this page [unless the problem has been fixed]).

CRAP for LDP Survey

Establishing the visual logic of the survey through design will give us a chance to put the CRAP principles to work in resolving a specific presentation problem.

First, let's look at an example of survey design from one of the LDPs.

Example of survey
Example of survey

Next, take a look at this (similar) example from the world of print: Rolex Awards for Enterprise

Next, let's go over this CRAP principles design demonstration based on the Rolex Awards example above.

Finally, let's apply this to one of the LDP surveys.

Example revised of survey

Revised survey item design

Example of revised survey

Revised survey layout design (A)

Example of revised survey

Revised survey layout design (B)

Homework

Web Typography Reading

Code Style: Build better CSS font stacks

Ross Shannon, Web Typography (overview)

Oliver Reichenstein, Web Design is 95% Typography

Michael Owens, 6 Ways To Improve Your Web Typography

Other Reading

Duckett, Beginning HTML, TBA.

EWP

Complete the zoom version of the page.

Have a go at building the dynamic CSS gallery version of the EWP (I revised the intstructions a bit since class). If you get it to work, that's excellent. If not: at least have the HTML and images set up. Then we can review any problems in class.

Add a feedback page. The feedback page should contain a form element and its sub-elements in the "content" div. The form should ask your user questions about the different ways that the EWP presents the material. Ask them to explain the different advantages and disadvantages of the different layouts and modes of presentation. Combine text answer questions with other kinds (checkbox, multiple choice). Consider enhancing your questions with visual material: screenshots, diagrams of the different layouts.

LDP

Location diagram. Make a diagram of the location. Draw by hand or machine. Indicate on the diagram the locations of objects and views depicted in your photographs. (A main purpose of the diagram is to help your user understand the spatial relations between what the photographs depict.)

The diagram should be in landscape orientation and approximately as wide as the content area (i.e., take advantage of the space to make the diagram as legible as possible).

For general advice on making good diagrams, refer to Google.

When finished: Add the diagram to your main LDP page.

top

Week Five

Wednesday, Feb. 15
Week Five

Announcements

Meeting Time and Place

This week we're back in Loree 013, the room in which we met two and three weeks ago. Start time is 11:10 am.

Next week and the week after we'll be back in 023.

Work Due

Quine + CSS 2

Complete the work started in class. Be sure to work through the CSS intermediate tutorial at HTML Dog. Again: the challenge is to add as much CSS to the pages as you can. Upload all files to your "drafts" folder. Post a link to the home page in a reply to the "Quine + CSS 2" thread on the Class Forum.

NOTE: The Quine pages should retain the working site navigation and jQuery-enabled external link behavior we worked on in class.

Location Documentary Project

Complete a first draft of this project page. As with other work, start from the basic HTML template. Create and link to an external CSS file ("ldp.css"). Fill in the title and h1 elements and proceed from there.

Organize your page into sections with h2 and even h3 elements labeling each section. Use the "figure" div pattern for your images. None of your images should be on its own. That is: Each image should be inside a "figure" div with a caption identifying the content of the image.

Upload your files to the "drafts" folder and post a link to the "LDP - first draft" thread on the Class Forum.

Project Ideas

Respond to the "Project Ideas" thread on the Class Forum.

Discussion

Copyright and Related Matters

We'll refer to the intellectual property reading for this week and begin a series of conversations on copyright, plagiarism, and related matters.

Extra reference: Stanford Copyright & Fair Use Center.

Project Ideas Review

Discussion of early project ideas via the Class Forum.

HTML Review

To review: A sample bio page with problematic lists.

Quine and LDP First Draft Review

We'll take a look at your work via the Class Forum.

We'll use some of your pages to discuss the application of the CRAP principles to specific design tasks.

Activities

Floating Demo

A quick demonstration of the utility and peculiarities of the FLOAT property.

Project Home Pages

Basically a review/rehearsal of what we worked on last week. Create preliminary home pages for your EWP and LDP sites ("ewp_home.htm", "ldp_home.htm"). Use the basic HTML template. Add title, h1, CSS and JS links, "home" ID for the body, and site navigation with the "current" ID for the home page link. Leave the "content" div on each page empty for now. You'll be filling those in soon.

End of the World Project - Static Grid

So far you've completed a basic linear version of the EWP, part two of the project assignment. We'll tweak this a bit further by adding footer content) and go over any problems you might have so far.

Next, we'll move on to the static grid version of the project, which uses CSS for its layout.

You should have the "ewp_grid.htm" you made last week. It should still have linear page content and look like the linear page. But that will change. You should now have three distinct HTML files: "ewp_linear.htm," "ewp_grid.htm," and "ewp_home.htm". (If you need to keep extra drafts of these, give the other drafts numbers. The names of your main [ie., most up-to-date] versions should remain number-free.)

Note: Feel free to divide your "images" folder into sub-folders (e.g., "ldp," "ewp") in order to keep your images separate.

Location Documentary Project

If there is time ...

Homework

Reading: Focus on Layout

Duckett, Beginning HTML, chapter eight, page 340 and on, and chapter nine. They cover layout and positioning.

EWP: Grid

Complete the grid version with beginner CSS and intermediate CSS styling and site navigation. Upload to your "drafts" folder. You should now have two versions there: the linear version saved as "ewp_linear.htm" and the new grid version, saved as "ewp_grid.htm". Re-save older versions with numbers; use the unnumbered file names for the current versions. Keep all versions in your "drafts" folder.

LDP

1. Gallery: A web page presenting a static grid format image gallery. Use your nine DETAIL images and associated short captions (edit these as needed). You should have the images in both preview and large sizes. Build a gallery page using these images. Model the page on the EWP grid gallery we built in class. Add a short introductory section that will help users to understand what they are looking at and the role of the page in the project (e.g., if they come to this page without reaching it via the main page). Finally, add site navigation (see below).

2. Survey Questions: Prepare six or more questions. These should not be biographical or demographic questions (name, age, place of birth, etc.) or polar (yes/no) questions. You're trying to discover what people think about the location, what they do there, how it fits practically into their lives. Also: what they know or have noticed about the location that others might not. Try to make the questions as specific to the location as possible. E.g., possibly ask them questions about particular features of the place or particular activities.

3. Survey: Interview at least four people who use the location. Ask them the questions you prepared above. Take their photos. Add the questions, responses, and photos to a new "Survey" page for your LDP site. Add a short introduction explaining the purpose of the page and when and where the questions were asked. Upload the finished page to your "drafts" folder.

4. Site Navigation: The Gallery and Survey sections will each have their own page. Add links to these pages to the site navigation, so that you'll now have links to four pages: Home, Location (the main page), Gallery, and Survey. Add links for two additional pages: Designer and Contact (we'll get to making these page in the next week or two).

Note: Use the float method to style the site nav horizontally.

When all this is done and uploaded to your "drafts" folder, post a link to the HOME page (more or less blank save for the header with name and sitenav) in a reply to the "LDP - Second Draft" thread on the Class Forum.

top

Week Four

Wednesday, Feb. 8
Four

Announcements

Meeting Time and Place

This week we're back in Loree 023, the room in which we met for the first class. Start time is 11:10 am.

Work Due

Location Documentary Project: Prep

Complete the preparatory work for the Location Project. Combine your material in a single Word document, upload a PDF version to your "hw" folder, and bring a printed copy to class.

Images in the document can be small in the printed version, to save ink and paper, and double-sided, black-and-white printing is fine.

Finally, bring all your files (text and images) to class. If we have time, we'll start putting together a draft of the LDP page.

Applying CSS to the Quine Page

Complete the work started in last week's class. Upload all files to your "drafts" folder. Post a link to the page in a reply to the "Quine + CSS 1" thread on the Class Forum.

Discussion

Copyright and Related Matters

We'll refer to the intellectual property reading for this week and begin a series of conversations on copyright, plagiarism, and related matters.

Extra reference: Stanford Copyright & Fair Use Center.

CSS Introduction, Part Two

CSS example: Page with CSS. And here is another: Yvette's Wedding Dresses.

You can think of the web page structure as a series of smaller boxes inside larger boxes (body and head inside html, paragraph inside body, table cell inside table row inside table, etc.) and boxes in a stacked order or succession (e.g., one paragraph following another paragraph following a table, etc.).

Each box on the page, in turn, consists of a further series of boxes:

W3 Schools Box Model Diagram. Source: guiStuff.

Note: Elements inside the body element divide between block-level and inline elements.

Activities

Adding Simple JavaScript

We'll use jQuery framework and some simple JavaScript to get external links (those with the rel="external" attribute) to open in a new tab/window.

  1. Create a "js" folder on the desktop (or in whichever folder you're using on your local machine).
  2. Download jQuery (the "production," i.e., "minified" version); save "jquery.js" file in "js" folder. Note: Click the download button. Copy and paste the code into a new Notepad file. Save the file as "jquery.js" in your "js" folder.
  3. Save a new Notepad file as "basic.js" in "js" folder.
  4. Then add the following code (script) to your "basic.js" file and save.
    // open rel = external links in a new tab/

    $(document).ready(function() {
       $('a[rel="external"]').click( function() {
         window.open( $(this).attr('href') );
         return false;
       });

       $('a[rel="enlarged"]').click( function() {
         window.open( $(this).attr('href') );
         return false;
       });
    });
  5. Next: Add these two script elements (the code below) to the head of your current LDP and EWP drafts.
    <script src="js/jquery.js" type="text/javascript" ></script>

    <script src="js/basic.js" type="text/javascript"></script>
  6. Test your links. The external links and enlarged images should open in new tabs rather than in the same tab as the linking file.
  7. Upload your new "js" folder and your updated LDP and EWP files to your "drafts" folder on Eden.

Applying More Content and CSS to the Quine Page(s)

We'll work from the expanded Quine exhibition home page we conmtinued to revise last week.

First, we'll set up a site navigation menu for a Quine exhibition web site. Essentially, this is an unordered list (ul) containing relative links to other pages. Because it's a site-level (rather than page-level) feature, it should be located in the "header" div rather than "content" div on the page.

We'll then make a second page, in order to test the site nav. Then, we'll add some new styling using CSS. Among other things, we'll look at two different ways to style and organize the site navigation. We'll stick with the second method, but it's important to understand both methods, which can be applied to many design tasks beyond the site nav.

We'll use the site nav styling to consider some important applications of the CRAP principles covered in the reading for this week.

After the demo, there'll be a CSS workshop. During this, work on completing the CSS intermediate tutorial at HTML Dog, again working with your Quine page(s).

Location Documentary Project

If we have time, we'll; start building a first draft of this page in class. As with other work, start from the basic HTML template. Create and link to an external CSS file. Fill in the title and h1 elements and proceed from there.

Organize your page into sections with h2 and even h3 elements labeling each section. Use the "figure" div pattern for your images. None of your images should be on its own. Each should be inside a "figure" div with a caption identifying the content of the image.

Homework

Reading: Focus on Design

Duckett, Beginning HTML, chapters 9 and 10.

Read again: Williams, Non-Designer's Design Book, chaptes 1-6.

Quine + CSS 2

Complete the work started in this week's class. Be sure to work through the CSS intermediate tutorial at HTML Dog. Again: the challenge is to add as much CSS to the pages as you can. Upload all files to your "drafts" folder. Post a link to the home page in a reply to the "Quine + CSS 2" thread on the Class Forum.

Location Documentary Project

Complete a first draft of this project page. As with other work, start from the basic HTML template. Create and link to an external CSS file ("ldp.css"). Fill in the title and h1 elements and proceed from there.

Organize your page into sections with h2 and even h3 elements labeling each section. Use the "figure" div pattern for your images. None of your images should be on its own. That is: Each image should be inside a "figure" div with a caption identifying the content of the image.

Upload your files to the "drafts" folder and post a link to the "LDP - first draft" thread on the Class Forum.

Project Ideas

Respond to the "Project Ideas" thread on the Class Forum.

top

Week Three

Wednesday, Feb. 1
One

Announcements

Meeting Time and Place

We meet this week once more in the Loree 013 lab, starting at 11:10 am. Next week it's back to the old room.

Work Due

Linking Questions

Turn in a PRINTED copy (not handwritten) of your answers to the Linking Questions. Note: Duckett, chapter 2, part of the reading for this week, covers linking. Additionally, you may use the abundant resources of the web for guidance.

Remember that late work for this assignment will NOT be accepted.

End of the World Project

Complete Part One (PDF version) and Part Two (linear version) of the End of the World Project (EWP).

For Part One, prepare a PDF containing your title, introductory text, nine images, and associated captions. Save a copy of this PDF in your "hw" folder on Eden and bring a printed copy for the instructor.

Note: You can make a PDF file from any document in MS Word.

For the linear version, save the completed HTML page and images in your "drafts" folder on Eden. Then post a link to your page in a reply to the "EWP - Linear" thread on the Class Forum.

Discussion

Linking Review

Linking is VERY important. We'll review some linking essentials, as covered in the Duckett reading for this week, in going over the Linking Questions. Not to be missed!

EWP Linear Gallery Review

We'll take a preliminary critical look at the first web version of your EWP.

And another look at a further bio page or two.

CSS Intro

First, I'll introduce some basic CSS concepts – in particular, the basic CSS syntax and the concept (and some methods) of selection. Then we'll move on to a demonstration of applying CSS to an HTML file and a related exercise.

For the demonstration, we'll use the Quine exhibition page we revised last week. View the source in Firefox (Ctrl + u); copy the code into a new Notepad file; and save as "quine_home.htm". Copy the image of Quine from the page to an "images" folder or use one of your making or discovery.

Next: We'll add some basic CSS to the page and then you'll have a chance to try this on your own. Then we'll add some more HTML (specifically, a site navigation menu). And then we'll apply some CSS to this added HTML.

To add CSS:

  1. Open a new Notepad file and save the file as "quine.css".
  2. Modify the LINK in the HEAD section of the "quine_home.htm" file so that it links to the new CSS file: i.e., change the default value in the existing link from "no.css" to "quine.css").

  3. Now we're ready to begin styling.

Activities

Applying CSS to the Quine Page(s)

Following the CSS demo (above), practice applying some basic CSS of your own. To help with this, follow the CSS Beginner tutorial at HTML Dog.

As part of this exercise, you'll need to add some more features to the page. In particular: add five or more external in-text (hyper)links to the main introductory text. Give each link a rel="external" attribute as demonstrated above.

When you're finished applying CSS (as much as you can), upload your version of "quine.htm," "quine.css," and any associated image files to your "drafts" folder.

. . .

Note: HTML Dog covers three ways to apply CSS to your HTML file. For this assignment, you'll use an EXTERNAL file (i.e., drafts.css) that you'll link to from the HEAD of each of your html files.

Following HTML Dog, you'll add styling to your body, paragraphs, headers, table, list, etc. Add text styling, color, margins, padding, and borders to the elements of your page. Try to get your page to look distinct but also clean and readable.

For a list of Common Fonts and other useful font-related material, see the Font Resources at Browser News.

For a quick one-page reference, here is a CSS Cheat Sheet.

Homework

Reading: Focus on CSS and Design

Duckett, Beginning HTML. Read chapter 7 (on CSS). Then read chapter 8 (more CSS) as far as page 337.

Williams, Non-Designer's Design Book, chapters 1-6. These chapters introduce us to the mighty (simple) "CRAP principles" – Contrast, Repetition, Alignment, and Proximity – by which we can make our pages look good, or at least a lot better, with relative ease.

Special Plagiarism, Copyright, & Intellectual Property Reading

Review the Writing Program's plagiarism policy and the Business and Technical Writing Program plagiarism guidelines.

Browse: U.S. Copyright Office

Location Documentary Project: Prep

Complete the preparatory work for the Location Project for next week. Survey your site; write the text; take the fifteen photos and edit them as needed. Then combine in a document, upload a PDF version to your "hw" folder, and bring a printed copy to class. Images can be small in the printed version, to save ink and paper, and double-sided printing is fine.

No web page for the LDP is required for next week. Just the words and pictures. However: bring all your files (text and images) to class. If we have time, we'll start putting together a draft of the LDP page.

Update: Applying CSS to the Quine Page

Complete the work started in this week's class.

Follow the CSS Beginner tutorial and apply as much of the beginner-level CSS to the Quine page as you can. Don't worry about aesthetics or design. We'll get to that next week. For now, work at familiarizing yourself with the CSS, with what it can do to the HTML file.

If you have problems applying the CSS, check that your HTML file is linking to your CSS file. Check for any typos (esp. mispelled selectors or properties and missing brackets or semi-colons). Also, remember that you can use the Firefox error console (Cmd/Ctrl + Shift + J) to check for (some) errors.

When you're finished applying CSS, post a link to the page in a reply to the "Quine + CSS 1" thread on the Class Forum.

top

Week Two

Wednesday, Jan. 25
Week Two Image

Announcements

Meeting Time and Place

We meet this week in the Loree 013 lab, starting at 11:10 am. We're scheduled to meet in this same location next week as well, then back in room 023 the following week.

New Students

If you missed the last class, (1) identify yourself; (2) speak to me before you leave today; and (3) be sure to review the course description and policies. Note also that you'll need to catch up on any missing work by the next class.

Work Due

Class Forum

Reply to the "Introductions" thread on the Class Forum.

Bio Page

Complete the first draft of Bio Page. Make sure that all the required content is there. Do your best with the HTML. If things don't work out with the coding, at least have all the content (the text, the images, the headings, etc.) and your best attempt at coding in a file. Do not show up with nothing.

Bring all the files associated with this page to class (via flash drive or email or whatever method works for you). These should include the HTML file and all the images you use for the page. We'll move these onto the Web as part of this week's class.

Discussion

Of Interest

The photographic work of Stephen Gill can give a good sense of the types of images that work well for the End of the World project (see the homework section for this week). See in particular his book in newspaper format, The Hackney Rag (Artbeat, 2009).

Technical Policies for Web Authoring

We'll briefly go over again the basic technical policies for the web authoring course.

To illustrate the file and folder name policiy, a wee table:

Naming Rules: Bad vs. Good
Rule Bad Good
No caps Bio.htm
BIO.htm
mypic.JPG
MYPIC.JPG
bio.htm
mypic.jpg
No blank spaces bio page.htm
my bio page.htm
biopage.htm
bio_page.htm
my_bio_page.htm
Clear, descriptive aaa.htm
pic1.jpg
page1.htm
small_1.png
big_pic.gif
bio.htm
contact.htm
moose_small.jpg
moose_big.jpg
Compact first_bio_age_by_jason_wilson_bartolamy_jan_19_2012.htm bio_page.htm
bio.htm

Storing, Sharing, and Managing Your Work

We'll go over the following:

  • Linking files: Links and Hyperlinks – VERY IMPORTANT
  • Disk Spaces: The difference between local disk space and remote disk space
  • Transfering files: between local and remote spaces (FTP) using the SSH client or a Mac equivalent
  • File and Folder Properties > Permissions

Following this, we'll set up folders on Eden in which to store and share your web work.

Activities

Important Preliminary Note

If you are new to this, then work on a PC rather than a Mac in class. All demonstrations in class will use a PC and, in most cases, PC-specific software. We have much to do in class and the instructor will not have time to help you with Mac-specific problems (e.g., saving files properly in TextEdit or transfering files using Fugu or Cyberduck).

SSH, FTP, and Folders

First, if you haven't done so yet, save/copy your Bio Page homework (the HTML file and all your images) to your local desktop (i.e., the desktop of the machine you're using today in class), and open the HTML file in Notepad.

Next, if you haven't done so already, then create an "images" folder on your local desktop for storing your images. Move all your images (i.e., image files) into this new folder, and, as needed, update the SRC links in your HTML file to reflect any change in the image files location. For example, if your HTML code looked like this:

<img src="work_photo.jpg" alt="Photograph of Jane Doe" />

then, once you've moved your image into the "images" folder, you'll need to change the HTML to this:

<img src="images/work_photo.jpg" alt="Photograph of Jane Doe" />

That way, you instruct the browser to look inside the folder named "images" for your image files (where they should all be at this point).

Once you've made these changes, save your file and then re-save the file ("File > Save as") as "bio_01.htm". This new file is going to be your first draft, saved for later reference, and should not be altered.

Next, close "bio_01.htm" and re-open your original file ("bio.htm" or whatever you've named it). This is the version you'll keep working on today in class (and possibly beyond that).

Using the SSH application, we'll set up folders on Eden for storing and displaying course work. First, I'll demonstrate the process for setting up the folders using the SSH software. Then you'll set up your own folders by following the linked SSH tutorial.

Remember the naming rules!

Once you have the folders set up, upload your Bio Page homework to your new "drafts" folder. Be sure to upload "bio_01.htm", "bio.htm," and your (new) "images" folder. Once you've uploaded the files to Eden, check that they can be viewed on the web. If you go to the URL for either page and the browser window says "FORBIDDEN," you'll need to reset the permissions for either the file or one or more of the encompassing folders to "755".

Next, respond to the "Bio Page" thread on the Class Forum. This is where you'll supply a link to your page so that the instructor and others can access the page. Be sure to check the link(s) before logging out.

Remember that a link to your work needs to be posted in the correct thread in the forum. If the link to your work is missing (or if it doesn't work), your assignment will count as NOT submitted.

Bio Page / HTML Review

Now that you've successfully submited your work via the Class Forum, we'll take a look at a few of your pages – paying attention to (1) how well they meet the content requirements and (2) how well the implement the HTML.

As needed, we'll review the process of putting together a basic bio page. This will give us a chance to go over some HTML basics in more detail than we did last week.

Since image display problems tend to be among the most common on early web pages, we'll take a look at some techniques for fixing your images: both getting them to display and getting them to display properly (or optimally, or reasonably close to that).

If any of your images fail to display, refer to this image display problem checklist.

If your images successfully display, there are still a few things we'll need to check – namely, size, scale, quality, and proportions. To help us to go over these points, we'll use this sample Bio Page: 500 words about Me.

More with Quine

Depending on how much time remains, we'll return to our Quine exhibition website example from last week and begin to take it a bit further. This will become the first stage a continuing exercise that we'll use to practice and expand our use of HTML as well as introduce CSS and some initial scripting.

One thing I want to do with the Quine demo this week is to develop the basic structure from the minimal markup we started with last week to the slightly more structured markup of the basic HTML template that we'll use as a standard starting point for web pages for the rest of the semester.

Homework

Reading

Duckett, chapters 2 – 5 (covers important HTML in detail).

Photoshop Tutorials: Burrough and Mandiberg, Digital Foundations, chapters 2 and 7 – 12. Read through these chapters. Most are devoted specificallty to Photoshop. Follow the exercises as needed. We'll return to a few of them later in the semester as we focus on particular skills or as they become relevant to particular aspects of the final project.

Kevin Yank, Simply JavaScript: The Three Layers of the Web (Sitepoint).

Milan Negovan, Back To Basics: (X)HTML Specs Made Easy

Also, take a look at XHTML v. HTML; Bad Tags; and Span and Div.

Linking Questions

As discussed in class, grasping the basics of linking is essential and will make what follows vastly more manageable. With this in mind, read Chapter Two of Duckett (see above), then answer the following questions on linking and URLs:

  1. What's the difference between an absolute and relative URL?
  2. What would be the HTML code for an ABSOLUTE URL (or link) to your "425" folder on Eden, so that clicking on the link would open the folder in a NEW browser window?
  3. If you're building a page inside your "425" folder and want a RELATIVE link from the new page to a page called "index.htm" in your "hw" folder, what would be the HTML code?
  4. If you're building a page inside your "drafts" folder and want a RELATIVE link from the new page to a page called "a_list.htm" in your "hw" folder, what would be the HTML code?
  5. What would be the code for an HTML element somewhere on your Bio Page named "part1"?
  6. What would be the code for a relative link to that element?

PRINT your answers on a SINGLE sheet of paper and bring the sheet to class.

Download (Free) SFTP Application

As noted in class: all campus PCs should have the SSH application, and all campus Macs should have Fugu. If you're working off-campus/on your own machine, you'll need to acquire one of these programs or an equivalent.

You can download SSH for home use from RU Software (login with your NetID and search under keyword "SSH").

Mac users can try Cyberduck or Fugu instead. (For help with these applications, consult one of the many computer lab assistants at any Rutgers computing lab.)

End of the World Project

Complete Part One (PDF version) and Part Two (linear version) of the End of the World Project (EWP).

For Part One, prepare a PDF containing your title, introductory text, nine images, and their captions. Save a copy of this PDF in your "hw" folder on Eden and bring a printed copy for the instructor.

Note: You can make a PDF file from any document in MS Word.

For Part One, take and format your photos (resize, crop as needed). You'll need to have access to all three sizes in class. Write your introductory text (at least three short paragraphs narrating how the world ended/changed radically; what it looks like now). Write in the voice, e.g., of a photo-journalist visiting the future and sending back a report. Prepare titles and descriptive captions for each of your nine images. Finally, come up with a descriptive title for the page. The title should give a sense of how the world met its fate. "End of the World," "End of the World Project," and "EWP" are not good titles.

As discussed in class, avoid the obvious environmental ideas – a world covered in snow and ice or drowned under a deluge of water. Creative exceptions to this, such as accounts focusing on what might be buried under the snow or water after the world ends, are allowed. (Also, avoid anything that emphasizes happy-pretty ends of the world. Last year there were a few worlds ending in beauty, with lots of colorful sunsets and flowers, that were unfortunately bland. Beautiful images are fine, but they also need to be strange, interesting, unexpected.)

Images should be landscape rather than portrait oriented (wider rather than taller). This will help with the screen-based layout, which tends to favor width over height (at least in the non-handheld cases).

As discussed in the assignment: You'll need to save your images as jpgs at three different sizes: thumbnail, preview, and large. Keep the width and height consistent for all the images at each size. In sum:

Size Width
Thumbnail 96px
Preview 264px
Large 624px

To save your images at the different sizes, use Photoshop or a similar program. Select the Save for Web & other Devices option under the File menu. For extra guidance, as needed, refer to these tutorials at Digital Foundations: Graphics on the Web.

Next: Complete Part Two of the project. Begin from the Basic HTML template. Save the completed HTML page in your "drafts" on Eden. Then post a link to your page in a reply to the "EWP - Linear" thread on the Class Forum.

top

Week One

Wednesday, Jan. 18
One

Announcements

Class Location and Start Time

We meet in Loree 023 this week; not in Hickman Hall. (In fact, we'll never meet in Hickman Hall.) Class will begin slightly later than listed, at 11:05 AM.

Working in Class

If you are fairly experienced at building web pages, then you may use whichever machine you prefer. If you are not, you should use a PC in class. Outside of class, do as you prefer. Note: All the machines in the classroom are dual-boot, i.e., can start as either a PC or a Mac.

Revised HTML Template for Bio Page

Use this template for your bio page. Copy and paste the text into a blank Notepad and file, save as "bio.htm", and go from there.

Introduction

Course Description and Policies

A printable and downloadable (PDF) course description and list of course policies can be found on the Resources page.

We'll review the description and policies in class. However: Be sure to read these carefully (especially the policies). If you have any questions about the syllabus or the policies that were not addressed in class, contact the instructor or ask him in next week's class.

Web Authoring Languages

Diagram of web authoring languages
Table of Web Authoring Languages
Type Use Example
natural content English
markup content structure XHTML
styling presentation CSS
scripting functionality Javascript

W.V.O. Quine Example

I'll illustrate some of this with a basic example that we'll return to over the next few weeks: an invitation to an exibition about the American philosopher and logician, Willard Van Orman Quine.

Exhibition websites (or pages) are a common web genre. Here is an example: Infinite Jest: Caricature and Satire from Leonardo to Levine. And here is a more complex exhibition site: Frogs: A Chorus of Colors.

Web Page Examples

Let's look at some examples of different web pages. Each of these pages belongs to a particular genre or familiar category of web page. The page includes features that users expect to find in instances of that genre. To what genre do each of the following pages belong? What standard features identify the page as an instance of the genre?

View the "source" code for the examples in Firefox (Ctrl + U).

Technical Policies for Web Authoring

In addition to the general course policies addressed above and in the supplement to the printable syllabus, there are a number of basic technical policies for the web authoring course. Following these will make things progress smoothly in each class and between classes.

Activities

Photoshop Review

We'll take a look at some basic features of graphics editing and manipulation, using the Adobe Photoshop application. Specifically, we'll concentrate on features that you'll use to revise images for your personal Bio Page and other work this semester.

This will be a brief review. You'll be expected to know how to do the following (it's a requirement for taking this course):

  • Resizing
  • Saving for the web
  • Copying & pasting
  • Working with layers
  • Cropping
  • Adding text

If you're not familiar with any of the above skills, try one or more of the many online tutorials that cover them. The tutorials can easily be located via Google.

HTML Beginner Tutorial

Web pages are structured using HTML. If you are new to HTML, then complete this HTML Beginner tutorial (at the HTMLDog website) before you start the Bio Page (see below).

For the tutorial (and all subsequent activities), work in Firefox. Do not use IE. If you don't have Firefox installed, get Firefox here.

The tutorial recommends that you use the Notepad program on a PC to write your code. When saving your file, select "All Files" as the "Save as type" option and give your file an "htm" extension (not a ".txt" extension):

picture of saving in Notepad

If you are working on a Mac, try using TextEdit. To save your HTML file properly in TextEdit, you'll need to set the application to save your file as PLAIN TEXT. You'll find this option on the FORMAT menu:

picture of saving in TextEdit

Also, when you save in TextEdit, give your file an ".htm" extension, not a ".txt" extension. If the program asks if you want to use the ".txt" extension, decline its offer.

Web Bio Page

The Bio Page will be your first substantial web page of the semester. Technically, it uses nothing more than the HTML covered in the above tutorial.

Note: Do not use the page you made in the tutorial for your bio page. Rather, use the basic XHTML template this simplified template for your bio page. Copy this basic code from the text file into a new Notepad file and save as "bio.htm". Then start adding your markup (i.e., HTML) and content.

Complete a draft of the assignment as homework for next week (see below). The content (some writing, some pictures, some online info-gathering) shouldn't be a problem. As for the HTML, if you're new to this (as many of you will be), just do your best with it. Next week, we'll address any major problems. (Also bear in mind that the Duckett book will help; so get the book as quickly as you can.)

Homework

Reading

Duckett, Beginning HTML, XHTML, CSS, and JavaScript, Chapter One. Note: Only this chapter is available online. For subsequent chapters you'll need the book. Note as well that chapters 2 and 3 cover linking and images. While not assigned reading until next week, you may want to refer to them in advance once you have the book.

456 Berea St., HTML Tags vs. Elements vs. Attributes.

HTML Beginner Tutorial

Complete the HTML Beginner tutorial (at the HTMLDog website) before you start the Bio Page homework. As covered in class, this tutorial will introduce you to the HTML basics.

For the tutorial (and all subsequent activities), work in Firefox. Do not use IE. If you don't have Firefox installed, get Firefox here.

The tutorial recommends that you use the Notepad program on a PC to write your code. When saving your file, select "All Files" as the "Save as type" option and give your file an "htm" extension (not a ".txt" extension):

picture of saving in Notepad

If you are working on a Mac, try using TextEdit. To save your HTML file properly in TextEdit, you'll need to set the application to save your file as PLAIN TEXT. You'll find this option on the FORMAT menu:

picture of saving in TextEdit

Also, when you save in TextEdit, give your file an ".htm" extension, not a ".txt" extension. If the program asks if you want to use the ".txt" extension, decline its offer.

Class Forum

Register for the Class Forum.

Note (1): You will not be able to access or reply to threads on the Forum until you register.

Note (2): You can access the Forum in future via the menu at the top of this page.

Post a reply to the "Introductions" thread, introducing yourself (e.g., major or likely major, career plans, interests, technical experience).

Note (3): You'll find more than one thread on the forum. For now, reply to only the "Introductions" thread. You'll reply to other threads during and after class next week.

Web Bio Page

Complete the Bio Page assignment for the next class. Refer to the assignment page and the comments under the Activity section above.

Bring this work in electronic format to the next class via a portable drive, or email, or external storage (e.g., myRutgers); or whatever means works for you. But be sure to have access to the HTML file and all your images in class.

top