<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gluue &#187; WordPress</title>
	<atom:link href="http://gluue.com/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://gluue.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 21 Dec 2016 14:23:49 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.8.41</generator>
	<item>
		<title>Importing a WordPress XML File Into Your Custom CMS.</title>
		<link>http://gluue.com/2009/08/importing-a-wordpress-xml-file-into-your-custom-cms/</link>
		<comments>http://gluue.com/2009/08/importing-a-wordpress-xml-file-into-your-custom-cms/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 17:09:14 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Jumpchart]]></category>
		<category><![CDATA[Paste]]></category>
		<category><![CDATA[Import]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://pasteinteractive.com/blog/?p=640</guid>
		<description><![CDATA[Our mission: to make yet another bridge between website planning and website running. A couple of months back we launched a new export format in Jumpchart that allows our users to swoop their project straight into the WordPress CMS. We think it works great, and we got a lot of amazing feedback from our users. [&#8230;]]]></description>
				<content:encoded><![CDATA[	<p>Our mission: to make yet another bridge between website planning and website running. A couple of months back we launched a new export format in Jumpchart that allows our users to swoop their project straight into the WordPress <span class="caps">CMS</span>.  We think it works great, and we got a lot of amazing feedback from our users.</p>

	<p>While WordPress is a widely used <span class="caps">CMS</span>, unfortunately we don&#8217;t use it for most of our own web projects. We have a totally custom built system that we&#8217;ve been constantly tweaking and evolving for three years to fit our exact needs &#8212; internally, we call it Haydn (after <a href="http://en.wikipedia.org/wiki/Joseph_Haydn">Joseph</a>).</p>

	<p>So how were we going to make link between Haydn and Jumpchart? <span id="more-640"></span></p>

	<p>The first thought was to make a private &#8216;Export to Haydn&#8217; function inside Jumpchart. It sounded logical and simple enough, but there was something even simpler. When we stopped to think about the opportunities the WordPress export format gives us, it was clear where we should head. Put simply, a WordPress export is a regular <span class="caps">XML</span> file with all the flexibility of <span class="caps">XML</span>. It&#8217;s universally simple, and it can be read and parsed by virtually any programming language.</p>

	<p>We write <span class="caps">PHP</span> here at Paste, and we took advantage of the built-in <a href="http://us2.php.net/manual/en/class.domdocument.php">DOMDocument class,</a> which makes coding look a lot like the old-school Javascript (remember <a href="https://developer.mozilla.org/en/DOM/element.getElementsByTagName">element.getElementsByTagName</a>?). Besides being easy, the nostalgia of it all was pretty fun.</p>

	<p><code><br />
<?php</p>

	<p>	$Document = new DOMDocument();
	$Document->load(&#8216;wordpress-export.xml&#8217;);</p>

	<p>	$pages = $Document->getElementsByTagName(&#8216;item&#8217;);
	foreach($pages as $page)
	{
		/* Convert Jumpchart/WordPress data as required by the <span class="caps">CMS</span> data structure */
	}</p>

	<p>?><br />
</code></p>

	<p>We wanted an import function that was specifically tailored to our needs. Figuring out what would work and what wouldn&#8217;t was the most difficult part. Once we nailed that thought process down, the rest sort of fell into place.  And we can&#8217;t wait to see how it&#8217;s going to affect the efficiency of our workflow from here on out. Something we thought would be difficult and time consuming turned out to be easier than planned, and will hopefully prove more useful than we ever imagined.</p>

	<p>After a couple of hours and a little more than 100 lines of code, we have our new Jumpchart importer inside our custom <span class="caps">CMS</span>. Cool, fast and fun. If you&#8217;re like us, and have a custom <span class="caps">CMS</span>,  give writing your own importer a try. It&#8217;s easier than you think.</p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2009/08/importing-a-wordpress-xml-file-into-your-custom-cms/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Exporting your Jumpchart to WordPress</title>
		<link>http://gluue.com/2009/04/exporting-your-jumpchart-to-wordpress/</link>
		<comments>http://gluue.com/2009/04/exporting-your-jumpchart-to-wordpress/#comments</comments>
		<pubDate>Tue, 28 Apr 2009 17:10:29 +0000</pubDate>
		<dc:creator><![CDATA[Paste Interactive]]></dc:creator>
				<category><![CDATA[Jumpchart]]></category>
		<category><![CDATA[Paste]]></category>
		<category><![CDATA[Export]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://pasteinteractive.com/?p=464</guid>
		<description><![CDATA[Now that the new Jumpchart has been released into the wild we thought we&#8217;d write a few posts focusing on some of the most important new features that have come to Jumpchart. In this first post we&#8217;ll be looking at the new Export to WordPress option, what it means for your workflow, and why it&#8217;s [&#8230;]]]></description>
				<content:encoded><![CDATA[	<p>Now that the new Jumpchart has been released into the wild we thought we&#8217;d write a few posts focusing on some of the most important new features that have come to Jumpchart. In this first post we&#8217;ll be looking at the new Export to WordPress option, what it means for your workflow, and why it&#8217;s the most important new addition to Jumpchart.<span id="more-464"></span></p>

	<p>First, a bit of context. The guys and gals over at <a href="http://wordpress.org">WordPress</a> have created a specific file format for data that is exported out of (and into) a WordPress installation. This format is called .wxr, but at its heart it&#8217;s really just an <span class="caps">XML</span> file with a few WordPress specific tags. When you select &#8220;Export to WordPress&#8221; in Jumpchart you will be prompted to download a folder. The contents of this folder are pretty spare; just a simple theme, a special Jumpchart install file to speed you through the process and an <span class="caps">XML</span> file. The <span class="caps">XML</span> file is the most important part of your export, it&#8217;s the WordPress .wxr file, and it contains all the content for all the pages you have created. We won&#8217;t go into the specific process of moving your content into a fresh WordPress install (you can see that info here) but, suffice to say, WordPress has done an incredible job of streamlining the process for importing these <span class="caps">XML</span> based files.</p>

	<p>As a result of this ease-of-use and of the popularity of WordPress, this simple format has been adopted by many of the most popular and widely used content management systems out there, including <a href="http://www.typepad.com/">Typepad</a>, <a href="http://expressionengine.com/">Expression Engine</a>, <a href="http://drupal.org/">Drupal</a> and <a href="http://www.joomla.org/">Joomla</a>. Which means the folder you download when you export your Jumpchart is actually a highly portable method for taking your site&#8217;s content from organization and planning in Jumpchart straight through into the build phase using your favorite <span class="caps">CMS</span>.</p>

	<p>So how, exactly, does this impact your workflow? As the name indicates, we&#8217;ve optimized this process for WordPress, so let&#8217;s talk about the sweet stuff that you get when you export your Jumpchart using the WordPress export option. As we mentioned already, the folder you download contains the <span class="caps">XML</span> file with all your content and a few other things. One of those things is our clean, simple and (mostly) design agnostic WordPress theme, so no more looking at that big blue header when you&#8217;re starting up. The other file in the folder is one called jumpchart-wordpress-install.php. This file is a simple script that we&#8217;ve written to take care of some pre-configuration of your site. The impact on your workflow is that you can now take a finished Jumpchart to a content laden WordPress installation in just a few minutes. Which leaves only the customization of the theme files before you&#8217;re ready for delivery. No more retracing your steps to make sure you haven&#8217;t missed any content!</p>

	<p><a href="http://www.jumpchart.com/tour/wordpress/">Learn more about WordPress Export and check out working examples.</a></p>

	<p><a href="http://core.jumpchart.com/help/article/28/">Check out our detailed support article on Exporting for WordPress</a></p>

	<p>Jumpchart is all about content organization and planning, but we realize that Jumpchart is only a stepping stone in the process of building a fully functioning and deliverable website. The harder it is to get your organized content into your platform of choice quickly and easily, the less likely you are to use Jumpchart in the first place. The Export to WordPress option has significantly lowered the amount of time and effort it takes to get your content out there on the web, where it belongs.</p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2009/04/exporting-your-jumpchart-to-wordpress/feed/</wfw:commentRss>
		<slash:comments>1734</slash:comments>
		</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 226/236 objects using disk

 Served from: gluue.com @ 2026-06-09 00:53:45 by W3 Total Cache -->