• PreparingForTheFinalPresentation

• PreparingForTheFinalPresentation

• keep in mind, you need a Designers page.

• attendance required

Address

• how the project went overall
• where you ran into problems and how you dealt with them
• how you made choices: what you based them on
• at every turn, show how you have connected your design choices to your goals and personas

final presentation: Mon 17 Dec 3:30 - 5:30

• workday: attendance required

Tues 11 Dec

• FYI: Web design / writing positions at WGBH.

• FYI: []http://www.macintouch.com/readerreports/jobs/index.html | Web design / writing positions at WGBH.]]

Tues 4 Dec

Thurs 6 Dec

• tba: attendance required

Tues 11 Dec

• tba: attendance required

111 Tues 3 Dec

• quiz on chapter 5
• including a Designers page
  • Include link to Designers page in footer as part of provenance. One paragraph bio, photos optional.

• review of pages: checklist
  • page title
  • page footer - email link/page link
  • sidebar nav
  • link to home
  • color scheme / palette and legibility
  • page properties (use on template)
  • templates set with editable and uneditable areas
  • pages created from templates set to update
  • make global changes on templates
  • make content changes on individual pages
  • ...

• Chap 5: Writing Web Content

Thurs 29 Nov

• review Chap 5
• review of where everyone is
• work time

Tues 27 Nov

• workday

final: Mon 17 Dec 3:30 - 5:30

On deck

• Writing web content

=== final: Mon 17 Dec 3:30 - 5:30 ==

• visual hierarchy
• showing relationships: emphasis and meaning

• using headings, fonts, and styles

• BFA Writing Promo

• review some elements of visual design, chap 4: content and nav elements

for Tues, 20 Nov

• chap 4: Visual Design

• Writing web content

• for Tues, 13 Nov, read chap 4: visual design, especially designing with grids

• determine number of templates, review grid layout

• review some elements of visual design, chap 4

• work on site maps - navigation - wireframes -
• ready by Tues 13 Nov

• determine number of templates
• set up on server?

• set up site on server?

• visual design, chap 4

• work on site maps - navigation - story boards - wireframes

Tues 13 Nov

• review maps, nav, wireframes
• determine templates

Thurs 15 Nov

• set up site on server
• assign tasks: translate wireframes, create templates, draft content

• review persona for each group
• review goals for each persona
• review content inventory

• work day: all present.
• site maps - story boards - wireframes

On deck

• Example content inventories:
• FiberArts
• NorthernLights

• Example content inventory SiteContentRequirements

Thurs 8 Nov

• Visual design

• Workday: Develop personas. Then
• Return to your goals to refine user goals with persona information.
• Use personas ad revised goals to create a content inventory. Site Project: Personas and Content Inventories

Tues 6 Nov

• Chap 3: Experience Design
• SiteProjectExperienceDesign

• In class: review your goals, positioning, land (speculative) user goals.
• Chap 3: Experience Design. Review: user personas and task flows
• Start to develop personas from interview notes: Site Project: Personas and Content Inventories.
• Substantial development of personas by Thursday, end of class.

Thurs 1 Nov

• Return to your work on goals to refine user goals with persona information.
• Use personas to create a content inventory. Site Project: Personas and Content Inventories

• Decide how to collect and where to post interview notes. Other groups have posted interview notes at the bottom of the questions page, listed by who interviewed. Eg: JustinsInverviews ...

• decide how to collect and where to post interview notes / responses.

• all Site Research (site reviews and connections) due. Refined goals.

• start the session with refined questions, who to interview and how to split up the work

• Interview and take notes on your interviews: taking notes (33) and recording key findings (34) for each interview. Post interview notes to wiki.

• Tues: Start to develop personas: Site Project: Personas and Content Inventories Finish by Thurs.

Thurs - Tues

• Begin interviewing and taking notes on your interviews: taking notes (33) and recording key findings (34) for each interview.

Tues 30 Oct

• Tues: Start to develop personas. Finish by Thurs.

• mods 11 and 12 due
• all Site Research (site reviews and connections) due

• start the session with refined questions, who to interview and split up the work

• layers are now called divs

Tues 25 Oct

• review and refine interview questions
• decide who to interview and split up the work

• workday

• Interviews should be finished and notes posted by Tues, 30 Oct. Develop personas.

Thurs 25 Oct

Deadline: By Saturday 20 Oct midnight

• Use your main group page as you need to: to plan, make connections, set schedules and make assignments. Update it as your project develops.

for Tues 23 Oct

• print the privacy window at p. 258. Printing works on both Mac and Windows side.
• print at end of page, showing scrolling text
• Scrolling text does not appear using Mac Firefox v. 2. Mac side, use Safari.

• In this mod, you create a set of rollover controls for images and text. Print at the end of p. 296. Preview the page in a browser, point to a number to show an image and text, and print. The rest of the mod has you create a slide show from the same images and texts.

for Tues 23 Oct

• Mod 11
  • print the privacy window at p. 258. Printing works on both Mac and Windows side.
  • print at end of page, showing scrolling text
• Scrolling text does not appear using Mac Firefox v. 2. Mac side, use Safari.
• Mod 12

• Deadline: By Saturday 20 Oct midnight, you should have your site positioning research posted (including critiques of related sites), user groups selected, and interview questions posted.

• Start Site Project: Requirements Gathering.

• ID the goals
• Develop your two sentence concept statement into a first draft of a purpose statement.
• Look for and critique related sites: see what others have done, how they do it, and find your site's niche.
• Plan who to interview/visit, questions to ask, how to take notes, how to get those notes on the wiki, how to divide up the work.

