Forum Moderators: phranque

Message Too Old, No Replies

storyboards/conceptual web site maps

got effective ways of documenting and keeping track of sites?

         

msampson

5:04 pm on Apr 8, 2002 (gmt 0)

10+ Year Member



hi

i'm looking for a good way of conceptually mapping our site, not as a navigation tool, but as a way of letting members of the company i work for see clearly how site flow works, what functionality is where, and then planning and documenting any changes. ideally it would be in a form that people could print out and take to meetings, with a master version pinned up on a big wall.

does anyone have any good examples or templates of such a thing?

the particular site i'm doing is a fairly linear web application rather than a trad get anywhere from anywhere website.

thanks in advance

miles

(edited by: msampson at 5:23 pm (utc) on April 8, 2002)

Shane

5:17 pm on Apr 8, 2002 (gmt 0)

10+ Year Member




It is not perfect but what we do is use a sticky board with the pages temporarily stuck to them to show flow order. It works for showing flow during a meeting.

We document the overall flow in Visio. Cumbersome, but it works. Any graphics package would probably allow the same functionality.

..... Shane

mivox

5:36 pm on Apr 8, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I know GoLive is supposed to have a "site layout" feature where you can basically build an interlinked site diagram with page icons & whatnot, and then integrate it directly into your workflow as you construct the actual site, but I've never used that particular feature...

msampson

3:45 pm on Apr 9, 2002 (gmt 0)

10+ Year Member



thanks for the replies.

for those visio people out there, have you found a way to create a front page with a site flow map that allows people to click thru to see details of each specific page?

three other things:

how do you display things like navs, variations of which appear all over the place? do you put them in once and refer to them, or do you include them on every page?

do you include look and feel of the pages or do you try and cut it down to pure functionality?

how would you go about including extra information like the way a user's inputs on a registration page are validated?

cheers

miles