[Sigia-l] depicting lifecycle in site maps?

[Jonathan Baker-Bates]

> It got me thinking though ... how do others handle this problem?

In pretty much the same way as you did. Last time this happened I too
used layers as a matter of fact.

I also take the precaution of declaring the site map document dead once
the project settles down and we get into the detail with prototyping and
documentation. Attempting to use a conventional site map to capture
anything other than conceptual content relationships (and perhaps a
couple of other dimensions) is asking for trouble in my experience. I
find that once stakeholders get the idea of the general picture, they
need to focus on the real design artefacts.

That's just the way I work though - I know others have lots of success
maintaining vast site maps with symbols all over them. I just don't know
how they have the time.



> -----Original Message-----
> From: sigia-l-bounces at asis.org 
> [mailto:sigia-l-bounces at asis.org] On Behalf Of Eric Scheid
> Sent: 20 July 2007 11:21
> To: sigia l
> Subject: [Sigia-l] depicting lifecycle in site maps?
> 
> I've recently worked on a websites which was complicated by 
> the fact that there was a planned lifecycle involved: ie. the 
> site at launch time was one structure (for a given 
> purpose/audience), time would pass, and the structure of the 
> site would need to change as the purpose for the site 
> changed. The amount of change wasn't that great, but I know 
> of other sites where the planned change over time would be 
> much more drastic.
> 
> Thankfully, the site was relatively small and simple, and so 
> planning out the structure in a site map wasn't too 
> complicated. I simply drew up the whole site, with all pages 
> from all stages of the lifecycle, and annotated the nodes as 
> to when they appeared/disappeared. I also split them into 
> different layers, so I could print out the site map as it 
> would appear at the various life cycle stages.
>  
> It got me thinking though ... how do others handle this problem?
> 
> e.
> 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________