Schedule

Introduction

We will run through the ten concepts which make up the course content as we begin work on our major assignments. Find the readings mentioned in any week by clicking the link for that particular week. Required readings are tagged with "required", and examples with "example".

Week 1 (8/23 & 24): code

Introduction to the course. Discussion of semester objectives and assignments. Get materials. Discuss your computer skills, likes, and dislikes. Begin learning how to make web pages. In class, read syllabus, Wikipedia entry, and WordPress docs as needed.

Week 2 (8/30 & 31): code

Read Hetland’s "Instant Hacking," the Code Wikipedia entry, and the HTML Beginner’s Guide. Try some of the HTML examples, and/or make a web page with Nvu. Read the WordPress docs if needed. Get comfortable with software (Nvu, WinSCP, etc). In class, we’ll make some web pages, and discuss how writing code (by whatever means) differs from writing words.

Week 3 (9/6 & 7): style

Class online only this week (blogging). Don’t neglect posting! Style is defined in many ways in the readings; consider the similarities and differences. Read the Kelly piece and try using Word or OpenOffice to create a document with styles. What are the advantages of doing so? Open my CV if you need an example. Read "Inverted Pyramids in Cyberspace" and "Writing for the Web." Continue to make and post web pages; post your successes, questions, etc. to the weblog. Finally, review the project assignments; they will be posted by this time.

Week 4 (9/13 & 14): standards

Read: "A Web Standards Primer", "The way forward with web standards", "Interface Standards and Design Creativity", and "Open standard". Discuss standards in general. How do they work? Do they stifle us? Do they create community? How do communities affect writing (with computers)? How do they apply to our service learning projects?

Week 5 (9/20 & 21): interface

Read at least the intro and Ch. 1 of Interface Culture, all of "The Anti-Mac Interface", and the Wikipedia article "User interface." Macomb students should also look through the WIU FYE web site. Issues: what is an interface, broadly speaking? Should we think of interface whenever we think of all technologies—mobile phones? writing? Consider the elements of the Mac and Anti-Mac interfaces highlighted by Gentner and Nielsen. Their article is 10 years old: is it relevant for today? for web pages?

Week 6 (9/27 & 28): usability

Read the two Quesenbery articles and the Nielsen piece. Look at the testing lab image as well. Issues: what is usability, and why is it relevant to computers & writing? Why is a multi-part definition useful? How does it differ from other ways of evaluating technologies and communication? What is usability testing?

Week 7 (10/4 & 5): metadata

Read the Shirky article. Spend some time on Digg and compare it to Del.icio.us. Why do we need data about data? Why "tagging" as opposed to other forms of organization such as hierarchies? Consider both automated and human-generated metadata creators and interfaces.

Week 8 (10/11 & 12): network

Read the Nardi and O'Day article, Nielsen's "Does Internet=Web?," and the Wikipedia entry on "social network." What is a network? a social network? Why are the latter now so popular? How do social networking applications and sites function? (Think back to Digg and del.icio.us.) Also: midterm weblog & class participation evaluations.

Week 9 (10/18 & 19): ip

Focusing on McLeod’s book (intro and chapters 1, 5, 6), consider the role copyright plays for computers and writing. Why is it a big deal for music, images, text, and other forms? What problems arise from restrictions on rights?

In depth

We will fill in the schedule below at midterm. I would like to return to McLeod and Johnson, but I will defer to your wishes.

Week 10 (10/25 & 26): Studio time

No readings. Come to class ready to work on projects. Bring whatever materials you need.

Week 11 (11/1 & 2): Accessibility

Read Dive Into Accessibility. If you want, check out more on accessibility (a LOT more) in my del.icio.us.

Week 12 (11/8 & 9): Code, revisited

No reading; discussion and review from CBD.

Week 13 (11/15 & 16): Style, revisited

Re-read "CSS from the ground up," and "Tips for understanding Microsoft Word styles."

Week 14 (11/22 & 23): turkey

No class. Go eat turkey, etc.

Week 15 (11/29 & 30): none

Course evaluations. Finalize FYE work.

Week 16 (12/6 & 7): none

Work time.

Week 17 (12/13 & 14): none

Class meeting this week but very brief; turn in stuff only. All projects due 12/14/2006 at 8:00pm.