<?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: Flexible Sitemaps</title>
	<atom:link href="http://wireframes.linowski.ca/2009/01/flexible-sitemaps/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/</link>
	<description>Because every IA has something funky up their sleeve</description>
	<lastBuildDate>Wed, 28 Jul 2010 06:45:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Travis Schmeisser</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-859</link>
		<dc:creator>Travis Schmeisser</dc:creator>
		<pubDate>Sat, 25 Apr 2009 14:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-859</guid>
		<description>I&#039;ve switched to a method like this and it really does save time and make for easier revisions. When showing to clients, I&#039;ve found the lines don&#039;t help denote hierarchy any more than this. You can also move to indenting with a line extra deep pages if you find the color and tone don&#039;t work deeper. </description>
		<content:encoded><![CDATA[<p>I&#039;ve switched to a method like this and it really does save time and make for easier revisions. When showing to clients, I&#039;ve found the lines don&#039;t help denote hierarchy any more than this. You can also move to indenting with a line extra deep pages if you find the color and tone don&#039;t work deeper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sticky Sitemaps &#8250; Wireframes Magazine</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-328</link>
		<dc:creator>Sticky Sitemaps &#8250; Wireframes Magazine</dc:creator>
		<pubDate>Fri, 27 Feb 2009 09:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-328</guid>
		<description>[...] need for flexible design documents such as sitemaps has already been noted in the past. In this example however, instead of using the computer, a very similar style of [...]</description>
		<content:encoded><![CDATA[<p>[...] need for flexible design documents such as sitemaps has already been noted in the past. In this example however, instead of using the computer, a very similar style of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Linowski</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-216</link>
		<dc:creator>Jakub Linowski</dc:creator>
		<pubDate>Tue, 17 Feb 2009 19:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-216</guid>
		<description>In this sample at least, all number references contain no relationships. Perhaps these related links is something which could be set in the sitemap itself or in another document if they are very complex. In the sitemap for example, a new section could be created to group related or similar pages together. I just find that keeping relationships out of the numbering scheme affords more flexibility. That&#039;s all. </description>
		<content:encoded><![CDATA[<p>In this sample at least, all number references contain no relationships. Perhaps these related links is something which could be set in the sitemap itself or in another document if they are very complex. In the sitemap for example, a new section could be created to group related or similar pages together. I just find that keeping relationships out of the numbering scheme affords more flexibility. That&#039;s all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: josh</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-205</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Tue, 17 Feb 2009 19:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-205</guid>
		<description>Excuse the very very late reply.  How do you represent crosslinking or related links without the use of numbering? ie.  A &quot;Related Links&quot; nav that displays a grouping of related content that lives elsewhere on the site? I ask this as I want to move away from numbering my IAs while still making the flow chart easy to reference.  Hope i&#039;m making sense. Thanks! </description>
		<content:encoded><![CDATA[<p>Excuse the very very late reply.  How do you represent crosslinking or related links without the use of numbering? ie.  A &quot;Related Links&quot; nav that displays a grouping of related content that lives elsewhere on the site? I ask this as I want to move away from numbering my IAs while still making the flow chart easy to reference.  Hope i&#039;m making sense. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyesha</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-38</link>
		<dc:creator>Tyesha</dc:creator>
		<pubDate>Tue, 13 Jan 2009 23:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-38</guid>
		<description>I really like this and not just for the time savings of not messing with lines and arrows. I never want the &quot;bubbles&quot; on my site maps to be considered Pages, they are pieces of content or functionality that are living in a certain hierarchical structure.  Thinking about it this way allows this stage of the process to be separated from the design stage. If no one is attached to something being a &quot;Page&quot; then you have lots of freedom to design in the best way possible (layers, tabs, ajax, scrolling, floating, swilling, whatever...) 
 
This type of visual design really helps express the non-pageness of the bubbles. 
 
Thanks! </description>
		<content:encoded><![CDATA[<p>I really like this and not just for the time savings of not messing with lines and arrows. I never want the &quot;bubbles&quot; on my site maps to be considered Pages, they are pieces of content or functionality that are living in a certain hierarchical structure.  Thinking about it this way allows this stage of the process to be separated from the design stage. If no one is attached to something being a &quot;Page&quot; then you have lots of freedom to design in the best way possible (layers, tabs, ajax, scrolling, floating, swilling, whatever&#8230;) </p>
<p>This type of visual design really helps express the non-pageness of the bubbles. </p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Linowski</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-37</link>
		<dc:creator>Jakub Linowski</dc:creator>
		<pubDate>Tue, 13 Jan 2009 23:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-37</guid>
		<description>Thanks Tai. Will have to have a look at Omnigraffle one day. :) </description>
		<content:encoded><![CDATA[<p>Thanks Tai. Will have to have a look at Omnigraffle one day. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Linowski</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-36</link>
		<dc:creator>Jakub Linowski</dc:creator>
		<pubDate>Tue, 13 Jan 2009 22:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-36</guid>
		<description>I used Illustrator for the above example. Will have to check out MindManager. Thanks for the tip. </description>
		<content:encoded><![CDATA[<p>I used Illustrator for the above example. Will have to check out MindManager. Thanks for the tip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tai Toh</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-30</link>
		<dc:creator>Tai Toh</dc:creator>
		<pubDate>Tue, 13 Jan 2009 16:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-30</guid>
		<description>Hi Jakub,  
 
Great to see this site coming along.  Omnigraffle is quite good for traditional sitemaps and Hierarchical organizational charts.  It has an &quot;outlining&quot; feature that allows you to easily input and nest new objects.  I don&#039;t know about @Josh&#039;s question regarding numbering--I don&#039;t think it does it. 
 
Great work. Keep the content coming. </description>
		<content:encoded><![CDATA[<p>Hi Jakub,  </p>
<p>Great to see this site coming along.  Omnigraffle is quite good for traditional sitemaps and Hierarchical organizational charts.  It has an &quot;outlining&quot; feature that allows you to easily input and nest new objects.  I don&#039;t know about @Josh&#039;s question regarding numbering&#8211;I don&#039;t think it does it. </p>
<p>Great work. Keep the content coming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruven Gotz</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-27</link>
		<dc:creator>Ruven Gotz</dc:creator>
		<pubDate>Sun, 11 Jan 2009 23:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-27</guid>
		<description>Have you investigated using a mind mapping tool for this task? The lines redraw automatically, and the hierarchy formatting is applied automatically. As changes are made by simply dragging and dropping, all the lines and formatting magically update. I have been using MindManager for just this purpose and it works very well. </description>
		<content:encoded><![CDATA[<p>Have you investigated using a mind mapping tool for this task? The lines redraw automatically, and the hierarchy formatting is applied automatically. As changes are made by simply dragging and dropping, all the lines and formatting magically update. I have been using MindManager for just this purpose and it works very well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Linowski</title>
		<link>http://wireframes.linowski.ca/2009/01/flexible-sitemaps/comment-page-1/#comment-26</link>
		<dc:creator>Jakub Linowski</dc:creator>
		<pubDate>Sun, 11 Jan 2009 19:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=44#comment-26</guid>
		<description>Hey Josh. 
One other thing which I try to stay clear of when numbering are nested references such as &quot;Wireframe 3.2.1.4&quot; where the numbers represent (and duplicate) relationships and structure. For example, in this same sitemap example above I only create one number references such as &quot;W02&quot; or &quot;W12&quot; which are independent from content structure. This gives a bit more flexibility as it decreases the need to update the numbers after rearranging. Hope that helps? </description>
		<content:encoded><![CDATA[<p>Hey Josh.<br />
One other thing which I try to stay clear of when numbering are nested references such as &quot;Wireframe 3.2.1.4&quot; where the numbers represent (and duplicate) relationships and structure. For example, in this same sitemap example above I only create one number references such as &quot;W02&quot; or &quot;W12&quot; which are independent from content structure. This gives a bit more flexibility as it decreases the need to update the numbers after rearranging. Hope that helps?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
