Monday, March 9, 2009

Interface & Information Architecture, Part I

Group:
My portfolio is not so voluminous that the groups are not self-evident: Print, Websites and Motion Graphics. Mixing my pieces up via other nomenclature would definitely confuse the user.

Site Map:

A site map is a flow chart representing every page in my portfolio. When I arrange my ideas logically, users will not feel lost as they navigate through the digital portfolio site.
Additionally, a site map will help me answer several questions before I start building: 1. Will the user go directly from the homepage to view the work (or will there be a second level of navigation to access each group?); 2. Will all the work in a group be equally available (no hierarchy) or do I want to guide the user’s experience in order to view specific pieces in a specific sequence?

A successful site map shows three things at a glance:
1. Grouping – In may case, Print, Websites and Motion Graphics
2. Hierarchy – Where each page fits within the site
3. Connections – What will link from each page? (Since I plan to create my digital portfolio in Flash, there will be no links to outside sites, yes?)

The site map will account for every page on my digital portfolio site: A homepage from which each group’s page will branch – Portfolio (Print, Websites and Motion Graphics); Global pages (1. Bio; 2. Resume; and 3. Contact) will be accessible from any page.

It’s crucial to keep the concept of modularity in mind when creating the digital portfolio. Can the different pages be easily updated as new projects accrue; will it be easy to delete outdated/second-rate projects? This is particularly important for portfolios created in Flash – group interface elements together in timeline layers; create reusable symbols! If you fail to do this, you won’t be able to add a new link to the main nav bar!

“Schematic” and “Look and Feel” will follow (soon) in Interface & IA, Part II.

No comments:

Post a Comment