<?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>The Royal Blog &#187; Technology</title>
	<atom:link href="http://blog.theroyalorder.com/archives/category/technology/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.theroyalorder.com</link>
	<description>The Royal Order of Experience Design&#039;s weblog.</description>
	<lastBuildDate>Fri, 20 Nov 2009 16:47:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>TRO on Facebook</title>
		<link>http://blog.theroyalorder.com/archives/222</link>
		<comments>http://blog.theroyalorder.com/archives/222#comments</comments>
		<pubDate>Tue, 06 Oct 2009 18:38:59 +0000</pubDate>
		<dc:creator>Joe Clay</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Exploits]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[The Daily]]></category>

		<guid isPermaLink="false">http://blog.theroyalorder.com/?p=222</guid>
		<description><![CDATA[Login to your Facebook profile and search Pages for &#8220;The Royal Order of Experience Design.&#8221; Here you&#8217;ll be able to chat with everyone at TRO, share findings, and poke us.
]]></description>
			<content:encoded><![CDATA[<p><strong>Login</strong> to your Facebook profile and <strong>search Pages</strong> for &#8220;The Royal Order of Experience Design.&#8221; Here you&#8217;ll be able to chat with everyone at TRO, share findings, and poke us.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.theroyalorder.com/archives/222/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TRO on Twitter</title>
		<link>http://blog.theroyalorder.com/archives/220</link>
		<comments>http://blog.theroyalorder.com/archives/220#comments</comments>
		<pubDate>Tue, 06 Oct 2009 18:35:12 +0000</pubDate>
		<dc:creator>Joe Clay</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Exploits]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[The Daily]]></category>

		<guid isPermaLink="false">http://blog.theroyalorder.com/?p=220</guid>
		<description><![CDATA[http://twitter.com/theroyalorder
The Royal Order has officially joined the thousands of people addicted to Twitter. So follow our page, and in less than 140 characters you&#8217;ll learn about the latest RO news.
]]></description>
			<content:encoded><![CDATA[<p>http://twitter.com/theroyalorder</p>
<p>The Royal Order has officially joined the thousands of people addicted to Twitter. So follow our page, and in less than 140 characters you&#8217;ll learn about the latest RO news.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.theroyalorder.com/archives/220/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Client Side CMS</title>
		<link>http://blog.theroyalorder.com/archives/180</link>
		<comments>http://blog.theroyalorder.com/archives/180#comments</comments>
		<pubDate>Fri, 28 Aug 2009 20:43:56 +0000</pubDate>
		<dc:creator>Garrett</dc:creator>
				<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blog.theroyalorder.com/?p=180</guid>
		<description><![CDATA[The technology is clearly ahead of its time. But a new client side CMS named <a href="http://www.firerift.com">firerift</a> has my attention.

<img src="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire1-465x352.jpg" alt="fire1" title="fire1" width="465" height="352" class="alignnone size-medium wp-image-181" />

At first glance, Fire Rift is impressive. The CMS has set out to make life easier for developers by only managing your content via the CMS. No more hacking of your html and css to fit the limitations of your CMS's templating system (often archaic and completely different across various other CMS's.) With Fire Rift, you cut and code your psd and let Fire Rift take care of the content via css class names or javascript. 

Photos of the interface after the break]]></description>
			<content:encoded><![CDATA[<p>The technology is clearly ahead of its time. But a new client side CMS named <a href="http://www.firerift.com">firerift</a> has my attention.</p>
<p><a href="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire1.jpg"><img src="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire1-465x352.jpg" alt="fire1" title="fire1" width="465" height="352" class="alignnone size-medium wp-image-181" /></a></p>
<p>At first glance, Fire Rift is impressive. The CMS has set out to make life easier for developers by only managing your content via the CMS. No more hacking of your html and css to fit the limitations of your CMS&#8217;s templating system (often archaic and completely different across various other CMS&#8217;s.) With Fire Rift, you cut and code your psd and let Fire Rift take care of the content via css class names or javascript. </p>
<p>Meet the interface:</p>
<p><a href="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire2.jpg"><img src="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire2-465x537.jpg" alt="fire2" title="fire2" width="465" height="537" class="alignnone size-medium wp-image-182" /></a></p>
<p><a href="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire3.jpg"><img src="http://blog.theroyalorder.com/wp-content/uploads/2009/08/fire3-465x365.jpg" alt="fire3" title="fire3" width="465" height="365" class="alignnone size-medium wp-image-183" /></a></p>
<p>Creating content looks dead simple thanks to a back end that is hands down the cleanest I&#8217;ve seen from any other cms editor. See the <a href="http://www.firerift.com">overview video</a> for more info.</p>
<p>Ahead of it&#8217;s time:</p>
<p>With every new CMS there are issues that may get in the way of fulfilling your project requirements. The biggest debate centered around Fire Rift is the questionable handling of content for SEO. The problem is that Fire Rift is a javascript based CMS. That means the actual content on the page relies on javascript to be displayed. Try a view source of this Fire Rift powered <a href="http://photography.drewwilson.com/" target="_black">example page</a> to see what I mean. Google&#8217;s search engine reportedly only has the ability to index content via an onClick event. Meaning google only sees your html framework sans the content from the CMS. This fact alone is the EPIC FAIL flaw of Fire Rift. It  may just work against you when competing for top results against other server side CMS systems serving up similar content in the page.</p>
<p>In my opinion this is a great step forward for dynamic content. As many browsers focus on boosting javascript performance and treating the web as an app thus blurring the lines between desktop and cloud computing. But this CMS is not ready for primetime. Unless google finds a new way to index content via javascript (completely possible but not in the near future) or you go ahead and also serve up static content html pages (rendering the idea of a cms useless), I would consider it a beta idea that would be fun for designers/web developers to experiment with or use on sites that truly do not need to be spidered every day for content. </p>
<p>Garrett</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.theroyalorder.com/archives/180/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing Destination Kohler</title>
		<link>http://blog.theroyalorder.com/archives/103</link>
		<comments>http://blog.theroyalorder.com/archives/103#comments</comments>
		<pubDate>Fri, 07 Aug 2009 21:41:52 +0000</pubDate>
		<dc:creator>hogan</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blog.theroyalorder.com/?p=103</guid>
		<description><![CDATA[With marketing budgets tightening and full-scale site redesigns becoming somewhat less frequent, we are seeing a growing number of clients that wish to make changes opting for optimization. Whether the site was originally developed by The Royal Order or not, we are being tasked with modifying the experience based on changing business requirements, user feedback or performance metrics. Such was the case with Destination Kohler.

User feedback collected from online site surveys indicated several flaws in the home page architecture of both Destination Kohler (Wisconsin and St Andrews) sites that made it difficult to access specific content. Featured content tiles were not self-evident and in many cases redundant with global navigation. Secondary and footer navigation needed to be reorganized, and the page needed to be optimized for search engines and tagged with Omniture code.]]></description>
			<content:encoded><![CDATA[<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;">With marketing budgets tightening and full-scale site redesigns becoming somewhat less frequent, we are seeing a growing number of clients that wish to make changes opting for optimization. Whether the site was originally developed by The Royal Order or not, we are being tasked with modifying the experience based on changing business requirements, user feedback or performance metrics. Such was the case with <a href="http://www.destinationkohler.com" target="_blank">Destination Kohler</a>.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;">User feedback collected from online site surveys indicated several flaws in the home page architecture of both Destination Kohler (Wisconsin and St Andrews) sites that made it difficult to access specific content. Featured content tiles were not self-evident and in many cases redundant with global navigation. Secondary and footer navigation needed to be reorganized, and the page needed to be optimized for search engines and tagged with Omniture code. Additionally, the business wished to do a better job telling the brand story and promoting specific content such as packages, book online, e-commerce and special events.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial;">Our biggest challenge was in making strategic architectural and interface modifications without redesigning the entire site — since aside from the landing pages, site content was to remain unchanged. A primary goal was allowing users to book online at any time during their site visit. Since the interface was only 800 pixels wide, it was determined in IA that if we added a column to the right, we could stay within the standard 1024 display dimension, while housing a variety of &#8217;support&#8217; tools — including the persistent booking widget, 800 number and click to chat. In the interest of keeping this column efficient and the content apparent but digestible, we chose to employ javascript and reveal them one at a time interactively. This column is carried throughout the site, and was a relatively simple update for the technical team to deploy.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial;">From a branding standpoint, DK wished to update the look and feel to make it more vibrant and contemporary. Garamond was the dominant typeface, and in addition to being difficult to read in navigational menus, it&#8217;s application said &#8216;conservative&#8217;. Avenir was selected as a clean sans serif alternative, with a wide variety of weights and legibility at small sizes. The color palette for both sites have also been tweaked and extended to reflect the two similar but different brand experiences. In redesigning the landing pages, the breadth of service offerings has been given center stage, sequencing through a variety of beautiful location photography within an embedded Flash movie. Simplifying the promotional spiffs and focusing navigational organization makes finding content easy, and browsing content rewarding.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial;">Sometimes relatively small modifications to an existing site can make a big difference.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial;">
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial;">-TH</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.theroyalorder.com/archives/103/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
