<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>@Lathi.net: New Radiant Website</title>
    <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>On Life, Fatherhood, Christianity, and Computers</description>
    <item>
      <title>New Radiant Website</title>
      <description>&lt;p&gt;&lt;a href="http://corporatetool.blogspot.com/"&gt;&lt;em&gt;blah blah blah (lawyers made me change this)&lt;/em&gt;&lt;/a&gt; has been going through a major re-branding effort for the last long time.  This morning we&amp;#8217;re launching a major re-write of our main application.  There&amp;#8217;s a pretty cool &lt;a href="http://corporatetool.blogspot.com//personal/form/flash-demo-form"&gt;on-line demo&lt;/a&gt; that shows off our new sexiness.&lt;/p&gt;


	&lt;p&gt;Simultaneously we&amp;#8217;re rebranding our website and also restructuring most of our internal item catalog.  Pretty much everyone in the company has been involved in this effort in some way.  After months of work, we&amp;#8217;re live!&lt;/p&gt;


	&lt;p&gt;The new website is running Radiant from index to thank you page.  We have a web service for handling all of the EC business logic and multiple user facing web sites that connect to the service for managing their cart.  We&amp;#8217;ve written a &amp;#8220;store behavior&amp;#8221; to handle this xml-rpc client interface with Radiant.&lt;/p&gt;


	&lt;p&gt;This actually isn&amp;#8217;t our first production Radiant site.  Our first was our &lt;a href="http://www.rosettaworld.co.jp/"&gt;Japanese RosettaWorld&lt;/a&gt;.  That site isn&amp;#8217;t getting near the traffic that our US site does though.  The US site runs steady-state at about 5 user sessions per second.  We had a bit of a problem serving our &lt;span class="caps"&gt;CSS&lt;/span&gt; and JavaScript out of Radiant.  It was causing a session hit that forced an update to the DB.  Turns out that was a pretty big bottleneck in our load testing.  As a fix, we just moved those files out of Radiant for this rollout.  I&amp;#8217;m sure there&amp;#8217;s some in-Radiant solution to tell it not to track sessions on those pages.  We&amp;#8217;ll figure that out for this next release.&lt;/p&gt;


	&lt;p&gt;Hopefully, after all the stress of getting this release done we can take a collective deep breath.  However, I&amp;#8217;m guessing it&amp;#8217;s more likely we&amp;#8217;ll be scrambling to make all kinds of tweaks and such.&lt;/p&gt;</description>
      <pubDate>Tue, 28 Aug 2007 04:38:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:080b0b99-8ca7-4c7b-9c32-a01317383ec8</guid>
      <author>Doug</author>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website</link>
      <category>Ruby on Rails</category>
      <category>rosettastone</category>
      <category>radiant</category>
    </item>
    <item>
      <title>"New Radiant Website" by Barry</title>
      <description>&lt;p&gt;Demo really looks not bad :)
Who knows maybe you&amp;#8217;ll make a lot of money on this&amp;#8230;&lt;/p&gt;</description>
      <pubDate>Fri, 14 Sep 2007 12:34:18 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:512ed82f-e8da-4c34-a4ca-41efceed40b5</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-385</link>
    </item>
    <item>
      <title>"New Radiant Website" by Kim</title>
      <description>&lt;p&gt;Man you don&amp;#8217;t even know how long I&amp;#8217;ve waited for this since disabling my own Movable Type widget (that doesn&amp;#8217;t work since Haloscan bypasses that code).&lt;/p&gt;


	&lt;p&gt;THANK YOU!&lt;/p&gt;</description>
      <pubDate>Tue, 11 Sep 2007 11:25:14 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:b3647cc6-6f53-411d-8160-15d0a6b06f46</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-384</link>
    </item>
    <item>
      <title>"New Radiant Website" by Doug Alcorn</title>
      <description>&lt;p&gt;The major portions of our extensions are to talk to in-house services.  Those pieces don&amp;#8217;t make sense to release because no one would be able to take advantage of them.&lt;/p&gt;


	&lt;p&gt;That said, there are a couple things we&amp;#8217;re doing with workflow routing and feedback tracking that may make sense to release.  We&amp;#8217;re still in the throws of our major release this week.  We also have three more Radiant sites to release in the next 6 weeks (re-brand our JP site, release our UK and DE sites as Radiant).  Once we&amp;#8217;re done with the pressure of those releases we can bring up releasing some of this.&lt;/p&gt;</description>
      <pubDate>Wed, 29 Aug 2007 13:46:07 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:b8925705-533e-4f5f-9bd5-3b82b970fa71</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-383</link>
    </item>
    <item>
      <title>"New Radiant Website" by Damien McKenna</title>
      <description>&lt;p&gt;Are you going to be releasing any of your work as extensions?&lt;/p&gt;</description>
      <pubDate>Wed, 29 Aug 2007 10:28:59 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:23bf1a9f-13d9-4048-a00d-5fc9c4e5af17</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-382</link>
    </item>
    <item>
      <title>"New Radiant Website" by Doug Alcorn</title>
      <description>&lt;p&gt;We had actually built several CMS-like websites prior to settling on Radiant.  The one just prior (which is located at &lt;a href="http://rosettastone.de" rel="nofollow"&gt;http://rosettastone.de&lt;/a&gt; complete with our old site design) was internally very similar to Radiant.  What Radiant provided us was sound internals with a nice content editing interface and a framework for easily extending it.  Radiant is clearly a light-weight CMS, it says so right on the box.  But it gave us a solid framework to build on in a language we love.&lt;/p&gt;</description>
      <pubDate>Wed, 29 Aug 2007 08:01:01 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:2cd6ada3-8fa0-4e81-b2a7-61cd1da931d5</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-381</link>
    </item>
    <item>
      <title>"New Radiant Website" by bill Davenport</title>
      <description>&lt;p&gt;The site looks nice.  That&amp;#8217;s quite a lot of work.&lt;/p&gt;


	&lt;p&gt;What drew you to use Radiant as a base?&lt;/p&gt;</description>
      <pubDate>Tue, 28 Aug 2007 22:38:28 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:44c92bde-2eb7-420c-9690-619a307cd065</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-380</link>
    </item>
    <item>
      <title>"New Radiant Website" by Myers Carpenter</title>
      <description>&lt;p&gt;It should be noted that out of the box Radiant doesn&amp;#8217;t have sessions on for it&amp;#8217;s main content.  That was one of the first things I had to hack in.&lt;/p&gt;</description>
      <pubDate>Tue, 28 Aug 2007 13:44:48 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:2dd90949-9b56-4e33-b2cd-f8540f4fe983</guid>
      <link>http://blog.lathi.net/articles/2007/08/28/new-radiant-website#comment-379</link>
    </item>
  </channel>
</rss>
