<?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: SDL Tridion sitemap/navigation rendering &lt; 5s</title>
	<atom:link href="http://www.albertteboekhorst.com/tridion_how_to/sdl-tridion-sitemapnavigation-rendering-1s/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.albertteboekhorst.com/tridion_how_to/sdl-tridion-sitemapnavigation-rendering-1s/</link>
	<description>Web Content Management</description>
	<lastBuildDate>Fri, 27 Aug 2010 13:32:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dominic Cronin</title>
		<link>http://www.albertteboekhorst.com/tridion_how_to/sdl-tridion-sitemapnavigation-rendering-1s/comment-page-1/#comment-1971</link>
		<dc:creator>Dominic Cronin</dc:creator>
		<pubDate>Fri, 25 Dec 2009 12:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.albertteboekhorst.com/?p=401#comment-1971</guid>
		<description>I wouldn&#039;t say that the &quot;established way&quot; of generating a site map in Tridion is to traverse the structure via large numbers of API calls. Far from it; there are various much more efficient approaches that are in widespread use. Mostly the technique involves a recursive GetListItems at publication level (i.e. a single API call), and then some XSLT. In practice you will probably use more than one API call, but a full traversal is way over the top. 

That&#039;s not to say that there&#039;s anything wrong with your technique, just that the comparison with CMS-side techniques isn&#039;t fair.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t say that the &#8220;established way&#8221; of generating a site map in Tridion is to traverse the structure via large numbers of API calls. Far from it; there are various much more efficient approaches that are in widespread use. Mostly the technique involves a recursive GetListItems at publication level (i.e. a single API call), and then some XSLT. In practice you will probably use more than one API call, but a full traversal is way over the top. </p>
<p>That&#8217;s not to say that there&#8217;s anything wrong with your technique, just that the comparison with CMS-side techniques isn&#8217;t fair.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SDL Tridion Folder &#124; Albert te Boekhorst</title>
		<link>http://www.albertteboekhorst.com/tridion_how_to/sdl-tridion-sitemapnavigation-rendering-1s/comment-page-1/#comment-1521</link>
		<dc:creator>SDL Tridion Folder &#124; Albert te Boekhorst</dc:creator>
		<pubDate>Mon, 04 May 2009 08:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.albertteboekhorst.com/?p=401#comment-1521</guid>
		<description>[...] It is good practice to use the folder structure for generating the main navigation for the website. Using the folder structure for the navigation gives content editors a solid view of the navigation as opposed to other options. The drawback is that generating the navigation structure from within Tridion is slow. However there are remedies to this (todo: write about advanced navigation structure rendering) [...]</description>
		<content:encoded><![CDATA[<p>[...] It is good practice to use the folder structure for generating the main navigation for the website. Using the folder structure for the navigation gives content editors a solid view of the navigation as opposed to other options. The drawback is that generating the navigation structure from within Tridion is slow. However there are remedies to this (todo: write about advanced navigation structure rendering) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
