<?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: Jumpchart + Drupal</title>
	<atom:link href="http://gluue.com/2009/09/jumpchart-drupal/feed/" rel="self" type="application/rss+xml" />
	<link>http://gluue.com/2009/09/jumpchart-drupal/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 17 Mar 2026 18:34:31 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.8.41</generator>
	<item>
		<title>By: Dan Frydman</title>
		<link>http://gluue.com/2009/09/jumpchart-drupal/comment-page-1/#comment-135</link>
		<dc:creator><![CDATA[Dan Frydman]]></dc:creator>
		<pubDate>Sun, 13 Sep 2009 16:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://pasteinteractive.com/blog/?p=651#comment-135</guid>
		<description><![CDATA[Yes, it is very cool!

We&#039;re actively using Jumpchart to build sitemaps then export to WordPress.

With just a few tweaks to Drupal we&#039;ve been able to do the following:

1. Preserve the path that&#039;s automatically generated in WordPress after the XML import it done.

2. Keep the node order in the same order as it comes from Jumpchart (drupal sets nodes in the menu in alphabetical order by default).

The benefits are easy to understand - when the client changes their mind yet again, we can run the export via WordPress to Drupal and not have to worry about creating nodes again and move everything around manually.

It&#039;s not much good if it happens again just before launch - but during the sitemap / design / development phase for sites up to about 150 main page nodes, we think it&#039;s going to be okay.

If anyone is interested in us contributing the update modules back to the Drupal community, do let me know via:

   dan at inigo dot net

or a direct message on Twitter to:

   @danfrydman

I suspect that something very similar can be done with Joomla, Typo3, etc.

Cheers guys - you made this stage of the job a lot easier :)]]></description>
		<content:encoded><![CDATA[<p>Yes, it is very cool!</p>
<p>We&#8217;re actively using Jumpchart to build sitemaps then export to WordPress.</p>
<p>With just a few tweaks to Drupal we&#8217;ve been able to do the following:</p>
<p>1. Preserve the path that&#8217;s automatically generated in WordPress after the <span class="caps">XML</span> import it done.</p>
<p>2. Keep the node order in the same order as it comes from Jumpchart (drupal sets nodes in the menu in alphabetical order by default).</p>
<p>The benefits are easy to understand &#8211; when the client changes their mind yet again, we can run the export via WordPress to Drupal and not have to worry about creating nodes again and move everything around manually.</p>
<p>It&#8217;s not much good if it happens again just before launch &#8211; but during the sitemap / design / development phase for sites up to about 150 main page nodes, we think it&#8217;s going to be okay.</p>
<p>If anyone is interested in us contributing the update modules back to the Drupal community, do let me know via:</p>
<p>   dan at inigo dot net</p>
<p>or a direct message on Twitter to:</p>
<p>   @danfrydman</p>
<p>I suspect that something very similar can be done with Joomla, Typo3, etc.</p>
<p>Cheers guys &#8211; you made this stage of the job a lot easier <img src="http://gluue.com/wp-includes/images/smilies/icon_smile.gif" alt=":)" class="wp-smiley" /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 165/168 objects using disk

 Served from: gluue.com @ 2026-04-22 03:45:40 by W3 Total Cache -->