<?xml version="1.0"?><rss version="2.0">
<channel>
<title>BitsyBox the Blog</title>
<link>http://bitsybox.com/blog/</link>
<description>think outside the box... bitsybox</description>
<language>en-us</language>

 
 

		 <item>
		   <title>Rebirth of the Dashboard</title>
		   <link>http://www.bitsybox.com/blog/rebirth-of-the-dashboard</link>
		   <guid>http://www.bitsybox.com/blog/rebirth-of-the-dashboard</guid>		   
		   <description><![CDATA[<p>For several months now, many of you have been using our Dashboard tool to create and maintain content for your websites. We've been humbled by the overwelming positive response and while we've been relatively quiet these past few weeks, we're proud to announce that today we've launched our new <a href="http://dashboard.bitsybox.com"><strong>Dashboard</strong></a> into production.</p><p>The new system represents a complete re-working of our Dashboard codebase, which will enable us to develop features faster and easier from now on. We've added several new interface enhancements, which I'll outline in this post.]]></description>
		   <pubDate>Thu, 08 Oct 2009 08:45:00 +0000</pubDate>
		 </item>		
		
		 <item>
		   <title>New Screencast, Docs, PHP Client Update</title>
		   <link>http://www.bitsybox.com/blog/new-screencast-and-more</link>
		   <guid>http://www.bitsybox.com/blog/new-screencast-and-more</guid>		   
		   <description><![CDATA[<p>Since we launched the beta program two weeks ago and opened up BitsyBox to a few hundred of you, we've gotten <a href="http://groups.google.com/group/bitsybox-developers" target="_blank">great feedback</a> from an eager group of interested developers. Most of the questions so far have surrounded the integration process. In response to that, we've done a few important things.]]></description>
		   <pubDate>Sun, 30 Aug 2009 12:00:00 +0000</pubDate>
		 </item>		
		
		 <item>
		   <title>Now Open For Beta</title>
		   <link>http://www.bitsybox.com/blog/beta-program-new-servers</link>
		   <guid>http://www.bitsybox.com/blog/beta-program-new-servers</guid>		   
		   <description><![CDATA[<p>We're now allowing a few select people to beta test BitsyBox for free. If you're one of those people, welcome! Remember, if you need help, send us an email at <a href="mailto:info@bitsybox.com">info@bitsybox.com</a> or visit our <a href="http://www.bitsybox.com/support" target="_blank">Support Section</a> to read documentation, download client code, and more.</p>
<p>Also wanted to let everyone know that we recently completed a full infrastructure migration to an excellent new host, Linode. This means faster servers, more reliability, and more hardware.</p>
<p>Enjoy the speed!</p>]]></description>
		   <pubDate>Mon, 03 Aug 2009 21:34:00 +0000</pubDate>
		 </item>		
		
		 <item>
		   <title>Save Drafts, Publish Later</title>
		   <link>http://www.bitsybox.com/blog/save-drafts-publish-later</link>
		   <guid>http://www.bitsybox.com/blog/save-drafts-publish-later</guid>		   
		   <description><![CDATA[<p>We've added a number of new features tonight, including the ability to save your data as 'drafts' and publishing it later. This is an important feature because it allows you to actively work on content changes over a long period of time and save them in a queue. When you're ready to make the changes live, come back, click Publish and they're live. ]]></description>
		   <pubDate>Mon, 20 Jul 2009 21:34:00 +0000</pubDate>
		 </item>		
		
		 <item>
		   <title>New Feature: Revision Tracking</title>
		   <link>http://www.bitsybox.com/blog/revision-tracking</link>
		   <guid>http://www.bitsybox.com/blog/revision-tracking</guid>		   
		   <description><![CDATA[<p>Today we're launching a powerful new feature that will help you track changes made to any part of your content. <strong>Revision tracking </strong>comes in the form of a small right-side module that shows you a brief history of the last few edits to a module or list item. This means you'll know who changed what, and when they changed it. ]]></description>
		   <pubDate>Wed, 08 Jul 2009 08:19:00 +0000</pubDate>
		 </item>		
		 
</channel>
</rss>