• Deadline: By Saturday midnight, you should have your site positioning research posted (including critiques of related sites), user groups selected, and interview questions posted.
• We'll look at interview questions in class on Tuesday, 23 Oct.

• Begin interviewing and taking notes on your interviews once you have your interview questions formed. (taking notes (33) and key findings (34) for each interview)

• Look for related sites to review.

• Mod 10: p;. 227. Arrange the elements on the page and print. p. 235. Print with the logo on the right hand side of the page.

Over the weekend

• Start Site Project: Requirements Gathering
• ID goals
• Develop your two sentence concept statement into a first draft of a purpose statement.
• Plan who to interview/visit, questions to ask, how to take notes, how to get those notes on the wiki, how to divide up the work.

• f2f work with Site Project: Requirements Gathering

Thurs 18 Oct

• Workday: continue Site Project: Requirements Gathering
• Deadline: By Thursday midnight, you should have your site positioning research posted, user groups selected, and interview questions posted.
• You can begin interviewing and taking notes on your interviews once you have your interview questions formed. (taking notes (33) and key findings (34) for each interview)

• GettingStarted
• SiteEditingGuides
• Use your main group page as you need to: to plan, make connections, set schedules and make assignments. Update it as your project develops.
• Expect to be working on the project outside of class - both face to face and on the net. Figure 2 hours for every hour of classtime.
• Bring your copy of Summer and Summers to class each day. You'll need to refer to it.

Tues 16 Oct

• Debrief on connecting goals with design choices: Examples. 10 mins.
• Work with chap 2 in Summers and Summers.
• Start Site Project: Requirements Gathering
• ID goals
• Develop your two sentence concept statement into a first draft of a purpose statement.
• Plan who to interview/visit, questions to ask, how to take notes, how to get those notes on the wiki, how to divide up the work.

• Groups, intro wiki, getting organized
• Main/GettingStarted
• Main/SiteEditingGuides

• Mod 9: Print one page at the end of p 219 (cropped images)
• Mods 10

• SiteProjectRequirementsGathering

Thurs 11 Oct

• Groups, intro wiki, getting organized, getting started
• ...

• Mods 5 and 6 due/

Thurs 4 Oct

• Part 4 due: Content: nomenclature, introductory text, blurbs, etc. Add typed content to page mockups. Usual procedure.

• Mods 7 and 8 due.
• Hand in materials from PortfolioSitePrototypeProject.Isolate the final versions from the draft versions.

Chap. 7 is shorter than others, and seem to end suddenly, after a confidence check. It does end on p 166.

• Mod 7: Print a page - any page showing the Spry menu you created.

• Before step 1: There are three buttons at the bottom left of the CSS Styles panel. One looks like a bullet list, the next has A B and a down arrow on it, and the third has two ** and a down arrow. Click the third one (the one with asterisks) to show the Show only set properties. The rest of the mod should be ok.

• Mod 8: Print at the end of p 199

• NotesOnDreamweaverEssentialsCS3

• Mod 7: Print a page.

• Step two (adding a property) is incorrect on the Mac side. It might be ok on the Windows side. Do this instead.
  • The line below font-size is font-family. Click in the space to the right of font-family and choose Verdana ... from the drop down menu.
  • Save your work and preview the page.

Tues 9 Oct

• Start the main project for this course.
• Chap 2: read it for review in class.
• Hand in materials from PortfolioSitePrototypeProject.Isolate the final versions from the draft versions.

• New mod pdfs and new Dreamweaver files available. Replace your current files with the new set.

• part 3 of PortfolioSitePrototypeProject due. Visual design and page mock ups. pp. 8 - 10. Review and discuss how your visual design choices connect with your goals.

• New mod pdfs and new Dreamweaver files available. Hang on to your old files, but use the new set.
• Mods 7 and 8 for Tues, 9 Oct.
  • Mod 7: Print a page.

• Mod 9: Print one page at the end of p 219 (cropped images)
• Mods 10 and 11 for Tues, 9 Oct (pending)

• Class canceled: family emergency. Meet as usual on Tuesday, 2 Oct.

Tues 2 Oct

• part 3 of PortfolioSitePrototypeProject due. Visual design and page mock ups. pp. 8 - 10. Review and discuss how the visual connects with the goals.

• Mods 8 and 9 for Tues, 9 Oct.

Thurs 4 Oct

On deck

Tues 9 Oct (pending)

• PageDescriptionAnnotatedWireframesUsability
• PortfolioSitePrototypeProject

• part 3 due. Visual design and page mock ups. pp. 8 - 10. Review and discuss how the visual connects with the goals.

• Mods 8 and 9 for Tues, 2 Oct.
  • Mod 8: Print at the end of p 199
  • Mod 9: Print one page at the end of p 219 (cropped images)

• Part 4 due: Content: nomenclature, introductory text, blurbs, etc. Add typed content to page mockups. Usual procedure.
• Mods 10 and 11 for Tues, 9 Oct (pending)

Thurs 4 Oct

• Chap 3 (pending)
• Hand in set of materials from this chapter. Isolate the final versions from the draft versions.

• tba: Mods 8: Advanced Templates and 9, or 9 and 10 for Thurs, 4 Oct.

• Mods 5 and 6 due
• Start Mods 8: Advanced Templates and 9 (Mod 7 is no yet available.)

