Tuesday section will start at 4.15 pm.
Wednesday section will start at 5.15 pm.
Yet another comparative timeline: The Times Square Time Ball.
Like Javascript and the Actionscript underlying Flash, PHP is a scripting language. Unlike the other two which run in the browser, PHP runs on the server (e.g., Eden or RCI). Here are two examples of PHP for us to examine.
This is an example of a PHP Page Changer script.
Here is the PHP code for the page changer. It can easily be integrated into a the HTML of any page. However, to work, the page will need to be re-saved with the .php extension.
Refer to Show Form PHP and Email Form PHP.
For your final project, implement the showform script.
Basically you can cut and paste the code into Notepad and save with a .php extension. Then, in your form tag 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 (most should have it installed), but will not work on your desktop or other personal computer.
On PHP, see W3 Schools' PHP Tutorial, etc.
Review the Final Project checklist (revised for clarity on Dec. 11).
Test your pages in IE 6. Test your Javascript.
Clean up all your old (midterm era) pages. For example: Older Bio Page; New Cleaner Bio Page.
By "cleaning up," of course, I mean not simply visual revision. Rather: content needs reconsidering. For instance, your bio page should represent you as the author of your final project, not as the student who began this class 14 weeks ago. Finally, cleaning up means updating your code to reflect best XHTML and CSS practices.
Complete the Final Project. Review the Final Project checklist on last time.
The finally finished Final Project is due, finally, online by 1 PM, Monday, Dec 15. All files (XHTML, CSS, images, .swf files, .js files, .php files, etc.) should be in the same "final" folder.
Once you have completed your project, post a link to your "final" folder in a reply to the "Final Project" thread on the Class Forum. I will not examine your project or considered it submitted until you post a link.
After you have submitted it, leave your Final Project online and unchanged for at least one month after the start of the next semester. (If you wish, of course, 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.)
Finally leave a CD copy of your entire final project by 12 pm, Wednesday, Dec. 17 either (1) in my mailbox in the Murray Hall mailroom on College Ave or (2) under my office door, Loree 010, on Cook/Douglass.
You can receive your final grade and your graded final work from me in my office, Loree 010, on Wednesday, Dec. 17 between 2.30 and 3.30 PM. If you cannot make this time, you can request your grades from me via email. Note, however, that I will not send grades by email without an explicit request for the grades to be sent by email.
My classes for Spring 2009.
Free and lovely science art and photo library: Conceptual Diagram Symbol Libraries.
Here are some more (recent) timeline examples:
Note: these are not necessarily optimal timeline formats; they're linked for inspiration and class discussion.
Here is an example of one kind of interview text. Notice the mix of Leibowitz's quoted answers with the writers comments, summary, and contextualization.
Here is an example of a different kind of interview text. Here we have a few paragraphs of intro/set-up followed by illustrations and a question/answer format.
Here is another explanation of conditional comments.
Basic conditional comment for an IE 6 specific external CSS file:
<!--[if lte IE 6]> <link rel="stylesheet" type="text/css" href="ie.css" /> <![endif]-->
You would insert this special comment into the head of your HTML file.
Here is a site harmonization checklist:
Another look at this homepage revision demo.
Work on Final Project.
Complete draft of the bulk of your final project. At least have ideas for supp pages.
Remember: Your final project will need at least two supplementary pages (e.g., FAQ page).
Resource Overload: Deziner Folio.
For example: FlexiGrid demo; Ultimate Web 2.0 Layer Styles – Free Download; and my favorite of the day: the Smooth Scroll code.
Making embedding Flash movies in your XHTML easier: SWFObject.
Good image size and quality and in a narrow ("blog") column design: MoCo Loco
Ditto: London Ampersand Hunt
For those of you interested in adapting current print design trends to your webiste, observe The New(er) Typography: Counterless, Bold and mostly Geometric.
Finally, just because I like it: Retro-Futurismus.
Embedding links in your Flash movie.
Embedding your Flash movie (.swf file) in your HTML.
Second text essay. 1200-1800 words. On a topic and of a genre discussed with and APPROVED BY the instructor. Same formatting as first. Stapled, numbered pages. Include word count at the end.
Continue work on timeline page. Begin building visual page. (Again: the visual material on this page should be non-copyright and preferably of your own creation. Use Flash, Photoshop, a camera, your imagination, pen, pencil, scanner, whatever works. And be ready to discuss more ideas with the instuctor.)
Start to revise midterm work.
remember: Your final project will need at least two supplementary pages (e.g., FAQ page).
Tuesday section will start 20 minutes late today.
We'll discuss these (further). Make sure you post a link to your example via the Class Forum.
Kevin Cannon, Twin Cities Rock Atlas (.jpg) for City Pages.
Cannon documents and explains his design process for this project on his blog, Big Time Attic.
If you want to take a break, use Google to find out how to make a favicon (e.g.,
) for your website.
Then make one. This will give you a chance to practice more with Photoshop and pixel measurements.
Historical inventory of older browser bugs: RichInStyle.com Bug pages.
Use Conditional Comments to get your site to display accurately in in Internet Explorer (I.E.).
Basic conditional comment for an IE-specific external CSS file:
<!--[if lte IE 6]> <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:
Timeline should include 20 events, with illustrations (with title/caption and source information). Should be comparative, with in-text links (for further reference).
Style: visually, dates must contrast with descriptions. Other style points discussed in class.
Here's a mock comparative timeline design. It's static and clean but not too interesting. How might the Java swaps from last week be used to liven up the design?
Some older examples:
Second text essay. 1200-1800 words. On a topic and of a genre discussed with and APPROVED BY the instructor. Same formatting as first. Stapled, numbered pages. Include word count at the end.
Continue work on timeline page. Begin planning and design for visual page. Again: the visual material on this page should be non-copyright and preferably of your own creation. Use Flash, Photoshop, a camera, your imagination, pen, pencil, scanner, whatever works. And be ready to discuss more ideas with the instuctor.
We discuss these.
This is a simple but creative and effective Flash movie/slideshow promoting Greg Bear's science-fiction novel, City at the End of Time (2008).
Related: an article on Book Trailers, Book Videos, LitVids and Book Promotion.
What I find exciting about the Bear movie/animated slideshow is its non-video photographic technique.
And unrelated: short video tutorial on using Photoshop and Illustrator in conjunction (to make a logo).
More unrelated: Nike ID Home Page (via Andrea). Appealing home page design.
By popular demand, we take a short break from the projects proper to learn some Flash and make animated promotional material to lure visitors to your sites.
Some examples: HP Brand campaign: HP Digital Photography
To begin, let's take a look at a typical set of online advertising guidelines (Business World).
The Google AdWords Advertising Policies goes into a bit more detail.
From these guidelines we see that a max. length of 15 seconds is a convention and one that we'll follow for this assignment.
This is a Flash assignment from last semester.
Lukamaras.com has a special section of banner (and banner ad) tutorials.
The in-depth tutorial Creating a flash ad banner from start to finish will form the basis of this assignment — with a few modifications.
Here are the basic requirements for the flash ad:
Have fun!
Wednesday section: Work on Flash movie for Visual Page.
Both sections: Work on Timeline page.
Simple but effective design: Kristine Janssen's Portfolio.
For ideas: Best of CSS Design 2007 (sez Web Designers Wall).
Tom Phillips, 20 Sites n Years
For adding secure email links to your website, consider using The Hivelogic Enkoder.
Vintage Home Page designs (or, Raiding the Public Domain for Inspiration): Web 2.0 style is all about making our web pages look very "now" (or ten minutes ago, things moving cable-quickly as they do). But think about the possibility of moving, designing, in the opposite direction, 1907 rather than 2007. For instance, take a look at these fantastic Inland Printer covers from way back in the last century. Design is very time-sensitive, thus dates remarkably quickly. This can be a danger, but you should also see it as a resource, something to exploit, esp. if your project has a historical dimension.
New Pages: Timeline Page, Visual Page, and Second Text Page (e.g., feature story, interview story, in-depth tutorial, critical analysis, comparative analysis, multiple-entry blog). Note that the second text page should fit your site topic well (logically) and cannot be a simple report that gathers and presents information without some kind of argument, critical point of view, or organizing narrative. Consequently, even a tutorial should be framed by a narrative of some kind.
New Code: Javascript, possibly Flash.
Some examples:
Let's take a look at the site navigation samples from a few weeks back.
And some of the sample home pages as well.
Next: A home page revision demo.
And a note on centering text: If you must (i.e., if it looks really good), you can center headers/titles. But except in very, very special cases, you should never center paragraphs (blurbs, chunks, etc.) of text. It just looks bad, usually interferes with the overall page design, and makes reading a little more difficult.
First: MAKE SURE that you are organizing your (revised) feedback page with FIELDSETS and LEGENDS. This makes the page easier to read (scan), better looking, and easier to style and re-style as needed.
Some functions of the Feeback Page:
Not: Did you learn something about women in racing that you never knew before? (y/n)
But: What did you learn about women in racing that you never knew before?
What was the first video game you remember playing?
How long did it take you to master the game?
Disagree with any of my book reviews? Left me know!
Let's take a look at this fairly simple HTML Swap Demo.
Next, let's take a look at these related HTML swap Demos: Three, Four, and Five.
Finally, here's a slightly more comlex application of the same basic code in combination with CSS: Six.
Basically, when triggered by a mouseover action, the script located the div element with the specified id (e.g., "right" in first demo) and replaces the HTML inside the div with the new HTML specified in the corresponding instance of the function.
As discussed previously, the visual page focuses on the visual rather than the textual. The page must relate to your site topic. It should contain roughly 24 non-copyright images, preferably of your own creation (or commission You may use/present the images in a gallery, a timeline, a slideshow narrative, a tutorial, a tour, a pictorial encyclopedia entry, a dialogue, a Flash movie, etc.
Text in captions or elsewhere on the page should identify each image, and (where necessary)explain what we should notice in it.
Here are some gallery pages for us to examine:
Note: These examples are for class discussion; they are not necessarily models for your image gallery
Note: The requirements for these differ slightly.
For the next assignment: You'll make an illustrated, interactive comparative timeline containing twenty or more events in two distinct categories.
Interactivity on the page can involve the display (i.e., dynamically displaying content), the navigation (subnav, cross-referencing, etc.), or both.
Bad example: Impressionism.
Good example: Manet and Maximilian.
Note: These timelines were made for a somewhat different assignment; they are presented here for comparison and disucssion and should not be used as models for the current assignment.
Note: Some are more interactive than others.
Work though Javascript demos. Revise home page. Begin researching and constructing timeline page.
Find and read what you find to be a good example of an online text that you feel would meet the requirements for the Second Text Page. Copy and paste the URL in a reply to the "Second Text Example" thread on the Class Forum. In the next class we'll go through these examples. Each student will explain his or her example to the class – i.e., how it works as a good example of an online text feature (that meets the reqs for this class); also, where it might fail in places.
We'll review the feedback questions you posted and the ones on your pages, and talk about how to sharpen and broaden them for the midterm and beyond.
But first a novelty: web.Burza – Superhero Edition.
Work on revising your BR and Feedback pages and begin to build your Home page. Again, here are the BR template and basic CSS we developed/revised last week. Elaborate, modify, customize, and improve for your continued use.
For the latter, refer to the material in the HTML Dog book and to the beginner and advanced form tutorials on the website. Use CSS and the CRAP principles to style your form and make it easy to use. For the midterm, you do not need to have a working form (i.e., not has to happen to the information when the user submits it).
Revise BR text, links blurbs (there'll be a revision exercise in class), and Feedback Questions. Insofar as possible: Your original BR text should be chunked and trimmed by 15-25%. You'll then add new material in response to my feedback and peer-review (in today's class). Unrevised BR and blurb texts will weaken the midterm by at least one letter grade. As will your failing to turn in a PRINTED COPY prior to the midterm.
Use Adobe Kuler and other color resources to give your website a stable and attractive color scheme, one that goes with your topic and enhances the readability of your content.
Remember that for the midterm, CSS for all the pages should come from a SINGLE external .css file.
Give a distinct id name to the body tag of each of your pages. This will allow you to write page-specific CSS rules by combining ID selection with descendant selectors.
Finally, to clarify what was discussed last week: all pages (home, BR, feedback, and any others you might add) need to have site navigation. Site navigation should be in the same place on all pages, except on the home page (if it functions as a more graphically focused cover/title page rather than a simple introduction page). And all pages should have a banner identifying the website. The banner can be tailored to each page or (for the midterm only) be a general banner.
Complete and upload your midterm by Friday, October 24, 6 pm.
All (and only) midterm files must be in a (new) "mid" folder inside your "425" folder.
Once your "mid" folder is complete, post a link to it in a reply to the "midterm" thread on the Class Forum. Your midterm will not count as submitted until you post your reply.
Part of the next class will focus on the Home Page. We'll also preview the next group of pages for your project.
I'm subtracting the Author's Page (new bio page) from the midterm. (This will probably return as a req for the final.) Instead, you'll add a small bio paragraph or two to the sidebar of your BR page (and possibly your other pages as well).
For an example, scroll down to the ABOUT ME section in the sidebar of Sheila Heti's I Dream of Hillary blog.
Note: The midterm will be due online (with a notification in the class forum) by 6 PM, next Friday, October 24. You'll need to create a "midterm" folder inside your "425" folder and copy your midterm pages, CSS file, and "img" folder there. The "midterm" folder should contain only the files of your midterm. Nothing else. I regret to seem cruel, but having non-midterm pages or images in your midterm folder will takes points away from your grade.
We'll start today with the Book Review and Links Sidebar. If we have time, we'll work on the Feedback page as well.
The Feedback Page has four main aspects: content in the form of well-defined questions, structure in XHTML, presentation through CSS and CRAP, and functionality through scripting.
The first draft of the Feedback Page will need to ask at least eight questions of your user. Basic biographical and demographic questions, such as age, location, and gender, do not count towards these eight questions (but ask them if you want). The questions should be divided into at least three sections (i.e, fieldsets) and use at least three different input types.
The feeback page is basically a form page. I'll introduce form pages a little in class; but you'll need to work with the HTML Dog book and site. See the beginner and advanced form tutorials on the website and chapter 9 in the textbook.
Use CSS and the CRAP principles to style your form and make it easy to use. Note: For the midterm, you do not need to have a working form (i.e., not has to happen to the information when the user submits it).
Finished drafts of the BR and Feedback pages are due next week. Late or incomplete work on these pages will affect your midterm grade.
In class writing exercise: Compose a brief paragraph in which you discuss the intended audience of the book under review (i.e., who did the author have in mind when he or she wrote the book; not necessarily the same as your audience) and explain whether or not (or to what extent), you believe, the book will satisfy the expectations of that audience. For example: Does it tell them what they would want to learn? Does it do so in an accessible way?
When you've finished copy and paste your paragraph in a new reply to the Further Reading Question 1 thread on the Class Forum.
Your Home Page should establish the general "look" of your site. It should be constructed around a focal image or design and needs to give your user an overview of the site architecture (main pages, content, nav options, etc.)
The HP Rule: Main page design, introductory content, and site navigation must fit in the active graphic space.
Examples:
Your HP will include and emphasize a site navigation design. This same design may repeat on the other pages of your project. Or you may develop a visually related but distinct site nav suited to the layout of the other pages. Other than on the home page, site nav should remain visually the same and in the same location. Site nav links should NOT change apperance or position from page to page or your user will get lost, confused, annoyed.
Here are some interesting examples of site navigation:
Some things to keep in mind:
Here are some samples. The first blurb might accompany a partly comic review of a Chuck Norris biography, the second a more serious review of the "browser wars":
One technique is to include a short list of examples in combination with brief descriptive phrases. Let's apply this idea to the following test cases:
Work on the Book Review page. I'll go over some features and techniques in class.
As noted in the assigmnet: The page needs a banner and the infrastructure for site navigation. Make a horizontal list of placeholder links for the site nav div under or above the banner div in your header. For link/list ideas, models, and sample code, survey the Listamatic at MaxDesign.
Begin work on Feedback Page and Home Page.
Here are some Photoshop and image swap/rollover related links that might prove useful for your home page or other parts of your midterm:
HTML Dog: chapter on forms.
Web Writing That Works!: How to trim your text (pdf) and make text scannable (pdf). These chapters from Hot Text will help you to revise your book review for brevity, precision, and scanability.
Another very short article on Writing for the Web.
And the "editorial style" section of the Yale Web Style Guide.
"Navigation Menus: Trends and Examples"
Complete drafts of your BR Page (inc. sidebar links) and Feedback Page for the next class. We'll review and revise these further in class.
Update: Here are the BR template and basic CSS we worked on in class. Elaborate, modify, customize, and improve for your continued use.
Revise your BR text and links blurbs. These need to be polished and exhibit good "web style" for the midterm. Make sure paragraphs are well-chunked into approx. 2-4 sentences per paragraph. Eliminate all uses of "there is/there are". As much as possible, keep an active voice.
The midterm prototype is the first draft of your final project and will be due online by Friday, TBA, at 6 pm.
The midterm consists of
Additional References for your book review page research and images can be presented on that page or on the optional Works Cited Page.
The Midterm needs to have a unified look or "visual theme," with a banner design based on/replicating some key features of the Home Page focal image.
Each page will need a banner that reproduces or resembles the Home Page design. You may use a single banner for all your pages or, more impressively, vary your banner thematically from page to page, as on this successful website.
Let's visit the Class Forum and take a look at some of your Further Reading Pages. In terms of content, we'll want to look at quality of sources and consistency of the bibliographical formatting. In terms of presentation and design, we'll want to focus on legibility and CRAP principles. Finally, in terms of code, we'll want to check for economy and error-free-ness.
Let's start with this Spore FRP Example.
Let's take a look at the Writing Program's plagiarism policy and the Business and Technical Writing Program plagiarism guidelines
As the Business and Technical Writing Program plagiarism guidelines make clear, using the code or design of a page that you find online generally counts as plagiarism, even if you credit the source. For the purpose of this class, this includes using any free page code and design templates you may find online or in an editing program like Dreamweaver.
You may use brief tutorial code you find online (e.g., from a tutorial that tells you how to make an image swap or a pullquote, things like the examples on the HTML Dog website and in the book).
You also may use prewritten Javascript that you find online, but you should discuss this with me (at least the first time you do this) and you must credit the source of the script in a comment in your code.
Image Use: Wherever possible use images of your own creation or images that are in the public domain. When you use an image under copyright, try to get permission from the image's owner. At the very least, credit the source of the image. (We will return to this matter again in the coming weeks.)
Finally, as stated in the class policies, if you miss this discussion in class, be sure to speak to me about these issues as soon as possible. I do not lie: They are very important.
Your Book Review page should have three or more images in addition to the optional cover image of the book under review and/or an author photo.
Each image should have a caption identifying/describing the image and identifying the source of the image (if you are not its creator).
Identify the image source by its author's name (author of the book, article, or website from where you acquired the image). For online sources, let the identifying name double as a link to the source.
In terms of CSS, you should create a standard image plus caption div class as well as standard "left" and "right" classes of floating div for the two offset image positions (if you plan to use these). Include image, title/caption, and image source inside these divs. Set the float directions for each div and use margins or padding to put space between the image and surrounding text.
Note: As stated above, you do not need to float images to the left or right. Wide images often work best inside or between paragraphs of text as part of the vertical flow of content. For example: Giornale Nuovo on Erik Desmazieres.
Small images: Unless it is essential to your page design, you should not center small images on your page.
Large images: If you need your user to view a very large image, put the image on a second page and create a link to it on your feature page.
Keep data size of the images on your pages as small as you can; preferably under 50 KB (large images obviously will be larger but still aim for the lower KBs). If necessary, re-save iamges for the web at a smaller data size.
Here is a demonstration of revising page design in order to use an image informatively with text.

So far we've looked at centering a div (or other block-level element), a basic layout technique. If we have time today we'll begin to examine a few more layout techniques, and then continue with them in more detail next week.
We'll try an exercise based on Float Tutorial 4 on Max Design's Floatutorial. Using your photographs from the Week 2 homework, you're build a slightly larger-than-thumbnail image gallery.
Next we'll begin to build a skeleton layout for your Book Review page (this is the second exercise I mentioned above).
First: Let's take a close look at the first book review example from last week: PHP and MySQL by Example.
Another book review example: Ellen Lupton's Thinking with Type.
Finally: for sidebar links see how Maud Newton does it in the sidebar on her blog.
Now to the demo/exercise itself:
Review the display (discussed last week) and page layout sections at HTML Dog.
In addition to the material in the HTML Dog book, many layout tutorials are available, such as:
Remember, you can use Firebug to study and test the CSS of any page. And here is the helpful Firebug Layout Intro.
Forgot to post this one last week, on web-writing style: Writing for the Web by Jakob Nielsen.
As we discussed, the Book Review is a genre of non-fiction writing and the Book Review Page, an emerging genre of web page. To get a better sense of what writing for a genre, or within a particular genre, might involve, take a look at "Writing in a Genre" (from Hot Text!: Web Writing that Works).
Construct a first draft of your BR page using the template we worked on in today's class or a similar structure of your own design. Add book review text and use CSS to format the text. Chunk text so that no paragraph has more than four or five sentences. Add images to the text. Images may be offset to the left or the right but larger images integrated into the text flow are better.
For next week, provide the following:
These last six questions will become part of your Feedback Page.
Post your questions to the "Feeback Questions 1" thread on the Class Forum. Also, turn in a printed copy of your questions in class.
Read this . . .
The link blurbs and other homework for this week and your book review (text but not web page) are due the next time we meet (week 6).
In the next class (week 6), then, we'll go over copyright and plagiarism matters. We'll begin to work with CSS positioning and layout, first with a float tutorial and exercise and then in setting up a basic book review page layout. This is absolutely essential stuff – in terms of both coding and design – and can be quite tricky at first. So, if you want to save yourself frustration, don't miss this class.
Also: We'll try look at each of your FRPs in class, esp. in terms of coding, usability, and basic design (see the CRAP principles reading from last week).
And we'll preview the midterm project, due around the end of week 8; although I'll probably get to say more about this in the week 7 class.
Here is a pretty terrible old web page: Wondermints fan site.
And here is an article on Current Web Style.
And here is an example of that style: Net Squared website.
And here is a related Web 2.0 How To tutorial.
Visual logic of the page: uses page design to visually indicate what goes together, what doesn't.
CRAP = Contrast, Repetition, Alignment, and Proximity.
Another principle is Focus.
Let's compare these examples:
More examples:
First, we'll discuss navigation and web semantics. Then we'll use the following models and tutorials to add subnavigation to your FRP.
Here are tutorials and some models for customizing navigation (using pseudo-classes) and then formatting navigation on a web page. We'll appply these first to the sub-navigation on your FRP.
Here are some more color resources. And (if I remember) we should also take a look at some of these web typography resources.
A further step: Use Photoshop's rounded rectangular shape tool and layer styles and effects to create a set of Web 2.0 style buttons for your FRP. To help with this try using Deziner Folio's Ultimate Web 2.0 Layer Styles (free download).
For the first major page of your final project, you'll write a 1200-1500 word book review with an accompanying related links sidebar. As discussed, the book should be a recent (as recent as possible but within the past five years) book related to your site topic and of likely interest to your intended site users. Also, it needs to be approved by the instructor.
Here are basic requirements for the page:
Note: the word count fo 1200-1500 words excludes block quotes.
The review should not simply summarize the book but should describe and evaluate it critically. For some content guidelines, see On Writing Book Reviews.
http://www.lavc.edu/Library/bookreview.htmSome examples (2 book reviews, 2 different online articles):
So far we've looked at centering a div (or other block-level element), a basic layout technique. If we have time today we'll begin to examine a few more layout techniques, and then continue with them in more detail next week.
We'll try an exercise based on Float Tutorial 4 on Max Design's Floatutorial. Using your photographs from the Week 2 homework, you're build a slightly larger-than-thumbnail image gallery.
Note: If we run out of time, we'll work on this exercise in next week's class.
Your "instructor-approved" book review book
HTML Dog, chap. 5.
Ellyssa Kroski, "Information Design for the New Web" (and the same article with better layout)
Molly E. Holzschlag's highly recommended Thinking Outside the Grid
Jonathan and Lisa Price, "Make clear what the user will get from the link" (.pdf) and "shift focus from the links, or the linked-to documents, to the subject" (.pdf).
Review the Writing Program's plagiarism policy and the Business and Technical Writing Program plagiarism guidelines
For a good sense of the tough reality of copyright conditions for images on the internet, read this informative exchange on Brian Carver's Ludwig Wittgenstein site
Find nine websites that would be of genuine interest/use to the reader of your book review.
Avoid (1) obvious sites (like Wikipedia) and (2) online articles in exclusive subscritpion databases like JSTOR, Project Muse, EBSCOhost, etc.
Write three-sentence descriptive blurbs for each site. Try to make these blurbs interesting and informative. Refer to the Jonathan and Lisa Price readings above for some advice on this.
Bring a printed copy of your blurbs to turn in and save an electronic copy in your "hw" folder.
Here is a good stylish example of some blurbs:

Unauthorized Photoshop mods and remixes of Scott McCloud's Google Chrome comic (last week's novelty): "Google's Chrome Comic Gets Bastardized 70 Different Ways".
Interesting use of pseudo-archaic but very unified page design: Dollar Dreadful Family Library.
A nice collection of banners from the Little Nemo classic Sunday comic strip.
Basic page design: Strictly Film School's Kiyoshi Kurosawa page.
Fancy page design: The Lippincott homepage.
The differences in design are quite clear. But what do these pages have in common?
As described under Week One, you'll work on the Final Project in several phases. The first phase culminates in the Midterm Prototype, during around Weeks 7 or 8.
First you'll write a book review of a recent non-fiction book strongly related to your topic and then build a Book Review (BR) page containing the review. Next you'll add a links sidebar to the BR page. Then you'll build a Feedback page, in which you seek different kinds of information and potential content from your site users. Finally you'll re-make your Bio page and design and build a preliminary homepage with introductory material and a few other features. You'll also design a single banner, based on the homepage design, to use on each of the other pages.
If you look at the sample final projects linked under Week One, you can sense of what each of these different pages involves.
Since you're going to begin your project with the book review, the best step to take as you determine what your project will be, is to find a recent non-fiction book. If you're struggling to find an idea, find a book of interest and use that form the idea. If you already have a good idea, use the book to sharpen it, to narrow down the idea.
The easiest way to find a book, I think, is to perform a key word search in IRIS, the RU Libraries online catalogue. Find a few books, check them out the library, and then pick one.
Open the CSS-added version of your bio page both remotely in Firefox and locally in Notepad.
Next, test your bio page's CSS in an CSS Validator to see if it validates.
If the page fails to validate, fix the problems, re-upload your file, and check again.
Repeat until valid.
Start by looking at XHTML v. HTML; Bad Tags; and Span and Div.
Next, let's look at the content, design, code, and image use of some of your Bio Pages. We'll access these via the Class Forum.
Note: 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 NOT submitted.)
Finally, let's preview the Adding CSS part of the FRP assignment.
Your sites should not be TOO colorful, but color should be used both aesthetically and meaningfully. For instance, use color to organize your page visually.
One method of logical page-coloring is to use a key image – e.g., from your home page – to generate a multi-color palette for background color, border colors, link colors, etc.
Select the image. Then apply the image to, e.g., Color Palette Generator, and see what we get.
An especially useful web tool for generating and testing coherent color schemes is Adobe Kuler.
Complete the Research Review for FRP.
After the research review, work on building FRP with XHTML and CSS.
For reference and review: Adobe Photoshop CS3 Tutorial
Very short: "CSS Coding Conventions" (PHPied).
Online article: "How to Size Text in CSS" (A List Apart).
If you have it: Read Robin Williams, Non-Designer's Design Book, pp. 10-86. 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.
If you are not in possession of the the Williams book, then read these online articles on the CRAP principles of design:
We'll go over examples of CRAP applied and CRAP ignored in next week's class. And there'll be a small related group exercise.
Note: This is a graded homework assignment.
Once we've discussed your topic idea (in class or by email), complete the Project Proposal assignment on the Class Forum ( Tue, Wed). This must be completed before the next class.
As part of the Project Proposal, you'll need to find 2-3 non-fiction books related to your topic. I'll approve one or more of these for your book review. The books need to have been published within the last five years.
Answer the Proposal questions on the Class Forum and bring a printed copy of your response for next week.
Finish building your FRP. Use XHTML to structure the page. Use CSS to style the page.
In Photoshop or another graphics program: Make an thematic banner for your FRP. The banner can use photographs or line art. It should not distract from the rest of the page, but nor should it be dull. It CANNOT be a text-only banner (e.g., colored text on a colored background.)
Here are some banner examples:
Google Chrome: The Comic by the Chrome Team and Scott McCloud. (And as I'm typing this, a guy has come on the radio to say that he thinks the advent of Google Chrome was the biggest [overlooked] news of last week.)
Related: Patrick Montero, Interview with Scott McCloud, artist behind Google Chrome comic (Daily News).
Open your bio page both remotely in Firefox and locally in Notepad.
Next, test your bio page's markup in an HTML Validator to see if its web-standards compliant.
If the page fails to validate, fix the problems, re-upload your file, and check again.
Repear until valid.
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.
We'll take a look at some basic features of graphics editing and manipulation, using the Adobe Photoshop CS3 application. Specifically, we'll concentrate on three features that you'll use to revise images for your personal Bio Page: layers, cropping, and saving (images) for the web. We'll also look at as some basic text editing in Photoshop.
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.).
<html>
<head></head>
<body>
<p></p>
<p></p>
</body>
</html>
Each box on the page, in turn, consists of a further series of boxes:
Note: Elements inside the body element divide between block-level and inline elements.
After a short demonstration of some basic CSS (using this Sample Bio Page), continue to develop your Bio Page by adding styling to it with CSS. Follow the CSS Beginner tutorial at HTML Dog.
Griffiths covers three ways to apply CSS to your HTML file. For this assignment, you'll use an EXTERNAL file (e.g., biopage.css) that you'll link to from the head of your Bio Page.
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.
Read the assignment. Then we'll discuss it. Or, we'll discuss it first. We'll begin working on this page as we finish the bio page. For next week, you'll need to complete the research/prep part of the assignment. Using the research, then, you'll begin building the actual page in class.
If you're stuck for an idea, a good place to begin is to find a good non-fiction book that interests you (you'll need to write a review of one for your project) and develop your project idea from the book.
Here are some very general types of project:
And here is a particularly excellent final project from last year: The Decline of Railroading in America.
Remember, it's important that your final project does NOT cover something already covered (at least not in the same way, from the same perspective, for the same audience) on the internet. If it's already there, it doesn't need to be there twice.
As you you think about your project, remember also that your idea should allow you to satisfy the page genre requirements.
Finally, all project ideas need to the instructor's approval.
And with that said, here are some projects or topics to avoid:
Blog Herald, "CSS Tips and Tricks".
HTML Dog, chap. 6, on lists.
Photoshop CS3 book, chaps. 6 (size control), 7 (layer basics), and 22 (working with type). These chapters cover in detail what we try briefly in this week's class.
Finish adding basic ("beginner") CSS styling to your Bio Page.
Replace the h1 text at the top of your page with a text image. (See HTML Dog 88-92.) For those of you using GIMP instead of Photoshop, try this tutorial.
Take at least six digital photographs representative of your daily space (e.g., details of your room or where you work; things you pass everday on your way to class; places you spend time outside of class).
Using Photoshop or an equivalent free program like GIMP, crop and adjust the photographs and save them for the web at a good size, i.e., one that doesn't take over the page but that still allows your site user to see what you want him or her to see in the image.
Save/upload these photos to the "img" folder in your "drafts" folder on Eden.
Add a new section to your Bio Page consisting of (1) a descriptive section heading (h2 or h3); (2) a short introductory paragraph; and (3) the six photographs.
Note: When you save the image for the web, try to keep the dimensions the same for all six images.
Complete the prep research for the FRP. Find the information on your sources (4 books, 4 articles in science journals, 4 articles by scientists mentioned in the article, and 3 website) and format them using MLA style.
Print and turn in a copy next week. (Two-sided printing is fine.)
If you want, you can also begin to build the FRP itself using XHTML and basic CSS. We'll work on this part in next week's class.
The introduction will cover the following topics:
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 eatures that users expect to find on instances of that genre. To what genre do each of the following pages belong? What standard features identify the page as instance of the genre?
View the "source" code for the last example in Firefox (Ctrl + U), or use this link: Simple HTML
The Final Project for Web Authoring involves building a multi-page website devoted to a specific topic or purpose. You select the topic, but the instructor must approve it. There's a lot of material on the internet, but there are also many gaps or absent perspectives. Your project should begin to fill one of those gaps or present a new perspective.
You'll work on the final project for about ten weeks of the semester, so it's more a semester project than a final one. Also, since you'll spend quite a bit of time on it, the project's topic should be something in which you have interest.
Note: You may produce a website to supplement research you've done in another class (e.g., producing an online version of a literature or science project). This will save time, since you'll revise and adapt work you've already done. If you want to do this, be sure to let the instructor know.
The Final Project develops in three stages. The first stage produces early draft pages: an online book review, a links sidebar to add to the book review page, and a feedback page.
The second stage results in the Midterm Prototype, due around the eighth week of class. For the midterm, you'll revise your book review, links sidebar, and feedback form; transform your bio page (that we start today) into a more formal Author's Page; develop a side navigation strategy and design; and add a front page (AKA home page, title page) that introduces visitors to your evolving website.
The final stage begins after the midterms and produces the Final Project proper, due about a week after the final class meeting. For the Final Project proper you'll fully revise the midterm and add an illustrated essay, a timeline, a glossary, and a few other supplementary pages. Emphasis will be placed especially on developing the visual aspect of your website.
To get a sense of what this work comes to, let's take a look at some Final Projects (FP) from previous semesters.
We'll look more closely at some of these sample projects over the next few weeks.
We'll go over the following:
Make folders for course work.
Complete SSH exercise.
Let's start to make a basic XHTML page step by step with this first week demo. The result of this demo will become the starting point for your Bio Page.
With the demo complete, begin to make your personal Bio Page. Complete a draft of the page for next week.
Read HTML Dog, chapters 1-4. It's very important that you work with this book and that you keep up with the reading.
Milan Negovan, "Back To Basics: (X)HTML Specs Made Easy"
456 Berea St., "HTML tags vs. elements vs. attributes".
Register for the Class Forum (Tue, Wed).
Post a reply to the "Introductions" thread, introducing yourself (e.g., major or likely major, career plans, interests, technical experience).
Think of at least two possible topics for your Final Project. List them in a reply to the "Project Ideas" thread on the Class Forum. We'll share and discuss these ideas in next week's class.
If you are working on a suitable research project in another class, you may use its topic for your web-authoring project. Basically, you'd develop a website to complement your project in the other class. This can reduce the amount of writing and research you'll need to do this semester. If you decide to do this, please discuss it with me.
Finish making a draft of your personal Bio Page. Use W3 Schools and HTML Dog. Students also find this HTML tutorial helpful.
Remember to match all opening tags with closing tages at the end of the element.
Update: Work in Notepad on a PC (or Textedit on a Mac, with the "Ignore rich text commands in HTML files" option checked in Preferences. Basically, you need to make sure that your saving your code as "plain text" and not as "rich text".). When you save on a PC, make sure you select "All Files" and NOT "txt" in "Save as type". I'm not sure what you need to select in Textedit, but, again, make sure that it saves with an ".htm" and not a ".txt" extension. I believe that was (part of) the problem some Mac users had in the Wednesday section. I.e., the Macs were saving the files as "biopage.htm.txt" or something like that.
For more help, take a look at "How do I save HTML files from TextEdit?".
If you need to, 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.
Update: If you have any trouble getting your files online, just make sure that you have access to them via email or Flash drive for the next class.
Update: If you're having trouble with your images, refer to the image display problem checklist.
Answer the following questions on linking and URLs (use Griffiths and Google to find the answers):
Print out your answers on a SINGLE sheet of paper and bring the sheet to class.