<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by joe gannon</title>
    <link>http://www.boxesandarrows.com/person/1257</link>
    <pubDate>Sun, 30 Sep 2007 00:27:13 GMT</pubDate>
    <description>Comments by joe gannon</description>
    <item>
      <description>&lt;p&gt;It really depends on the project. If the site is going to be created using a dynamic &lt;span class="caps"&gt;CMS&lt;/span&gt;, then its more difficult to make &lt;span class="caps"&gt;HTML&lt;/span&gt; mockups. The site&amp;#8217;s pages were dependant on user types and specific content elements based on roles. The developers needed to understand the presentation, but the templates were done in &lt;span class="caps"&gt;HTML&lt;/span&gt;.&lt;/p&gt;

	&lt;p&gt;Unfortunatly what&amp;#8217;s good for a developer isnt apparently good enough for fellow IAs. I still get wierd looks when I show my documents drawn in Visio. Sadly some dont get the real reason why we need to create documentation. Its based on the project needs&amp;#8212;not some pie-in-the-sky ideal document.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/real_wireframes#content_12716</link>
      <guid>http://www.boxesandarrows.com/view/real_wireframes#content_12716</guid>
      <pubDate>Sun, 30 Sep 2007 00:27:13 GMT</pubDate>
      <author>joe gannon</author>
    </item>
  </channel>
</rss>