• Part 1 of Portfolio Site Prototype Project due. Hang them up to discuss / revise.

• Part 2 of Portfolio Site Prototype Project due. Summers and Suummers, pp 4 - 8: Site maps and wireframses (note the plurals). Hang them up to discuss / revise.

• part 3 due. Visual design and page mock ups. pp. 8 - 10.

On the Dreamweaver mods

• Read the chapter intro text - it gives some concepts.
• If somethihng doesn't work, delete, back up, try again.
• Watch for problems: the text IS is in draft
• Alert: Some of the F-keys used in the Dreamweaver text conflict with the F-key assignments on the Mac. When the Dreamweaver text refers to using any F-keys ([F8] or [F12] for instance) use the menu open given instead.

• Alert: Some of the F-keys used in the Dreamweaver text conflict with the F-key assignments on the Mac. When the Dreamweaver text refers to using any F-keys ([F8] or [F12] for instance) use the menu open given instead.
• The [Cmd] key equivalents work ok on both platforms.

• Print Mod 6: When you complete the mod, you'll have created a quiz. Take the quiz and print out the last frame, the one that says "I'd like to take this test again." This might be tricky to print out; frames often are.

• Part 2 of Portfolio Site Prototype Project due. Hang them up to discuss.

• Alert: Some of the F-keys used in the Dreamweaver text conflict with the F-key assignments on the Mac. When the Dreamweaver text refers to using any F-keys ([F8] or [F12] for instance) use the menu open given instead.
• Mods 3 and 4 due. Start Mods 5 and 6.
  • Print Mod 5: p 137. When you complete the form, preview it in a browser, fill it out, and then print it.
  • Print Mod 6: tba

• Part 2 of Portfolio Site Prototype Project due.

Tues 25 Sept

• no class

Thurs 27 Sept

• part 3 due

Tues 2 Oct

• part 4 due

Thurs 13 Sept

Hand in wireframes from both exercises

Tues 18 Sept

• Mods 3 and 4 due. Start 5 and 6

Thurs 20 Sept

• Part 2 of Portfolio Site Prototype Project due.

• Put up wireframes, part 2 and discuss

• Part 1 of Portfolio Site Prototype Project due. Hang them up to discuss.

On deck

• Start mods 3 and 4. Due next Tues.
  • Mod 3: p. 81. Print any page using the template.
  • Mod 4: p 112. Preview page in browser and print. The background might not print, depending on how you have your browser set.

• put up wireframes, part 2 and discuss

On deck

Thurs 13 Sept

• Part 1 of Portfolio Site Prototype Project due

Tues 18 Sept

• Mods 3 and 4 due. Start 5 and 6
• Part 2 of Portfolio Site Prototype Project

• Web Design Handlist

references Web Design Handlist

• Review / discuss chap 1 to start the first project: PortfolioSitePrototypeProject

• Overachievers: refer to Design of Sites, chap 1 and 2.

• Review / discuss chap 1 to start the first project: A Portfolio Site Prototype

• Mods 1 and 2 complete. Hand in print outs.
• Read, annotate, Summers and Summers, chap 1
• A little more wireframing: PageDescriptionAnnotatedWireframesUsability
• Over achievers: refer to Design of Sites, chap 1 and 2.

Tues 11 Sept

• Hand in wireframes from both exercises
• Hand in print outs from mods 1 and 2
• Start mods 3 and 4
• Review / discuss chap 1 in preparation for first project

Thurs 6 Sept

• a little more on usability
  • go to selected sites. wireframe of page and usability notes
  • Web Design Handlist

For Tues, 11 Sept

• Summers and Summers, chap 1

• start first project

• PageDescriptionAnnotatedWireframesUsability

• PageDescriptionAnnotatedWireframesUsability

tba

Tues 28 Aug

Thurs, 30 Aug

for Tues, 4 Sept

Tues 4 Sept

For Thurs, 6 Sept

For each site, make some additional notes on usability. Give yourself couple of task you might perform on each site (Find the home page for the Dept of English. Find out if they offer a Web Design course ...)

• How easy was it to find information you're looking for? What makes it so, or what gets in the way?
• How do you know where you are on the site? How do you know you came from? How do you know where else you've been on the site?
• Did you get lost or disoriented? What did you do to get reorientated?
• How legible was the text? How readable? How easy was it to scan the text for information? What maked it so, or not?
• Anything else?

• Bring a flash drive!
• Pick up pdfs of chaps 1 - 4 and files for Dreamweaver Essentials CS3.

• We'll look at page wireframes
• We'll look a some more sites with a focus on usability.

• MSU Mankato. Do the same as for SCSU.

• Findability. How did you find the site?

• Work thorough mods 1 and 2 for Tues, 11 Sept.
• Mod 1: Print out your index page with your email address on it at the end of the chapter.
• Mod 2: Print out the table you worked on at p. 48
• Mod 2: Print out the button bar layout at p. 60

• If you run into problems with the DW Essentials text, check NotesOnDreamweaverEssentialsCS3. If there's no solution or note about the issue, leave one.

• look at page wireframes 1
• some more sites with a focus on usability.

• SCSU. Look at pages along top nav (category). Create a wireframe of a representative page. Then, look at the pages under the user nav on left. Create a wireframe of one page that varies from the others.
• MSU Mankato. Do the same as for SCSU

• How easy is it to find information you're looking for? What makes it so, or what gets in the way?
• How do you know where you are? Where you came from? Where else you've been on the site?
• How legible is the text? How readable? How easy is it to scan for information? What makes it so?
• Anything else.

