<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 05:52:09 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Decal CMS Blog: Testing your website before launching: how to let content drive design (Part 1)]]></title>
      <guid>http://www.phpdeveloper.org/news/16841</guid>
      <link>http://www.phpdeveloper.org/news/16841</link>
      <description><![CDATA[<p>
New from the Decal blog today there's a <a href="http://www.decalcms.com/page/Testing_your_website_before_launching_how_to_let_content_drive_design">general post about testing</a>, not writing tests for your code but testing methods for your site as a whole (like A/B testing). This is the first part of a series.
</p>
<blockquote>
For a long time, we here at Working Software have been strong believers in the "content precedes design" philosophy, as famously espoused by <a href="http://www.zeldman.com/2008/05/06/content-precedes-design/">Jeffrey Zeldman</a> and summarised here on <a href="http://uxmyths.com/post/718187422/myth-you-dont-need-the-content-to-design-a-website">UX Myths</a>. [...] We are relaunching this website so we'd gone through the process of creating our "content first" wireframe using Decal Mockups.
</blockquote>
<p>
They go through their entire process - how they decided what to test on the site, the methods they chose for the testing (including <a href="http://pickfu.com/">PickFu</a> and <a href="http://feedbackarmy.com/">Feedback Army</a>) and some of the results of the feedback from each.
</p>]]></description>
      <pubDate>Fri, 09 Sep 2011 13:05:42 -0500</pubDate>
    </item>
  </channel>
</rss>
