<?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: Appreciation of the material we work with</title>
	<atom:link href="http://www.nickpan.com/2009/12/23/appreciation-of-the-material-we-work-with/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nickpan.com/2009/12/23/appreciation-of-the-material-we-work-with/</link>
	<description>Family guy, Blogger, Web Producer in Singapore.</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:45:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mingfang</title>
		<link>http://www.nickpan.com/2009/12/23/appreciation-of-the-material-we-work-with/comment-page-1/#comment-43663</link>
		<dc:creator>Mingfang</dc:creator>
		<pubDate>Wed, 30 Dec 2009 17:00:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.nickpan.com/?p=2369#comment-43663</guid>
		<description>I find that a passionate web developer will be able to appreciate and understand how all the pieces fit together, because it is what we do - we understand how things work and then we try to put all the snazzy bits together. On the other hand, designers focus more on the look and feel, and more often than not, fail to understand how their design can fit with the grid of a CMS. In an ideal world, my designer will be able to give me a design that exploits the CMS&#039;s theme to it&#039;s fullest potential. But we don&#039;t live in an ideal world, so we have problems when Account Managers end up showing mock-ups that can&#039;t be integrated with the selected CMS.</description>
		<content:encoded><![CDATA[<p>I find that a passionate web developer will be able to appreciate and understand how all the pieces fit together, because it is what we do &#8211; we understand how things work and then we try to put all the snazzy bits together. On the other hand, designers focus more on the look and feel, and more often than not, fail to understand how their design can fit with the grid of a CMS. In an ideal world, my designer will be able to give me a design that exploits the CMS&#8217;s theme to it&#8217;s fullest potential. But we don&#8217;t live in an ideal world, so we have problems when Account Managers end up showing mock-ups that can&#8217;t be integrated with the selected CMS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://www.nickpan.com/2009/12/23/appreciation-of-the-material-we-work-with/comment-page-1/#comment-43661</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Tue, 29 Dec 2009 11:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.nickpan.com/?p=2369#comment-43661</guid>
		<description>This would be an excellent post, had it not been observed by a non-designed-trained web developer who probably only worked with the code, JS, CSS, the ideal designer should also have produced.

Other than appreciation of the material, we should also appreciate the efforts of those who work tirelessly with &quot;could-be-better&quot; deliverables. In print, the publication is the end product. On digital, layouts is only the beginning. There&#039;s still a team behind the codes handling the layouts.</description>
		<content:encoded><![CDATA[<p>This would be an excellent post, had it not been observed by a non-designed-trained web developer who probably only worked with the code, JS, CSS, the ideal designer should also have produced.</p>
<p>Other than appreciation of the material, we should also appreciate the efforts of those who work tirelessly with &#8220;could-be-better&#8221; deliverables. In print, the publication is the end product. On digital, layouts is only the beginning. There&#8217;s still a team behind the codes handling the layouts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils Hendriks</title>
		<link>http://www.nickpan.com/2009/12/23/appreciation-of-the-material-we-work-with/comment-page-1/#comment-43660</link>
		<dc:creator>Nils Hendriks</dc:creator>
		<pubDate>Tue, 29 Dec 2009 07:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.nickpan.com/?p=2369#comment-43660</guid>
		<description>I fully agree with the above. In fact it basically touches the same issue Jeffrey Zeldman described in &#039;Style versus design’ on http://www.adobe.com/designcenter/dialogbox/stylevsdesign/ and something I tweeted about. 

In my humble opinion most or at least a lot of web designers today are excellent with their tools - as long as it’s Photoshop or Fireworks. They barely have any knowledge of the medium they design for both technically and layout-wise. Compare this to the more traditional print designer who usually has a vast knowledge of paper, colour, layout, typography etc.

In view of designing web content it wouldn’t hurt to know a bit about layout, DTP, just the basic structures of laying out content like one would for say a report, a book etc with different levels of headings, paragraphs, unordered and ordered lists etc etc.</description>
		<content:encoded><![CDATA[<p>I fully agree with the above. In fact it basically touches the same issue Jeffrey Zeldman described in &#8216;Style versus design’ on <a href="http://www.adobe.com/designcenter/dialogbox/stylevsdesign/" rel="nofollow">http://www.adobe.com/designcenter/dialogbox/stylevsdesign/</a> and something I tweeted about. </p>
<p>In my humble opinion most or at least a lot of web designers today are excellent with their tools &#8211; as long as it’s Photoshop or Fireworks. They barely have any knowledge of the medium they design for both technically and layout-wise. Compare this to the more traditional print designer who usually has a vast knowledge of paper, colour, layout, typography etc.</p>
<p>In view of designing web content it wouldn’t hurt to know a bit about layout, DTP, just the basic structures of laying out content like one would for say a report, a book etc with different levels of headings, paragraphs, unordered and ordered lists etc etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

