The sitemap focuses on the structure of the visible navigation system plus any additional links found on a page that changes the topic of information flow to that of something not related to the page being viewed. For example, if a "Hot News" item is speaking of a new management team and there's links to the manager's profile, this is not reflected on the sitemap since it is being provided in a context form. Overall, I'm not to sure if this is the correct way of analyzing the effectiveness of a site's structure. I'm open to suggestions on what should be included in the sitemap and what shouldn't be. Sitemap split into
Analysis of current sitemap:
Overall a bit confusing, yet it's only made of four levels, which contain about 45-50 links. I will develop a new sitemap based on my readings and study of information architecture in the next several days. At the moment, a quick rough idea for goal specifics would be to reduce the number of structural navigation links by 50% and reduce the number of levels by 1.
1 comment:
I'm not sure if you mean the sitemap itself or the site represented in the sitemap. For the site represented in the sitemap, it's mostly college students living on-campus. The demographics include freshmen to juniors, age 18 to 21 who live on campus. Since all students are required to live on campus until their senior year, this includes the majority of the student body.
But if you meant the sitemap as itself... I developed my sitemap to help myself get a good picture of how the website is structured at the moment. I'm planning on using it as a common base for comparison to everything that will be done for improvement.
Post a Comment