SIGIA-L Mail Archives: Re: [Sigia-l] Site maps for web apps, vs for content sites?
Re: [Sigia-l] Site maps for web apps, vs for content sites?
The easiest way to apply a site map to an interaction flow is to turn the
site map on its side and show all page hierarchies -and- workflows from
left to right. This way, you don't have to worry about the distinction
between hierarchical page relationships vs. workflow page relationships,
and you don't have the design challenge of throwing a workflow into
something that looks like an org chart.
> another look at a particular deliberable:
>> Site maps generally fall into two different categories:- those that
>> the navigational structure of the site, and those that describe
>> flow. As the days of enormous, static sites vignette to make way for
>> driven by logic not links, we naturally see a shift in emphasis from
>> navigational maps to those which document interaction. The question
>> exploring, however, is can this form of documentation continue to prove
>> useful and a valuable investment of resources?
> I'm liking the approach he's come up with.
> When replying, please *trim your post* as much as possible.
> *Plain text, please; NO Attachments
> Searchable Archive at http://www.info-arch.org/lists/sigia-l/
> IA 06 Summit. Mark your calendar. March 23-27, Vancouver, BC.
> Sigia-l mailing list -- post to: Sigia-l_at_asis.org
> Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable Archive at http://www.info-arch.org/lists/sigia-l/
IA 06 Summit. Mark your calendar. March 23-27, Vancouver, BC. http://www.iasummit.org/
Sigia-l mailing list -- post to: Sigia-l_at_asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
This archive was generated by hypermail 2.1.6
: Thu Feb 09 2006 - 07:41:40 EST