• If you run into problems with the DW Essentials text, check here. If there's no solution or note, make one. NotesOnDreamweaverEssentialsCS3

• NotesOnDreamweaverEssentialsCS3

Tues 4 Sept

• pick up pdfs of chaps 1 - 4 and files for Dreamweaver Essentials CS3.
• look at page wireframes
• book check

<<<<<<<

• Example pages on delicious

>>>>>>>

• http://del.icio.us/mcmorgan/webdesignexample Example pages on delicious

• Boston University http://www.bu.edu/. Sketch and annotate the common elements of the category head pages: Admissions | Academics | Campus Life | etc

• News: I'll distribute the first pdfs of Dreamweaver Essentials CS3 next Tuesday, 4 Sept. You'll have until the following Tuesday to work through them.

• News: I'll distribute the first pdfs of Dreamweaver Essentials CS3 next Tuesday, 4 Sept. You'll have until the following Monday to work through them.

News I'll distribute the first pdfs of Dreamweaver Essentials CS3 next Tuesday. You'll have until the following Monday to work through them.

News I'll distribute the first pdfs of Dreamweaver Essentials CS3 next Tuesday. You'll have until the following Monday to work through them.

• Describing websites: using neutral language, taking a balcony view

• National Trust: http://www.nationaltrust.org.uk/

News I'll distribute the first pdfs of Dreamweaver Essentials CS3 next Tuesday. You'll have until the following Monday to work through them.

• National Trust: http://www.nationaltrust.org.uk/main/w-index.htm
• Boston University http://www.bu.edu/

• PageDescriptionAnnotatedWireframes using selected pages

• Have sketch paper and pencils/markers

for Tues, 4 Sept PageDescriptionAnnotatedWireframes using selected pages

Announcements

• Introductions

Thurs, 30 Aug

• How the Internet works (notes)
• Describing websites: neutral language, balcony view
• Describing websites: making wireframes and naming the parts: Web Design Handlist

• Siegel, Kevin. Essentials of Macromedia Dreamweaver CS 3. Skills and Drills. IconLogic, 2007. This text hasn't been published yet. I'm arranging to get it in pdf.

• Van Duyne, Landay, and Hong. The Design of Sites: Patterns for Creating Winning Web Sites. 2nd ed. Prentice Hall, 2007.

Hello World

• CourseStatement

• Some examples

Required Texts

• Summers and Summers. Creating Websites that Work. Houghton Mifflin, 2005 - Amazon
• Siegel, Kevin. Essentials of Macromedia Dreamweaver CS 3. Skills and Drills. IconLogic, 2007. This text hasn't been published yet. I'm arranging to get it in pdf.

Recommended

• Lynch and Horton. The Web Style Guide, 2nd edition. Yale UP, 2001 Available as an online book, or purchase a print version.
• Van Duyne, Landay, andHong. The Design of Sites. 2nd ed. Prentice Hall, 2007. Amazon?.

