<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Design 1</title>
	<atom:link href="http://logbook.projecttrackr.com/ui/design-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://logbook.projecttrackr.com/ui/design-1/</link>
	<description>Building a better web based project management solution</description>
	<lastBuildDate>Mon, 01 Mar 2010 21:50:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Design 2 - Project Trackr Development Log</title>
		<link>http://logbook.projecttrackr.com/ui/design-1/comment-page-1/#comment-19</link>
		<dc:creator>Design 2 - Project Trackr Development Log</dc:creator>
		<pubDate>Thu, 30 Jul 2009 18:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=44#comment-19</guid>
		<description>[...] So here&#8217;s the next potential design for the application. This one is intentionally completely different from first one and has a much more contrasting colour scheme. It is also built using the 960 grid system CSS framework, so can easily be adopted to have the same structure as the variations shown in design 1. [...]</description>
		<content:encoded><![CDATA[<p>[...] So here&#8217;s the next potential design for the application. This one is intentionally completely different from first one and has a much more contrasting colour scheme. It is also built using the 960 grid system CSS framework, so can easily be adopted to have the same structure as the variations shown in design 1. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damian</title>
		<link>http://logbook.projecttrackr.com/ui/design-1/comment-page-1/#comment-16</link>
		<dc:creator>Damian</dc:creator>
		<pubDate>Sun, 19 Jul 2009 20:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=44#comment-16</guid>
		<description>Thanks for the feedback so far guys :)
It is almost certain that several designs will be used throughout the application based on the content. Although the layout may change, it would be inconsistent to go between designs such as the first and second, as it is just a UI change instead of a structural one. On the other hand, designs such as 2, 3 and 5 would work well together.
I’ll create some mocks of “real content” so you can get an idea of what the pages would really look like. 
Also, now that it’s been mentioned and I’ve been looking at the design for a while, it does seem a bit ‘flat’, so I’ve added some colour to it. The original can be found &lt;a href=&quot;http://www.projecttrackr.com/design/1/a/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; and the colour version is &lt;a href=&quot;http://www.projecttrackr.com/design/1/f/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback so far guys <img src='http://logbook.projecttrackr.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
It is almost certain that several designs will be used throughout the application based on the content. Although the layout may change, it would be inconsistent to go between designs such as the first and second, as it is just a UI change instead of a structural one. On the other hand, designs such as 2, 3 and 5 would work well together.<br />
I’ll create some mocks of “real content” so you can get an idea of what the pages would really look like.<br />
Also, now that it’s been mentioned and I’ve been looking at the design for a while, it does seem a bit ‘flat’, so I’ve added some colour to it. The original can be found <a href="http://www.projecttrackr.com/design/1/a/" rel="nofollow">here</a> and the colour version is <a href="http://www.projecttrackr.com/design/1/f/" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Ferguson</title>
		<link>http://logbook.projecttrackr.com/ui/design-1/comment-page-1/#comment-15</link>
		<dc:creator>David Ferguson</dc:creator>
		<pubDate>Sun, 19 Jul 2009 17:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=44#comment-15</guid>
		<description>I agree with Dan, the design definatly feels &#039;flat&#039; and needs some colour to add some depth to it.
That being said, I would lean more toward 2,3, or 5, but thats just because of personal preference on the layout not for a specific reason. It would be much easier to pick the appropriate layout if there were some sort of idea of what would be in the individual containers. Depending on what is being displayed, it may not be feasible to have a third column.

Just my opinion..</description>
		<content:encoded><![CDATA[<p>I agree with Dan, the design definatly feels &#8216;flat&#8217; and needs some colour to add some depth to it.<br />
That being said, I would lean more toward 2,3, or 5, but thats just because of personal preference on the layout not for a specific reason. It would be much easier to pick the appropriate layout if there were some sort of idea of what would be in the individual containers. Depending on what is being displayed, it may not be feasible to have a third column.</p>
<p>Just my opinion..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://logbook.projecttrackr.com/ui/design-1/comment-page-1/#comment-14</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 19 Jul 2009 15:59:34 +0000</pubDate>
		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=44#comment-14</guid>
		<description>The actual design at the moment I feel is a bit &#039;flat&#039; although effectively clean and simplistic. Some Improvements I think might help;
larger fonts - make things clearly simple, easy to read &amp; navigate, the number of main nav elements scared me a little but I need to remember this is a tool
more header space - at the moment it feels very &quot;toolish&quot; and unfriendly, some nice graphics or prehaps Icons / more graphic content &amp; symbolism will help of course not to overdue n kill the page.</description>
		<content:encoded><![CDATA[<p>The actual design at the moment I feel is a bit &#8216;flat&#8217; although effectively clean and simplistic. Some Improvements I think might help;<br />
larger fonts &#8211; make things clearly simple, easy to read &amp; navigate, the number of main nav elements scared me a little but I need to remember this is a tool<br />
more header space &#8211; at the moment it feels very &#8220;toolish&#8221; and unfriendly, some nice graphics or prehaps Icons / more graphic content &amp; symbolism will help of course not to overdue n kill the page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://logbook.projecttrackr.com/ui/design-1/comment-page-1/#comment-13</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 19 Jul 2009 15:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=44#comment-13</guid>
		<description>Personal choice would be to go for:
 2 - I prefer the simplistic minimal content layout of this design, no clutter but still space for additional content 
 1 - I like this for use in context with the app as the site content focus i assume is the project managements service your promoting, BUT the left sub nav type bar is dead so this prehaps is a bad idea.
 4 - As robert says this is the cleanest feeling structure, central focus as good space be a safe bet imo.

Overall i think a variant design wouldbe better, I always think its a bit tough to decide the structure of each page til you know what content needs to sit on it and what focus you intend to give it. Prehaps the last, not too common.

All look good though and look forward to the variant designs.</description>
		<content:encoded><![CDATA[<p>Personal choice would be to go for:<br />
 2 &#8211; I prefer the simplistic minimal content layout of this design, no clutter but still space for additional content<br />
 1 &#8211; I like this for use in context with the app as the site content focus i assume is the project managements service your promoting, BUT the left sub nav type bar is dead so this prehaps is a bad idea.<br />
 4 &#8211; As robert says this is the cleanest feeling structure, central focus as good space be a safe bet imo.</p>
<p>Overall i think a variant design wouldbe better, I always think its a bit tough to decide the structure of each page til you know what content needs to sit on it and what focus you intend to give it. Prehaps the last, not too common.</p>
<p>All look good though and look forward to the variant designs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Stein</title>
		<link>http://logbook.projecttrackr.com/ui/design-1/comment-page-1/#comment-12</link>
		<dc:creator>Robert Stein</dc:creator>
		<pubDate>Sun, 19 Jul 2009 13:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=44#comment-12</guid>
		<description>The 4th one down (with 2 sidebars either side) I believe looks the neatest. These sidebars create a sort of &quot;frame&quot; around the main content focusing attention upon it. Rather than having a fuller field of text, the main content is kept with the confines of the centre, hence making it more asthetically pleasing to the reader.

Also, the 2 side bars can have multiple uses, thus increasing the potential uses for them.</description>
		<content:encoded><![CDATA[<p>The 4th one down (with 2 sidebars either side) I believe looks the neatest. These sidebars create a sort of &#8220;frame&#8221; around the main content focusing attention upon it. Rather than having a fuller field of text, the main content is kept with the confines of the centre, hence making it more asthetically pleasing to the reader.</p>
<p>Also, the 2 side bars can have multiple uses, thus increasing the potential uses for them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
