<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Lazy IA&#8217;s Guide to Making Sitemaps</title>
	<atom:link href="http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Tue, 18 Jun 2013 12:43:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: jamesmelzer</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5794</link>
		<dc:creator>jamesmelzer</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5794</guid>
		<description><![CDATA[I&#039;ve had some good luck with this Visio technique before. A couple of limitations are worth mentioning. Visio does not perform well with lots of boxes. It crashes a lot. Then there is the issue of formatting. The org chart wizard doesn&#039;t give a lot of options as far as when the finished product looks like.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve had some good luck with this Visio technique before. A couple of limitations are worth mentioning. Visio does not perform well with lots of boxes. It crashes a lot. Then there is the issue of formatting. The org chart wizard doesn&#8217;t give a lot of options as far as when the finished product looks like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fason</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5795</link>
		<dc:creator>fason</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5795</guid>
		<description><![CDATA[I would also like to comment on another amazing diagramming application called &lt;a href=&quot;http://www.omnigroup.com/applications/omnigraffle/pro/&quot; rel=&quot;nofollow&quot;&gt;OmniGraffle Pro&lt;/a&gt; from OmniGroup. I have been using the Pro version since version 3.0. In conjunction with &lt;a href=&quot;http://www.omnigroup.com/applications/omnioutliner/pro/&quot; rel=&quot;nofollow&quot;&gt;OmniOutliner&lt;/a&gt; (very similar to the Outline Mode for MS Word) you can import directly into OmniGraffle to make sitemap diagrams.

The OmniGraffle / Outliner combo is for MacOSX exclusive, but to be honest its the best out there. It allows importing/exporting of Visio XML Diagrams, exports PDFs, JPGs, etc. I cannot speak more highly of this app suite. Where they failed at OmniWeb, they far exceeded with OmniGraffle Pro.]]></description>
		<content:encoded><![CDATA[<p>I would also like to comment on another amazing diagramming application called <a href="http://www.omnigroup.com/applications/omnigraffle/pro/" rel="nofollow">OmniGraffle Pro</a> from OmniGroup. I have been using the Pro version since version 3.0. In conjunction with <a href="http://www.omnigroup.com/applications/omnioutliner/pro/" rel="nofollow">OmniOutliner</a> (very similar to the Outline Mode for MS Word) you can import directly into OmniGraffle to make sitemap diagrams.</p>
<p>The OmniGraffle / Outliner combo is for MacOSX exclusive, but to be honest its the best out there. It allows importing/exporting of Visio XML Diagrams, exports PDFs, JPGs, etc. I cannot speak more highly of this app suite. Where they failed at OmniWeb, they far exceeded with OmniGraffle Pro.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bryanjbusch</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5796</link>
		<dc:creator>bryanjbusch</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5796</guid>
		<description><![CDATA[OmniGraffle (Pro) 4 has a built-in outliner in a side window (&quot;Utilities&quot;) that will allow you to create your hierarchical text-only view of the site, and the program &lt;em&gt;simultaneously&lt;/em&gt; draws the site map while you work.

Granted, this probably removes the handy &quot;share with others&quot; benefit described in the article, but if you&#039;re main concern is saving time and effort, this is the method I recommend.]]></description>
		<content:encoded><![CDATA[<p>OmniGraffle (Pro) 4 has a built-in outliner in a side window (&#8220;Utilities&#8221;) that will allow you to create your hierarchical text-only view of the site, and the program <em>simultaneously</em> draws the site map while you work.</p>
<p>Granted, this probably removes the handy &#8220;share with others&#8221; benefit described in the article, but if you&#8217;re main concern is saving time and effort, this is the method I recommend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gordon</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5797</link>
		<dc:creator>gordon</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5797</guid>
		<description><![CDATA[After years of trying to create the world&#039;s greatest site map, I&#039;ve found that  the excel spreadsheet, all by itself, as displayed in step one - the input tab - does the trick. While lacking some of the visual appeal of a visio diagram, it provides many other benefits:
1. No issues with file formats - every client I&#039;ve worked with has Excel, while only a few have Visio
2. Allows clients to edit the site map or insert comments and questions.
3. Conveys the depth and breadth of a site at a glance.
4. Easily add additional notes, such as references to a requirements document
5. Easy to add other navigation oriented notation, such as footer links versus primary navigation.
6. No space limitations - no more &quot;oh no, my boxes are too big, this won&#039;t fit on a letter sized piece of paper, does our printer have any legal paper?&quot;
7. Major time saver: more time architecting, less time diagramming; allows information architects to focus on information architecture.]]></description>
		<content:encoded><![CDATA[<p>After years of trying to create the world&#8217;s greatest site map, I&#8217;ve found that  the excel spreadsheet, all by itself, as displayed in step one &#8211; the input tab &#8211; does the trick. While lacking some of the visual appeal of a visio diagram, it provides many other benefits:<br />
1. No issues with file formats &#8211; every client I&#8217;ve worked with has Excel, while only a few have Visio<br />
2. Allows clients to edit the site map or insert comments and questions.<br />
3. Conveys the depth and breadth of a site at a glance.<br />
4. Easily add additional notes, such as references to a requirements document<br />
5. Easy to add other navigation oriented notation, such as footer links versus primary navigation.<br />
6. No space limitations &#8211; no more &#8220;oh no, my boxes are too big, this won&#8217;t fit on a letter sized piece of paper, does our printer have any legal paper?&#8221;<br />
7. Major time saver: more time architecting, less time diagramming; allows information architects to focus on information architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donnamaurer</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5798</link>
		<dc:creator>donnamaurer</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5798</guid>
		<description><![CDATA[Thank you so much for the update. I was reading the old article recently and wondering whether I had the time to figure out for myself how to do this in V2003.]]></description>
		<content:encoded><![CDATA[<p>Thank you so much for the update. I was reading the old article recently and wondering whether I had the time to figure out for myself how to do this in V2003.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cdpapoulias</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5799</link>
		<dc:creator>cdpapoulias</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5799</guid>
		<description><![CDATA[I&#039;ve had some success with OpenOffice.org Draw instead of Visio, but the stencil support isn&#039;t there.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve had some success with OpenOffice.org Draw instead of Visio, but the stencil support isn&#8217;t there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allen</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5800</link>
		<dc:creator>allen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5800</guid>
		<description><![CDATA[Agree about not using sitemaps much - just get too busy for big sites and then there&#039;s all the exceptions... I put the sectional nav in Excel and flow-chart the exceptions (carts etc). However if I need something really good looking I&#039;ll use GraphViz (PC and Mac) to produce beautiful diagrams for IA from Excel but it is *quite* involved: You have to use the &#039;concatenate&#039; feature to write various pieces of column information into a single cell, then export that to a GraphViz friendly txt format. GraphViz can produce outstanding results but you have to sweat a little. http://www.graphviz.org/]]></description>
		<content:encoded><![CDATA[<p>Agree about not using sitemaps much &#8211; just get too busy for big sites and then there&#8217;s all the exceptions&#8230; I put the sectional nav in Excel and flow-chart the exceptions (carts etc). However if I need something really good looking I&#8217;ll use GraphViz (PC and Mac) to produce beautiful diagrams for IA from Excel but it is *quite* involved: You have to use the &#8216;concatenate&#8217; feature to write various pieces of column information into a single cell, then export that to a GraphViz friendly txt format. GraphViz can produce outstanding results but you have to sweat a little. <a href="http://www.graphviz.org/" rel="nofollow">http://www.graphviz.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: audcrane</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5801</link>
		<dc:creator>audcrane</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5801</guid>
		<description><![CDATA[Would second the OmniGraffle / OmniOutliner recommendation.

I try to use Excel-only also (per Gordon&#039;s excellent suggestion, especiall WRT the file format problem) but find it breaks down in two places:
• starts to be difficult to read past 2 levels
• doesn&#039;t easily allow for brief page descriptions

Does anyone have an example of Excel-only that does this well?]]></description>
		<content:encoded><![CDATA[<p>Would second the OmniGraffle / OmniOutliner recommendation.</p>
<p>I try to use Excel-only also (per Gordon&#8217;s excellent suggestion, especiall WRT the file format problem) but find it breaks down in two places:<br />
• starts to be difficult to read past 2 levels<br />
• doesn&#8217;t easily allow for brief page descriptions</p>
<p>Does anyone have an example of Excel-only that does this well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: octopus</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5802</link>
		<dc:creator>octopus</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5802</guid>
		<description><![CDATA[Great, but what can you do for Omnigraffle Professional?]]></description>
		<content:encoded><![CDATA[<p>Great, but what can you do for Omnigraffle Professional?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gordon</title>
		<link>http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5803</link>
		<dc:creator>gordon</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/the-lazy-ias-guide-to-making-sitemaps/#comment-5803</guid>
		<description><![CDATA[A few other points. First, I don&#039;t want to take away from the value and power of a visual - I think there&#039;s a need for simplifying the site mapping process, and I definitely want to try out these ideas. I find site maps especially useful in reports and presentations. 
One thing I&#039;ve found useful, refering back to the original excel spreadsheet - I like to label &quot;Level 1&quot; &quot;Level 2&quot; as &quot;1-Click&quot; and &quot;2-Click&quot;. Even though this doesn&#039;t account for all paths to a page, such as home page call-outs, or for the fact that many people don&#039;t start at the home page, it does make explicit the answer to a question that every client will ask. 
Also, I use a lot of columns. So, for example, I&#039;ll have a column for page summary, a column for recommended words of copy, a column for author, etc. Then, when I need to print, depending on the audience, I&#039;ll hide various columns. So, for authors, I&#039;ll focus on the &#039;number of words&#039;, &#039;author&#039;, etc; whereas for a developer, I&#039;d show a column indicating any modules (if the site is being built on a CMS or other platform). That way, the Excel file serves a lot of purposes. So, if it can feed some visio diagrams too - all the better!]]></description>
		<content:encoded><![CDATA[<p>A few other points. First, I don&#8217;t want to take away from the value and power of a visual &#8211; I think there&#8217;s a need for simplifying the site mapping process, and I definitely want to try out these ideas. I find site maps especially useful in reports and presentations.<br />
One thing I&#8217;ve found useful, refering back to the original excel spreadsheet &#8211; I like to label &#8220;Level 1&#8243; &#8220;Level 2&#8243; as &#8220;1-Click&#8221; and &#8220;2-Click&#8221;. Even though this doesn&#8217;t account for all paths to a page, such as home page call-outs, or for the fact that many people don&#8217;t start at the home page, it does make explicit the answer to a question that every client will ask.<br />
Also, I use a lot of columns. So, for example, I&#8217;ll have a column for page summary, a column for recommended words of copy, a column for author, etc. Then, when I need to print, depending on the audience, I&#8217;ll hide various columns. So, for authors, I&#8217;ll focus on the &#8216;number of words&#8217;, &#8216;author&#8217;, etc; whereas for a developer, I&#8217;d show a column indicating any modules (if the site is being built on a CMS or other platform). That way, the Excel file serves a lot of purposes. So, if it can feed some visio diagrams too &#8211; all the better!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