• [[http://del.icio.us/mcmorgan/WebDesignExample | Some examples]

Project Workspaces

Sidebar

Web Design for Content Writers

• CourseSyllabus
• CourseStatement
• CourseResources

Projects

• NorthernLights
• TravelPrograms
• HuntingAndFishing
• FiberArts

Sites

• Bemidji Borealis
• Travel Programs
• Hunt/Fish Bemidji
• Fiber Fabulous

Process

• Site Project: Requirements Gathering
• Site Project: Personas and Content Inventories
• Site Project: Experience Design

Participants

• AngelBatterman
• JeppeBundgaard
• JeremyDewey
• GrantGartland
• ToddGeiger
• KatherineGrandstrand
• TravisGrimler
• EricNorquist
• SharonSimpson
• JessicaSpeer
• MollyVotava

• AspenEasterling
• MichelleHawkins
• EricKuha

Preparing for your presentation

• Start a new page titled FinalPresentation
• Update task list: list who did what
• Review your original site concept and goals. Present the original goals, and if they need updating, add an updated version.
• Use the rest of the page for your individual notes. You can refer to these as you present, and I will refer to these as I review.
• You'll have 15 - 20 minutes, plus some time for questions. Everyone should present. How you divvy up the presenting is your decision.
• Speak mainly to how the site is designed to meet users' needs and priorities. Speak not only to the finished site but to the process: Design problems you ran into and how you solved them.
• To prepare, you might review the Final Checklists at the end of chaps 2 - 5. You'll find topics to address that you can select from.

• For a final review, I'll be looking at
  • the project itself: effectiveness at meeting your stated goals using the principles in Summers and Summers - 100
  • individually: a demonstrated understanding of principles of web design as presented in the Summers and Summers and in class.

• class meets. Qs on chap 5* upload what you have

Thurs 7 Dec

• workday

Tues 12 Dec

• class meets!
• some final notes
• preparing for your presentation

Tues 5 Dec

more to come

Final

• Friday, Dec 15, 1:00 - 3:00
• Each group will present what they have, talk about how they made choices, problems, success, and how their design decisions go back to their user profiles.

• All - and especially writers - read Chap 5: Creating Effective Content

Tues X Dec

• class meets. Qs on chap 5

• Meet to touch base
• Review what's been uploaded
• Upload what you have

Thurs 30 Nov

• workday

• Review what's up.

• Upload what you have.

• Meet in class to touch base.

• Upload what you have, even if it's rough.

Tues 28 Nov

• Tues, 21 Nov: Dreamweaver page layouts / templates and furniture.

• Deadline for Dreamweaver page templates and visual furniture!

Update

Class canceled due to illness. Use the time as a workday. We'll meet as usual on Thursday for the quiz.

Thurs 16 Nov

Tues 21 Nov

• Deadline for page templates and visual furniture!

• Make task assignments. Start Task Assignment area on your project page. Name people, tasks, due dates, and completed or not. Begin to record your work. Deadline for task assignments: Thursday, 9 Nov.

Thurs, 9 Nov

• Morgan is presenting in Mankato. Workday.

Tues 14 Nov

• Meet in class. Quiz on visual design elements.
• Then working time.

Thurs 16 Nov

• tba. Possibly deadlines for page templates and visual furniture.

• start Task Assignment area on your project page. Name people, tasks, due dates, and completed or not. Begin to record your work on this page.

• for Tues, 7 Nov: Read and markup chap 4: Visual Design

Completed syllabus items are moved to the CourseSyllabus page.

• '''Content inventory, site maps, nav, wireframes due
• present and review in class'''

Tues, 7 Nov

• class meets face to face
• move to Dreamweaver to set up site and create templates.
• discuss visual design from chap 4 and creating design mock ups.

ENGL 4169/5169: Web Content Writing will be offered this spring. If you're planning on taking it - and I'd recommend it - hang on to the Summers and Summers text. more here.

-- Completed syllabus items are moved to the CourseSyllabus page. --

ENGL 4169/5169: Web Content Writing will be offered this spring. If you're planning on taking it - and I'd recommend it - hang on to the Summers and Summers text. more here.

ENGL 4169/5169: Web Content Writing will be offered this spring. If you're planning on taking it - and I'd recommend it - hang on to the Summers and Summers text. more here.

ENGL 4169/5169: Web Content Writing will be offered this spring. If you're planning on taking it - and I'd recommend it - hang on to the Summers and Summers text. more here.

ENGL 4169/5169: Web Content Writing will be offered this spring. If you're planning on taking it - and I'd recommend it - hang on to the Summers and Summers text. more here.

Course announcement

!! Course announcement ENGL 4169/5169: Web Content Writing will be offered this spring. If you're planning on taking it - and I'd recommend it - hang on to Summers and Summers. more here.

deadlines

• Deadline: Midnight, Friday 20 Oct All user interviews and research done.

• Thurs, 2 Nov: Content inventory, site maps, nav, wireframes due present and review in class

• SiteProjectRequirementsGathering
• Site Project: Personas and Content Inventories
• Site Project: Experience Design: Site maps, wireframes and navigation.
• Some examples

I've left comments on the Persona pages and the Content Inventory pages. Be sure to develop your content inventory in detail, and drawing on the persona goals. (I've assigned provisional points on the content inventory so you can see how far you've come, and how far you need to go.) Your site maps, nav, and wireframes are going to depend on how much content you're including, and what kind of content you're including. Design the nav from the content up.

I've left comments on the Persona pages and the Content Inventory pages. Be sure to develop your content inventory in as much detail as you can, and drawing on the persona goals. (I've assigned provisional points on the content inventory so you can see how far you've come, and how far you need to go.) Your site maps, nav, and wireframes are going to depend on how much content you're including, and what kind of content you're including. Design the nav from the content up.

Sun 29 Oct

• I've left comments on the Persona pages and the Content Inventory pages. Be sure to develop your content inventory in as much detail as you can, and drawing on the persona goals. (I've assigned provisional points on the content inventory so you can see how far you've come, and how far you need to go.) Your site maps, nav, and wireframes are going to depend on how much content you're including, and what kind of content you're including. Design the nav from the content up.

• Start Site Project: Experience Design: Site maps, wireframes and navigation. Update: Don't prepare visual mock ups yet.

• develop site maps, wireframes, and navigation for each level or type of page on your site.

• Meet in class to review work
• Content inventory, site maps, nav, wireframes due present and review in class
• tentative: for Tues, 7 Nov, chap 4: Visual Design

Tues, 7 Nov.

• move to Dreamweaver to create templates, etc.

• Start Site Project: Experience Design: Site maps, wireframes, navigation, and first visual design mock ups.

• Review: How are personas developing? Names, contexts, user goals...

• Some examples

The pace of class is going to accelerate for a couple of weeks. You need to get started on personas and experience design materials so part of your group can move to Dreamweaver on Nov 7.

• Start designating tasks to group members. Keep track of who's doing what on your project page.

• develop site maps, wireframes, navigation, and visual design mock ups for each level or type of page on your site.
• update your content inventory

The pace of class is going to accelerate for a couple of weeks. You need to get started on personas and experience design materials so part of your group can get started with Dreamweaver.

• Meet in class. Chapter 3: User personas
• Start Site Project: Personas and Content Inventories
• Drafts of personas posted by classtime, Thurs, 26 Oct.
• Develop your content inventory as you develop the personas.
• Start designating tasks to group members. Keep track of who's doing what on your project page

• Start Site Project: Experience Design: Site maps, wireframes, navigation, and visual design mock ups.
• Finals of personas and well-developed content inventory due midnight Friday, 27 Oct.

You'll need to

• develop site maps, wireframes, visual design mock ups for each level or type of page on your site.
• assign tasks: Decide on how to split up the tasks and responsibilities

Deadline for Experience Design materials: Tues, 7 Nov. That's the day your group should move to Dreamweaver to create templates, etc.

Tues 7 Nov

• Start Dreamweaver. Set up a site folder on a flash drive. Select a computer to work on.

Thurs 26 Oct

• Meet in class.

• Decide on how to split up the tasks and responsibilities

Thurs 2 Nov

• meet in class to compare notes

Site Project: Requirements Gathering

• Meet in class. Chapter 3.
• Site Project: Personas and Content Inventories for Thurs, 26 Oct.

• Site Project: Experience Design: Site maps, wireframes, visual design mock ups, assign tasks
• Decides on how to split up the tasks and responsibilities

Tues 31 Oct:

• Work day. Morgan is out of town but you can still meet to work.

Deadline for Experience Design: Tues, 7 Nov. That's the day your group should move to Dreamweaver to create templates, etc

on deck

• site postioning : list of attributes exercise: (25)

• User interviews: revising interview questions, taking notes (33) and key findings (34) for each interview

• site postioning : list of attributes exercise: (25)

• Workday. You might want to meet f2f.
• Deadline: Midnight, Friday 20 Oct All user interviews and research done. Interview notes posted.
• For Tues, 24 Oct, read and annotate chap 3 Summers and Summers.

• Meet in class. Develop personas for Thurs, 26 Oct.
• Decide on work and responsibilities for chap 3.

Sat 14 Oct 9:00 am. I've left comments at the top your work pages. Most are coming along fine, some need more work: have a look. HuntingAndFishing and FiberArts have excellent interview questions, if you're looking for a good model. See everyone on Tuesday.

update Sat 14 Oct 9:00 am. I've left comments at the top your work pages. Most are coming along fine, some need more work: have a look. HuntingAndFishing and FiberArts have excellent interview questions, if you're looking for a good model. See everyone on Tuesday.

A network router to this server is going out intermittently and need to be restarted manually. If it goes out over the weekend, it can take some time to restore it. The University is aware of the problem and is looking for a way to repair it.

Patience.

If the server is down when you try to access it, try again in a couple of hours.

• Deadline: By Thursday midnight, you should have your site positioning research done and posted, user groups selected, and interview questions posted.
• You can begin interviewing and taking notes on your interviews once you have your interview questions formed. (taking notes (33) and key findings (34) for each interview)

• Touch base: Everyone stop by HS 109 at noon to compare notes.
  • site postioning : list of attributes exercise: (25)
  • user interviews: taking notes (33) and key findings (34) for each interview

• Then workday: Time for user interviews.

• Deadline: All user interviews and research done. Interview notes posted by midnight, Friday 20 Oct.

• Deadline: By Thursday midnight, you should have your site positioning research done and posted, user groups selected, interview questions posted.

• Deadline: By Thursday midnight, you should have your site research done and posted, user groups selected, interview questions posted.
• You can begin interviewing and taking notes on your interviews once you have interview questions formed.

• Touch base: Everyone stop by HS 109 at noon to compare notes. Then workday: Time for user interviews.
• Hand in print outs for Mod 11.

• Meet face to face in class to work and compare notes.
• Deadline: All user interviews and research done. Interview notes posted by midnight, Thurs 19 Oct.

• Meet in class. Start developing personas, chap 3 Summers and Summers.

• Deadline: By Thursday 6:00 pm, you should have your site research done and posted, user groups selected, interview questions posted.

• Touch base: Everyone stop by HS 109 at 12:00 to compare notes. Then workday: Time for user interviews.

• Meet face to face to work and compare notes.

• Debrief on connecting goals with design choices: Examples. 10 mins.

• Use your main group page as you need to: to plan, make connections, set schedules and make assignments. Update it as your project moves forward.
• Expect to be working on the project outside of class - both face to face and on the net. Figure 2 hours for every hour of classtime.
• Bring your copy of Summer and Summers to class each day. You'll need to refer to it.

update Saturday: Some are really moving into the SetUpAWikiNamePage. Have a look at Grant's, for instance.

update Saturday: Some are really moving into the SetUpAWikiNamePage. Have a look at GrantGartland/GrantGartland | Grant's]], for instance.

• Debrief on connecting goals with design: 10 mins.

Use your main group page as you need to: to plan, make connections, set schedules and make assignments. Update it as your project moves forward.

I've sketched out a template for Requirements Gathering, linked to the HuntingAndFishing page.

• Debrief on connecting goals with design: 10 mins,

• ID goals
• Develop your two sentence concept statement into a first draft of a purpose statement.
• Plan who to interview/visit, questions to ask, how to take notes, how to get those notes on the wiki, how to divide up the work.

Expect to be working on the project outside of class - both face to face and on the net. Figure 2 hours for every hour of classtime.

Bring your copy of Summer and Summers to class each day. You'll need to refer to it.

• Deadline: By the end of the day Thursday, you should have your site research done and posted, user groups selected, interview questions posted.

• Meet face to face to work.
• Deadline: All user interviews and research done. Interview notes posted.

Tues 10 Oct

• Debrief on connecting goals with design
• Work with chap 2 in Summers and Summers.
• Start Site Project: Requirements Gathering

• planning: who to interview/visit, questions to ask, how to take notes, how to get those notes on the wiki, how to divide up the work

Thurs 12 Oct

• Workday: continue Site Project: Requirements Gathering
• By the end of the day Thursday, you should have site research done and posted, user groups selected, interview questions posted.

Tues 17 Oct

• Workday: Time for user interviews.

Thurs 19 Oct

• All user interviews and research done. Interview notes posted.

Tues 24 Oct

• Start User personas, chap 3 Summers and Summers.

• finding your group
• On your group site page: develop at 1 - 2 sentence statement of what you might offer with your proposed site: a site concept that might be worth exploring to see if a site is necessary or appropriate. This can be in the form of a problem-solution statement, and the potential users you have in mind: who are they. HuntingAndFishing has a good example.
• You can begin to collect early notes on what to include for content. You can test these ideas when you begin to interview potential users.
• If you like, your group can start Site Project: Requirements Gathering

• On this page, you can begin to collect early notes on what to include for content. You can test these ideas when you begin to interview potential users.

• On your group site page: 1 - 2 sentence statement of what you might offer with your proposed site: a site concept that might be worth exploring to see if a site is necessary or appropriate. This can be in the form of a problem-solution statement, and the potential users you have in mind: who are they. HuntingAndFishing has a good example.

• On your group site page: 1 - 2 sentence statement of what you might offer with your proposed site: a site concept that might be worth exploring to see if a site is necessary or appropriate. This can be in the form of a problem-solution statement.
• and the potential users you have in mind: who are they.

• Mods 7 (Forms) and 8 (Importing MS Word docs) due.

• the people in your group
• 1 - 2 sentence statement of what you might offer with your proposed site: a site concept that might be worth exploring to see if a site is necessary or appropriate. This can be in the form of a problem-solution statement.
• the potential users you have in mind: who are they.

• developing your two sentence concept statement into a first draft of a purpose statement.

• Site Project: Requirements Gathering

Completed syllabus items are moved to the CourseSyllabus page.

Start the site project

• Read Summers, chap 2 to gain an overview of the first phase of the project, some conceptions of what might work as a site, and a sense of what you'll be doing for requirements gathering (eg: goal setting, site positioning research, observing and interviewing users).

Before leaving, submit a card with

• group name - not a project name because you won't know it yet.
• people in your group
• 1 - 2 sentence statement of what you might offer with your proposed site: a site concept that might be worth exploring to see if a site is necessary or appropriate
• potential users you have in mind

Thurs 5 Oct

• Intro to wiki
• for Tues, 10 Oct: SetUpAWikiNamePage

• developing your two sentence concept
• planning: who to interview/visit, questions to ask, how to take notes, how to get those notes on the wiki, how to divide up the work ...

Tues 10 Oct

• SiteProjectRequirementsGathering

• Hand in completed project materials. Include a brief (one-page tops) statement (word processed) indicating how your final design addresses your stated goals. Revise your materials so that your prototype clearly connects with the goals you have stated. That might mean revising your goals or your prototypes.

• Review Part 4 of Portfolio Site Prototype Project
• Revision of goals?

• Hand in completed project materials. Prepare a brief (one-page tops) statement (word processed) indicating how your final design addresses your stated goals. Revise your materials so that your prototype clearly connects with the goals you have stated. That might mean revising your goals or your prototypes.

• Hand in completed project materials. These should be revised so that your prototype clearly connects with the goals you have stated. That might mean revising your goals or your prototypes.

• Read Summers, chap 2 to gain an overview of the first phase of the project, some conceptions of what might work as a site, and a sense of what you'll be doing for requirements gathering (eg: observing and interviewing users).

• Hand in completed project materials.

Tues 3 Oct

• read Summers, chap 2 to gain an overview of the first phase of the project, some conceptions of what might work as a site, and a sense of what you'll be doing for requirements gathering (eg: observing and interviewing users).
• Come with some ideas for sites that can be created by 4 - 5 people over 9 weeks that address an existing need for a (local) audience.
• You will be either/or selling your idea to get group members, or looking for a group to join on Tuesday.

• Mods 1 and 2 due. Start 3 and 4, due Tues, 19 Sept.
  • Mod 3: print final version of Quark Express page
  • Mod 4: tba

Thurs 14 Sept

• Part 1 of Portfolio Site Prototype Project due

Tues 19 Sept

• Mods 3 and 4 due. Start 5 and 6
• Part 2 of Portfolio Site Prototype Project

Thurs 21 Sept

• Part 3 of Portfolio Site Prototype Project

Tues 26 Sept

• no classes

Thurs 28 Sept

• Mods 5 and 6 due. Start 7 and 8
• Part 4 of Portfolio Site Prototype Project

Tues 26 Sept

• no classes

• [Intro wiki]

• debrief on page description. Summers and Summers, p 7

• In a margin or on a separate page, Include some brief observations on usability: What features or elements seem to aid usability?

• Include some observations on usability: What features seem to aid usability? What features might get in the way?

• a portfolio page tba

• debrief on page description
• wireframes and notes: usability

More site description: PageDescriptionAnnotatedWireframes: updated a little

• Pay special attention to the nomenclature of the headings and global nav links
• http://www.getridofthings.com/index.html. Index page and a representative content page
• http://www.grandforksherald.com/ Index page and representative news story page

• Intro to the wiki
• for Tues, read Summers and Summers, chap 1.

• Intro to the wiki: SetUpAWikiNamePage

• Intro to the wiki: CreateAWikiNamePage?

• wireframes and notes: usability

• read Summers and Summers, chap 1.

Tues, 12 Sept

• Mods 1 and 2 due. Start 3 and 4, due Tues, 19 Sept

Thurs 13 Sept

• hand in PageDescriptionAnnotatedWireframes

• sites in class: focus on usability / user centered design
• create wireframes and usability notes in class

Tues, 5 Sept

• hand in annotated wireframes.
• review how Essentials is going.

on deck

Thurs, 7 Sept

• Intro to the wiki
• Start Summers and Summers, chap 1: Portfolio Site Prototype Project

Tues, 12 Sept

• Mods 1 and 2 due. Start 3 and 4, due Tues, 19 Sept
• Part 1 of portfolio due

Weeks 5 - 13: The Project

• forming groups
• Summers, chap 2: Requirements Gathering
• ...

• http://writing.colostate.edu/ - Wrting@CSU: Look around the site enough to find a representative page to work with. There may be more than one type of page.

• http://writing.colostate.edu/ - Wrting@CSU: Look around the site enough to sketch and annotate a representative page.

• http://web.mit.edu/newsoffice/ - MIT News Office. Look around the site enough to sketch and annotate a representative page. In case you're courious, here's MITs home page: http://web.mit.edu/

• http://web.mit.edu/newsoffice/ - MIT News Office. Look around the site enough to sketch and annotate a representative page. http://web.mit.edu/ - MIT home page
• http://writing.colostate.edu/ - CSU Wrting: Look around the site enough to sketch and annotate a representative page.

PageDescriptionAnnotatedWireframes using these pages

• http://web.mit.edu/newsoffice/ - MIT News Office. look at some news items and the nav bar to develop a typical page. http://web.mit.edu/ - MIT home page
• http://writing.colostate.edu/ - CSU Wrting: look around long enough to get a sense of what's typical in the layout to develop a typical wireframe.

• Get started on Essentials, modules 1 and 2 over the weekend to see if we run into problems. When finished, turn in a page printout of the completed mod. Mods I and 2 will be due Tues, 12 Sept.

• PageDescriptionAnnotatedWireframes

• Essentials, modules 1 and 2.

for Tues, 5 Sept

[more to come]

• How the Internet works (notes)

Thur, 31 Aug

• Observing websites: making wireframes and naming the parts: Web Design Handlist

• SiteDescriptionAnnotatedWireframes
• Essentials, modules 1 and 2

• Observing websites: Naming the Parts?

• Observing websites: [[Naming the Parts]

• Observing websites: wireframes, sketches, maps

%width=400px& | Obligatory Image

%width-400px& | Obligatory Image

(:cell:) (:cell:)

(:cell:) (:cell:)

(:table:) (:cell:) Attach:blairontv.jpg Δ (:cell:)

(:tableend:)

WebDesign/maningallery.jpg

• Observing websites: naming the parts: Web Design Handlist

Weeks 1 - 2

Weeks 3 - 4

Weeks 5 - 13: The Project

Week 5: The Project

• forming groups
• Summers, chap 2: Requirements Gathering
• ...

• Summers and Summers, chap 1: Portfolio Site Prototype Project

• Summers and Summers, chap 1: Portfolio Site Project?

Announcements

Aug 14 2006

Here's a rough syllabus for the first few weeks. Expect things to change.

Weeks 1 - 2

• Using the wiki

Weeks 3 - 4

ENGL 4170/5170: Web Design for Content Writers

Aug 14 2006

Here's a rough syllabus for the first few weeks:

Weeks 1 - 2

• Introductions
• How the Internet works
• Observing websites: neutral language, balcony view
• Observing websites: naming the parts
• Essentials, mods 1 and 2

Weeks 3 - 4

• Summers and Summers, chap 1: Creating a Portfolio Site
• Essentials, mods 3 and 4

• CourseResources

• CourseSyllabus
• CourseStatement

Very select supplemental readings

Very selected supplemental readings

• Writing for a Web Audience, Constance Petersen.

• Siegel, Kevin. Essentials of Macromedia Dreamweaver MX 2004. Skills and Drills. IconLogic, 2005. Amazon. Get the Dreamweaver 2004 MX edition. We're using Dreamweaver 2004 MX for 2006 - 2007.

Recommended

• Lynch and Horton. The Web Style Guide, 2nd edition. Yale UP, 2001 Available as an online book, or purchase a print version.

to do: * Put sites directory behind pw.

Materials

Resources

• Summers and Summers. Support for the text. Check here first for forms, lists, tutorials and explanations.
• Lynch and Horton. The Web Style Guide
• Copyright and using stuff from the web, from Summers and Summers

• Web Design Syllabus?
• Web Design Statement?

to do: * Rename wiki to fit in with Web Design. * Update about box. * Put sites directory behind pw.

to do:

• Rename wiki to fit in with Web Design.
• Update about box.
• Put sites directory behind pw.

• Summers and Summers. Support for the text. Check here first for forms, lists, tutorials and explanations.

• Copyright and using stuff from the web, from Summers and Summers

• Lynch and Horton. The Web Style Guide, 2nd edition. Available online, or purchase the book.

Resources

• Summers and Summers
• Lynch and Horton. The Web Style Guide

• Summers and Summers. Creating Websites that Work. Houghton Mifflin, 2005 - Amazon
• Seigal or Visual Start
• Lynch and Horton. The Web Style Guide, 2nd edition. Available online, or purchase the book.

Summers and Summers. Creating Websites that Work Houghton Mifflin, 2005 - Amazon

ENGL 4170/5170: Web Design for Content Writers

• Web Design Syllabus?
• Web Design Statement?

Required Texts

to do: Rename wiki to fit in with Web Design. Update about box.

Rename wiki to fit in with Web Design

Web Design for Content Writers

under development through August 28, 2006.

• Syllabus
• Statement

Texts