Edit | Search | Print | Upload
History | Recent Changes

About this wiki
M C Morgan
Dept of English
Bemidji State University

Web Design

Participants

Project Workspaces

Sites - fall 2007

Sites - fall 2006

NorthernLights


Related Courses


Index
AllRecentChanges
Documentation Index
web design rss feed
all-site rss feed

pmwiki.org
edit SideBar pmwiki-2.1.beta3

WebDesign > SiteProjectExperienceDesign

WebDesign.SiteProjectExperienceDesign History

Hide minor edits - Show changes to markup

November 01, 2007, at 11:01 AM by morgan -
Changed lines 11-12 from:

Work from your user personas and your content inventory as you design the site. Keep them in front of you as you work. I will being aksing you to connect your design decisions to the user goals you developed in the user personas.

to:

Work from your user personas and your content inventory as you design the site. Keep them in front of you as you work. I will being asking you to connect your design decisions to the user goals you developed in the user personas.

October 26, 2006, at 06:53 AM by morgan -
Changed lines 24-27 from:
  • Include navigation on your wireframes. Make them large enough to work with.

Visual designs will come next, in chap 4.
to:
  • Include navigation nomentclature on your wireframes. Make them large enough to work with.

Visual design comes next, in chap 4.
October 26, 2006, at 06:49 AM by morgan -
Changed lines 9-12 from:

Whoever is doing visual design mock ups should refer at Chap 4: Effective Visual Design. Expect to be revising your mock ups as the site develops.

You won't be able to do these on the wiki, so turn to whatever means you find comfortable: page layout, tagboard and markers, whatever.

to:

You won't be able to do the site map and wireframes on the wiki, so turn to whatever means you find comfortable: page layout, tagboard and markers, whatever.

Changed lines 26-32 from:

The visual mockups

  • Don't become too attached to these as your design will change once you try to work it out in Dreamweaver.
  • Make notes on the mockups, enough that others can follow them.
  • Usability and legibility are central, so skip the colored and textured backgrounds behind text. Both are passé anyway.
  • Skip, too, script fonts for reading and nav. Again, refer to Summers and Summers, chap 4.
  • Keep in mind that you are designing for screens, not print, and that you do not have complete control over placement. Design within the constraints.
to:

Visual designs will come next, in chap 4.

October 26, 2006, at 06:43 AM by morgan -
Changed lines 1-2 from:

Refer to Summers and Summers, chap 3, pp 49 - 65.

to:

Refer to Summers and Summers, chap 3, pp 49 - 65. The chapter covers method, level of detail, and set out criteria.

Added lines 7-8:

Did I mention this? Refer to Summers and Summers, chap 3, pp 49 - 65.

Added lines 15-16:

When in doubt as to what to include or what level of detail to work in, refer to Summers and Summers.

Changed line 19 from:
  • Level of detail: name the pages to indicate what each one will contain.
to:
  • Level of detail: include section names and page names.
October 26, 2006, at 05:31 AM by morgan -
Added lines 11-12:

Work from your user personas and your content inventory as you design the site. Keep them in front of you as you work. I will being aksing you to connect your design decisions to the user goals you developed in the user personas.

October 26, 2006, at 05:24 AM by morgan -
Changed lines 27-28 from:
to:
  • Keep in mind that you are designing for screens, not print, and that you do not have complete control over placement. Design within the constraints.
October 26, 2006, at 05:22 AM by morgan -
Changed lines 12-14 from:
  • Work from your content inventory and user goals to develop the site map, and from the map to navigation and wireframes.
  • Don't over design. Your site can be very simple and compact, on one level, with all the navigation visible on every page.
to:
  • Work from your content inventory and user goals to develop the site map, and from the map to develop navigation and wireframes.
  • Level of detail: name the pages to indicate what each one will contain.
  • Don't over-design. Your site can be very simple and compact, on one level, with all the navigation visible on every page.
October 25, 2006, at 06:55 AM by morgan -
Changed line 11 from:

=== The map ===

to:

The map

Changed line 15 from:

=== The wireframes ===

to:

The wireframes

Added line 17:
  • Refer back to your first set of wireframes and sketches from the web: hard bottom or soft? flexible layout or static?
Changed lines 21-23 from:

=== The visual mockups ===

  • Don't go over board on these as your design will change once you try to work it in Dreamweaver.
  • Make notes on the mockups, enough that others can follow them.
to:

The visual mockups

  • Don't become too attached to these as your design will change once you try to work it out in Dreamweaver.
  • Make notes on the mockups, enough that others can follow them.
Deleted line 26:
October 25, 2006, at 06:53 AM by morgan -
Changed lines 5-11 from:

You'll want to work together as well as designate tasks to individual members. For vis design mock ups, refer at chap 4: Effective Visual Design. Expect to be revising your mock ups as the site develops.

Look also to chap 5 to design information.

[more to come]

to:

You'll want to work together as well as designate tasks to individual members.

Whoever is doing visual design mock ups should refer at Chap 4: Effective Visual Design. Expect to be revising your mock ups as the site develops.

You won't be able to do these on the wiki, so turn to whatever means you find comfortable: page layout, tagboard and markers, whatever.

=== The map ===

  • Work from your content inventory and user goals to develop the site map, and from the map to navigation and wireframes.
  • Don't over design. Your site can be very simple and compact, on one level, with all the navigation visible on every page.

=== The wireframes ===
  • Create a wireframe for each major kind of page. Anticipate that your home page might be laid out differently than the content pages.
  • This is the time to experiment with different layouts. Again, refer to your user personas and their goals to make design choices.
  • Include navigation on your wireframes. Make them large enough to work with.

=== The visual mockups ===
  • Don't go over board on these as your design will change once you try to work it in Dreamweaver.
  • Make notes on the mockups, enough that others can follow them.
  • Usability and legibility are central, so skip the colored and textured backgrounds behind text. Both are passé anyway.
  • Skip, too, script fonts for reading and nav. Again, refer to Summers and Summers, chap 4.

Changed lines 29-33 from:

I'll be evaluating your materials using the checklist on pp 63 - 64.

to:

I'll be evaluating your materials using the checklist on pp 63 - 64, but I will return them to you right away.

October 22, 2006, at 11:32 AM by morgan -
Added lines 5-9:

You'll want to work together as well as designate tasks to individual members. For vis design mock ups, refer at chap 4: Effective Visual Design. Expect to be revising your mock ups as the site develops.

Look also to chap 5 to design information.

October 22, 2006, at 11:24 AM by morgan -
Changed lines 3-13 from:
to:

This is one of the trickiest and the most essential steps in design, so don't short it. Chapter 3 in Summers and Summers is a good guide to developing your site map, wireframes, navigation, terminology, and visual design. We'll look at some techniques and criteria in class.

[more to come]

Use the advice of the chapter and the checklist on pp 63 - 64 to help you design these materials. The lists are there to help you check and develop your design work; they do not guarantee success.

I'll be evaluating your materials using the checklist on pp 63 - 64.

October 22, 2006, at 11:05 AM by morgan -
Added lines 1-3:

Refer to Summers and Summers, chap 3, pp 49 - 65.

Edit - History - Print - Recent Changes - Search
Page last modified on November 01, 2007, at 11:01 AM
We share. This work is licensed under Creative Commons Licenses. See About This Wiki for details. Linking is always permitted.

PmWiki can't process your request

Cannot acquire lockfile

We are sorry for any inconvenience.