<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;Information Design&gt;Sitemaps</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Information-Design/Sitemaps</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Information Design and Sitemaps in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Web Design&gt;Information Design&gt;Sitemaps</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Information-Design/Sitemaps</link>
	</image>
	<item>
		<title>Here Be Content</title>
		<link>http://tc.eserver.org/34558.html</link>
		<guid>http://tc.eserver.org/34558.html</guid>
		<description>I have always liked the idea of medieval mapmakers using the phrase &quot;Here Be Dragons&quot; to denote unexplored or dangerous territories.  Sticking a fire-breathing reptile in documentation when you run out of facts? That’s panache.&#xD;&#xD;These days, people aren’t so stylish. When an information architect (or user experience designer) doesn’t have the time (or the talent) to document content requirements, they stick a &quot;page stack&quot; on their site map.</description>
	</item>
	<item>
		<title>A Map-Based Approach to a Content Inventory</title>
		<link>http://tc.eserver.org/29673.html</link>
		<guid>http://tc.eserver.org/29673.html</guid>
		<description>A map-based approach to building a content inventory allows it to be a tool from the concept stages and throughout the life of the website. Patrick Walsh tells us why to use them, shows us how to create the maps, and how to leverage them over the long haul.</description>
	</item>
	<item>
		<title>The Lazy IA&apos;s Guide to Making Sitemaps</title>
		<link>http://tc.eserver.org/26779.html</link>
		<guid>http://tc.eserver.org/26779.html</guid>
		<description>Sitemaps are common deliverables, desired by clients who want a visual representation of a site. Since they are rarely used to make decisions, information architects may not consider them the valuable tools they are. The effort required to make and maintain them requires time that might be better used elsewhere. In fact, I would suggest that making sure the little boxes line up is a waste of an IA&apos;s mental abilities.</description>
	</item>
	<item>
		<title>Site Diagrams: Mapping an Information Space</title>
		<link>http://tc.eserver.org/25617.html</link>
		<guid>http://tc.eserver.org/25617.html</guid>
		<description>Site diagrams can be quite helpful in answering all kinds of hard questions. How to create the right diagram became a personal challenge for Jason Withrow. He shares his story through tips and techniques…</description>
	</item>
	<item>
		<title>Dynamic Dueling: Grappling with Java-Based Site Maps</title>
		<link>http://tc.eserver.org/23057.html</link>
		<guid>http://tc.eserver.org/23057.html</guid>
		<description>When I compare the usability of the highly graphical MAPA dynamic site map with that of a more traditional text-based table of contents, the traditional approach wins hands-down. You can scan the contents much faster and you don&apos;t need a fast connection or a Java-enabled browser.</description>
	</item>
	<item>
		<title>Maps of Web Sites</title>
		<link>http://tc.eserver.org/23018.html</link>
		<guid>http://tc.eserver.org/23018.html</guid>
		<description>Web site maps are created by webmasters and content providers to help users navigate and search complex web sites. A variety of styles of map are used, many based on organisational charts. Presented here are some of the best examples from around the Web.</description>
	</item>
	<item>
		<title>The Problem(s) With Sitemaps</title>
		<link>http://tc.eserver.org/23016.html</link>
		<guid>http://tc.eserver.org/23016.html</guid>
		<description>I believe the most important thing to consider when building a sitemap is what kind of experience do you want to give the user.</description>
	</item>
	<item>
		<title>A Sitemap on Every Page</title>
		<link>http://tc.eserver.org/23015.html</link>
		<guid>http://tc.eserver.org/23015.html</guid>
		<description>About how to use a sitemap on all of one&apos;s web pages. Includes  some statistics, that you will see below, that encourage rethinking navigation on small web sites. A sitemap on every page is an interesting  idea. I&apos;ve only seen this done in a few cases, and usually it is not done  well. However, Peter obviously spent some time working on his and he  solicited feedback form users.</description>
	</item>
	<item>
		<title>Web Site Maps from Dynamic Diagrams</title>
		<link>http://tc.eserver.org/23017.html</link>
		<guid>http://tc.eserver.org/23017.html</guid>
		<description>The Web site map is one of the key tools that site designers can provide to help surfers successfully navigate through their site. However, the art and science of creating intuitive and useful Web site maps is still in its infancy.</description>
	</item>
	<item>
		<title>Sitemaps and Site Indexes: What They Are and Why You Should Have Them</title>
		<link>http://tc.eserver.org/21395.html</link>
		<guid>http://tc.eserver.org/21395.html</guid>
		<description>Sitemaps and site indexes are forms of supplemental navigation. They give users a way to navigate a site without having to use the global navigation. By providing a way to visualize and understand the layout and structure of the site, a sitemap can help a lost or confused user find her way.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Information-Design/Sitemaps.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>