Difference between revisions of "AIM Class1"

esse quam videri
Jump to: navigation, search
(→‎Single page construction)
(→‎Markup)
Line 140: Line 140:
 
===Markup===
 
===Markup===
 
[http://www.w3.org/MarkUp/Guide/ Getting Started With HTML]
 
[http://www.w3.org/MarkUp/Guide/ Getting Started With HTML]
 +
 
[http://www.janellbaxter.com/articles/HTMLauthoring.pdf HTML Authoring (pdf)]
 
[http://www.janellbaxter.com/articles/HTMLauthoring.pdf HTML Authoring (pdf)]
 +
 
[http://www.w3.org/TR/REC-html40/ HTML 4.0 Specification]
 
[http://www.w3.org/TR/REC-html40/ HTML 4.0 Specification]
  

Revision as of 00:42, 22 August 2006

Course Introduction

Introductions

Introductions of instructor and students in course.

Overview of Course

Required Texts

HTML for the World Wide Web with XHTML and CSS by Elizabeth Castro, ISBN: 0321130073, February 2003 - 5th edition (abbreviated as XHTML in the syllabus)

The Zen of CSS Design: Visual Enlightenment for the Web by Dave Shea and Molly E. Holzschlag, ISBN: 0321303474, 2005 (abbreviated as ZEN in the syllabus)

Highly Recommended Texts

Excerpts from these texts will be given as handouts

Information Architecture for the World Wide Web by Louis Rosenfeld and Peter Morville, ISBN: 0596000359 (abbreviated as IA in the syllabus)

Pause & Effect: The Art of Interactive Narrative by Mark S. Meadows, ISBN: 0735711712 (abbreviated as PE in the syllabus)

Login Accounts

To use the computers and studios in the Interactive Arts and Media department, you must first have an account with our servers. If you do not have a login account, please fill out the New Account Form.

Website Contracts

You must have a website on our servers for this course. Once you have an account, you can apply for a website by filling out the website contract form. Print the form, fill it out, and submit it to your instructor or Jeff Meyers.

Contact Information Forms

Print and fill out the Contact Information form. Return the completed form to your instructor.

Overview of Syllabus

Walkthrough of syllabus

Questions about Syllabus

Goal Oriented Media

What does it mean to develop something that is goal oriented?

Introduction to Website Construction

  1. Broad context of HTML/XHTML/CSS/XML
  2. WYSIWYG editors (such as Dreamweaver) vs. using a text editor

About the Web

  1. Brief history of the Internet
  2. Internet vs. WWW
  3. Evolution of markup - where it came from, where it is going.

Vocabulary

  1. Internet
  2. WWW
  3. FTP
  4. Browsers
  5. Servers
  6. IP address
  7. URL
  8. Markup
  9. HTML
  10. XML
  11. XHTML
  12. CSS

Definitions

Markup

HTML (HyperText Markup Language) is a set of directions that instructs another program (a "user agent" or "browser") to structure content.

Resources and Software

  1. Note about available resources at Columbia
    1. Server space (IAM)
  2. Recommendations
    1. Text editors (HTMLkit, SCITE)
    2. Image editors (GIMP, Photoshop, ImageReady)
    3. FTP applications (WinSCP, FileZilla)
    4. Server spaces
    5. Domain name services
    6. Redirecting to your site

Quick Overview

The process of editing with a text editor and a browser for previewing (screenshots are in the HTML Authoring (pdf) document).

XHTML + CSS

Structure and Presentation

Structure should be separated from presentation.

XHTML: Extending HTML

Earlier we spoke about the benefits of XML and why we are moving away from pure HTML documents. So why was HTML extended instead of replacing it entirely with XML?

XML is a "meta" markup language. In order to have anything meaningful, you must either use a pre-existing set of elements or create your own (unlike HTML, XML doesn't come with a predefined set of tags). For those looking to quickly markup a document, or for those who mainly need the set of tags already defined by HTML, XHTML is a more appropriate language to start with. XML languages can then be used in XHTML documents (HTML can not be used in XML languages - extending HTML allows us to use XHTML in conjunction with XML)

XHTML is almost exactly the same language as HTML 4.0 with a few important differences.

  1. Syntax - See the W3 Guidelines

XHTML Compliant Documents

A template for a basic XHTML document: 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>
Type document title here
</title>
</head>
</body>
Type page content here.
</body>
</html>

Single page construction

  1. Copy the template above and paste into the text editor of your choice. It is recommended that if you are using a PC in the IAM department, that you use either SCiTE or HTMLkit. Another popular editor is Text Wrangler.
  2. Create a link to an external site. Use the following example code, but link to a site other than Google. < a href = "http://google.com" target = "_blank" alt = "Google" title = "Google" > Google</a >.
  3. Create two lists - one with bullets and one that is numbered. Example code: <ul><li></li></ul>
  4. Add an image to your page. Example code:<img src = "image.jpg" width="100" height="100" alt="image description" />

Layout

CSS (will be introduced next class)

Tables (with caveat)

Multiple page construction

  1. Linking between pages
  2. Organizing site structure (and files)
    1. File naming: Filenaming is extremely important when working in a team - by having a predefined way of labeling files it is easier to know what a file's purpose is without having to open it up and figure it out. It is also useful when working individually on a large project. For example, if a site has navigation graphics that begin with nav_filename.jpg, when you see a file called nav_logographic.jpg you will know exactly what it is used for, and what type of image it is. It is ok to have long file names (we aren't running unix here), and the more explicit the name, the easier it will be to decipher the file's use three years from now.
    2. Naming conventions: Create a (or choose an existing) naming convention that you are comfortable with and then stay with it. Be consistent.
    3. Directory structure: Keep units together (such as all project one files in a folder called "projectOne" with a subfolder for "images")
  3. Basic navigation system

Posting to a server and testing

  1. How to post to the IAM server
  2. How to post to a remote server (using FTP)
  3. Browsing to a page vs. opening a page locally

Links

Text Editors

FTP Programs

Markup

Getting Started With HTML

HTML Authoring (pdf)

HTML 4.0 Specification

Homework

Reading

XHTML: Introduction (pgs 13-22), Chapters 1, 2, and 3

Self Review

Retrieved from "https://imamp.colum.edu/mediawiki/index.php?title=AIM_Class1&oldid=3561"