<?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"
	>
<channel>
	<title>Comments on: 99% of Web Design Books are Not</title>
	<atom:link href="http://bokardo.com/archives/99-of-web-design-books-are-not/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/99-of-web-design-books-are-not/</link>
	<description>A Blog about Social Web Design</description>
	<pubDate>Fri, 04 Jul 2008 05:00:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Fine art paintings</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-156318</link>
		<dc:creator>Fine art paintings</dc:creator>
		<pubDate>Tue, 29 Apr 2008 09:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-156318</guid>
		<description>If this is the true essence of Web Design, how can we educate most web designers and/or graphics designers about this?  Indeed, things shouldn’t be accomplished in the technical ways most of the time.  You see, most web designers nowadays are required to be masters of CSS, HTML, and all.  In fact most web designing jobs require the expertise on these applications.  If true web design isn’t about these applications, why is it then that these are the primary requirement job-wise?</description>
		<content:encoded><![CDATA[<p>If this is the true essence of Web Design, how can we educate most web designers and/or graphics designers about this?  Indeed, things shouldn’t be accomplished in the technical ways most of the time.  You see, most web designers nowadays are required to be masters of CSS, HTML, and all.  In fact most web designing jobs require the expertise on these applications.  If true web design isn’t about these applications, why is it then that these are the primary requirement job-wise?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Cruse</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-155906</link>
		<dc:creator>Dale Cruse</dc:creator>
		<pubDate>Fri, 04 Apr 2008 16:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-155906</guid>
		<description>This isn't the first time I've heard an IA/usability type poo poo other web disciplines. I'm curious why that is.</description>
		<content:encoded><![CDATA[<p>This isn&#8217;t the first time I&#8217;ve heard an IA/usability type poo poo other web disciplines. I&#8217;m curious why that is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CHRIS</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-146623</link>
		<dc:creator>CHRIS</dc:creator>
		<pubDate>Sun, 16 Sep 2007 16:13:22 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-146623</guid>
		<description>There was one time when webdesign was easy ...
You did the creation in Photoshop or Illustrator and click export as html ....
Then in Dreamweaver you just had to center the whole design or best put in a table with an austostretching colum for some semi-liquid design ....
If you didn't need to be so graphic and weren't disturbed by a fixed design in a world of bigger and bigger screens, you could also design with layers directly in Dreamweaver ...
Then came the headache of the CSS layout (for the purely graphic oriented mind we mean) and all this hacks esoterica requiring books and more books to explain how to eventually get this middle-of-the-road look that most standard compliant sites share together ...
So what id needed is now that Adobe is owning both Photoshop and Dreamweaver, that they come again with a conversion tool that takes your design in Photoshop and convert it into the equivalent CSS box model, with a couple of radio buttons to check :
- Do you want a fixed layout with layers (only current option of Adobe CS2) or liquid or semi-liquid ?
- Do you want this column to stretch ?
- Do you want the content to adjust or to overlap in case the size of the text is increased by the browser  ?
- Should this background be printed too and if not what colour would you like to have for the text in the automatically generated CSS print style sheet ?
- and so on ...

Or as well in Dreamweaver make it as easy to generate the "float design" you want, as it was for tables with the deprecated "advanced layout mode", or as it is easy to get a fixed compliant layout with the absolute positionning of the "layers" (simply drawing squares on your screen, yes siree) ...

Then all those books won't be necessary anymore ...
Like, at one point Dave Siegel had to spend time explaining the use of the non-breaking space or the transparent gif etc ... which seemed at the time a total aberration for the designer coming from the print and was quite a headache to implement, until the first version of DW and Image Ready came and make this invisible for the designer ...  By the way did you notice, that even in its latest versions, Dreamweaver is still using those same spacer.gif and nbsp;  in the code it creates ..?? &#160;  :-)  &#160; I mean Dreamweaver, Adobe, the ones shaping the future of the web in many ways ...

    The "good" thing is that the law of computers is such that when one difficult thing becomes easy, two that were impossible to do become very difficult to perform ... 
    So, those book writers won't be on the dole either and the pure designers will be happy - for some times...

    So please Adobe make a move (maybe it is done already with CS3, but we didn't hear the news so far ...)</description>
		<content:encoded><![CDATA[<p>There was one time when webdesign was easy &#8230;<br />
You did the creation in Photoshop or Illustrator and click export as html &#8230;.<br />
Then in Dreamweaver you just had to center the whole design or best put in a table with an austostretching colum for some semi-liquid design &#8230;.<br />
If you didn&#8217;t need to be so graphic and weren&#8217;t disturbed by a fixed design in a world of bigger and bigger screens, you could also design with layers directly in Dreamweaver &#8230;<br />
Then came the headache of the CSS layout (for the purely graphic oriented mind we mean) and all this hacks esoterica requiring books and more books to explain how to eventually get this middle-of-the-road look that most standard compliant sites share together &#8230;<br />
So what id needed is now that Adobe is owning both Photoshop and Dreamweaver, that they come again with a conversion tool that takes your design in Photoshop and convert it into the equivalent CSS box model, with a couple of radio buttons to check :<br />
- Do you want a fixed layout with layers (only current option of Adobe CS2) or liquid or semi-liquid ?<br />
- Do you want this column to stretch ?<br />
- Do you want the content to adjust or to overlap in case the size of the text is increased by the browser  ?<br />
- Should this background be printed too and if not what colour would you like to have for the text in the automatically generated CSS print style sheet ?<br />
- and so on &#8230;</p>
<p>Or as well in Dreamweaver make it as easy to generate the &#8220;float design&#8221; you want, as it was for tables with the deprecated &#8220;advanced layout mode&#8221;, or as it is easy to get a fixed compliant layout with the absolute positionning of the &#8220;layers&#8221; (simply drawing squares on your screen, yes siree) &#8230;</p>
<p>Then all those books won&#8217;t be necessary anymore &#8230;<br />
Like, at one point Dave Siegel had to spend time explaining the use of the non-breaking space or the transparent gif etc &#8230; which seemed at the time a total aberration for the designer coming from the print and was quite a headache to implement, until the first version of DW and Image Ready came and make this invisible for the designer &#8230;  By the way did you notice, that even in its latest versions, Dreamweaver is still using those same spacer.gif and nbsp;  in the code it creates ..?? &nbsp;  <img src='http://bokardo.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  &nbsp; I mean Dreamweaver, Adobe, the ones shaping the future of the web in many ways &#8230;</p>
<p>    The &#8220;good&#8221; thing is that the law of computers is such that when one difficult thing becomes easy, two that were impossible to do become very difficult to perform &#8230;<br />
    So, those book writers won&#8217;t be on the dole either and the pure designers will be happy - for some times&#8230;</p>
<p>    So please Adobe make a move (maybe it is done already with CS3, but we didn&#8217;t hear the news so far &#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: toys</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-144199</link>
		<dc:creator>toys</dc:creator>
		<pubDate>Mon, 30 Jul 2007 22:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-144199</guid>
		<description>I know exactly what you mean. I have shown up for three jobs in the past to be a web designer and then been told that what I would be doing is coding the pages and the graphic designer would be designing the pages. Not that I can't write code, but when I see the words web designer, I think of the design not the coding...for that I look for "web coder" or something like that. Although I have to disagree about the books. Don't you find that your style and what you understand differs remarkably from some of the other people around you? I know that my style of learning just doesn't fit in with Eric Meyer and I need someone else to teach me with book smarts how to do things. Not that he isn't good. He's excellent, but I'm a different kind of learner. Where do you find books when you go to Barnes and Noble? I usually end up in the Graphic Design section and it makes me feel a little weird because I'm a web designer. Do you think it is even possible at this point to make the transition to having people understand the difference? Or are we simply stuck as we are? Lumped in with coders under one name?</description>
		<content:encoded><![CDATA[<p>I know exactly what you mean. I have shown up for three jobs in the past to be a web designer and then been told that what I would be doing is coding the pages and the graphic designer would be designing the pages. Not that I can&#8217;t write code, but when I see the words web designer, I think of the design not the coding&#8230;for that I look for &#8220;web coder&#8221; or something like that. Although I have to disagree about the books. Don&#8217;t you find that your style and what you understand differs remarkably from some of the other people around you? I know that my style of learning just doesn&#8217;t fit in with Eric Meyer and I need someone else to teach me with book smarts how to do things. Not that he isn&#8217;t good. He&#8217;s excellent, but I&#8217;m a different kind of learner. Where do you find books when you go to Barnes and Noble? I usually end up in the Graphic Design section and it makes me feel a little weird because I&#8217;m a web designer. Do you think it is even possible at this point to make the transition to having people understand the difference? Or are we simply stuck as we are? Lumped in with coders under one name?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Delta</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-106521</link>
		<dc:creator>Delta</dc:creator>
		<pubDate>Tue, 20 Mar 2007 00:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-106521</guid>
		<description>I've always considered "web design books" to be useless.  I use Frontpage, and my code may be bloated and awful looking, but it doesn't effect page function or SEO so I'll stick to what I know (tables galore).  Every time I go into Barnes and Nobles I look at their web design section, and most of what I see doesn't seem helpful.  If you use Frontpage as a WYSIWYG program, you don't really need to have an in depth knowledge of coding unless you're trying to pull something complicated off.  I remember studying books on Photoshop and Frontpage for months, and learning more in a few weeks of working at a firm than I had trying to educate myself with literature.  A book isn't going to teach you how to develop an aesthetically pleasing site, I think it boils down to working with others, learning what's effective, and then developing your own ideas from there.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always considered &#8220;web design books&#8221; to be useless.  I use Frontpage, and my code may be bloated and awful looking, but it doesn&#8217;t effect page function or SEO so I&#8217;ll stick to what I know (tables galore).  Every time I go into Barnes and Nobles I look at their web design section, and most of what I see doesn&#8217;t seem helpful.  If you use Frontpage as a WYSIWYG program, you don&#8217;t really need to have an in depth knowledge of coding unless you&#8217;re trying to pull something complicated off.  I remember studying books on Photoshop and Frontpage for months, and learning more in a few weeks of working at a firm than I had trying to educate myself with literature.  A book isn&#8217;t going to teach you how to develop an aesthetically pleasing site, I think it boils down to working with others, learning what&#8217;s effective, and then developing your own ideas from there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Onlineshop</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-102439</link>
		<dc:creator>Onlineshop</dc:creator>
		<pubDate>Sat, 10 Mar 2007 03:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-102439</guid>
		<description>I think these blog is really useful for new comers and Excellent resource list.</description>
		<content:encoded><![CDATA[<p>I think these blog is really useful for new comers and Excellent resource list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Delta</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-57207</link>
		<dc:creator>Delta</dc:creator>
		<pubDate>Sat, 23 Dec 2006 00:29:06 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-57207</guid>
		<description>I'm hardly a coding purist as I do everything in Frontpage's WYSIWYG formatting.  Anyone reading those books on design at B&#38;N won't have bloated code, and can score points for accessibility, but I haven't seen any sites not getting indexed despite sloppy coding.  My coding is the equivalent of using duct tape to hold a car together, but it serves its purpose.  In the end, a lot of clients aren't going to be concerned with everything those books teach.  If the site is attractive, if it loads relatively fast and still ranks well, then perfect.</description>
		<content:encoded><![CDATA[<p>I&#8217;m hardly a coding purist as I do everything in Frontpage&#8217;s WYSIWYG formatting.  Anyone reading those books on design at B&amp;N won&#8217;t have bloated code, and can score points for accessibility, but I haven&#8217;t seen any sites not getting indexed despite sloppy coding.  My coding is the equivalent of using duct tape to hold a car together, but it serves its purpose.  In the end, a lot of clients aren&#8217;t going to be concerned with everything those books teach.  If the site is attractive, if it loads relatively fast and still ranks well, then perfect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sjors Timmer - blog - &#187; Design versus development</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-33399</link>
		<dc:creator>Sjors Timmer - blog - &#187; Design versus development</dc:creator>
		<pubDate>Sat, 11 Nov 2006 13:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-33399</guid>
		<description>[...] Yesterday I came across this post on Bokardo, where he writes about why most webdesign books are more about development than on design Part of the problem is that HTML and CSS ain’t easy. No matter what people tell you, the CSS layout scheme is not for the faint of heart. [...]</description>
		<content:encoded><![CDATA[<p>[...] Yesterday I came across this post on Bokardo, where he writes about why most webdesign books are more about development than on design Part of the problem is that HTML and CSS ain’t easy. No matter what people tell you, the CSS layout scheme is not for the faint of heart. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daus</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-24098</link>
		<dc:creator>Daus</dc:creator>
		<pubDate>Sat, 07 Oct 2006 07:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-24098</guid>
		<description>Interesting</description>
		<content:encoded><![CDATA[<p>Interesting</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: momof2</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-23486</link>
		<dc:creator>momof2</dc:creator>
		<pubDate>Mon, 02 Oct 2006 15:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-23486</guid>
		<description>I am very glad you bring this topic up. I am a Desinger who does web design and also some print design. Lately I have been wondering about where to draw the line when it comes to writing the code. I write my own HTML and CSS but lately there seems to be a demad of doing some JSP from me as well. I mean, I alot more time to do the technical part then the Design. We work in deadline driven environment and it is very hard to get both going at a good pace.

Recently I was looking at the resume for a Web Desinger and I noticed that there is lot more emphasis on techology than on the actual design skills. I mean come on you want us to do design and part of back end promgramming. It's not like the pay has gone up that much either. Basically you are required to know Photoshop, Illustrator, Dreamweaver, Flash, Go Live, HTML, Xhtml, CSS, PHP, DHTML, Javascript, Ajax and be an exceptional designer and get paid $25.00/hr.

So that brings back to my question, where do you draw the line? I have on many occasion thought about going technical and learch some languages, but my passion is design and I keep coming back to it.</description>
		<content:encoded><![CDATA[<p>I am very glad you bring this topic up. I am a Desinger who does web design and also some print design. Lately I have been wondering about where to draw the line when it comes to writing the code. I write my own HTML and CSS but lately there seems to be a demad of doing some JSP from me as well. I mean, I alot more time to do the technical part then the Design. We work in deadline driven environment and it is very hard to get both going at a good pace.</p>
<p>Recently I was looking at the resume for a Web Desinger and I noticed that there is lot more emphasis on techology than on the actual design skills. I mean come on you want us to do design and part of back end promgramming. It&#8217;s not like the pay has gone up that much either. Basically you are required to know Photoshop, Illustrator, Dreamweaver, Flash, Go Live, HTML, Xhtml, CSS, PHP, DHTML, Javascript, Ajax and be an exceptional designer and get paid $25.00/hr.</p>
<p>So that brings back to my question, where do you draw the line? I have on many occasion thought about going technical and learch some languages, but my passion is design and I keep coming back to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2006-09-29 (Leapfroglog)</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-23072</link>
		<dc:creator>links for 2006-09-29 (Leapfroglog)</dc:creator>
		<pubDate>Fri, 29 Sep 2006 06:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-23072</guid>
		<description>[...] Bokardo - Social Web Design » 99% of Web Design Books are Not Joshua Porter points out that a lot of stuff that&#8217;s known under the name of web design is actually more like web development. Designing for the web should be about designing for end-users not (like development) about solving technical problems. (tags: design webdesign development webdevelopment web JoshuaPorter webdev) [...]</description>
		<content:encoded><![CDATA[<p>[...] Bokardo - Social Web Design » 99% of Web Design Books are Not Joshua Porter points out that a lot of stuff that&#8217;s known under the name of web design is actually more like web development. Designing for the web should be about designing for end-users not (like development) about solving technical problems. (tags: design webdesign development webdevelopment web JoshuaPorter webdev) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 绝缘电阻测试仪</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-21064</link>
		<dc:creator>绝缘电阻测试仪</dc:creator>
		<pubDate>Mon, 18 Sep 2006 04:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-21064</guid>
		<description>楼主说的确实对我很有用,多谢了!@_@~~</description>
		<content:encoded><![CDATA[<p>楼主说的确实对我很有用,多谢了!@_@~~</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JJ</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-20403</link>
		<dc:creator>JJ</dc:creator>
		<pubDate>Thu, 14 Sep 2006 13:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-20403</guid>
		<description>Whew, indeed, it's about time someone actually wrote this in any sort of a published piece!!  

While I've been saying it personally for years, job listings continue to list designer as being someone who's fluent in not only html and css but they love to add in there xml, php, ajax (if they've heard it mentioned somewhere), cgi, etc. 

Only in my first Web [design] job, way back in 1998 was I deigned the luxury of working with a development team to translate designs. Now it's all up to me, and frankly, I'm really sick of it, judging that about 75% of my tasks each day are fixing folks' code they get from, say, Word, guessing, et al. 

A little bit true, now, is that I do understand some of what you can and are less able to present, though, after vast experimentation, I find that most IS able to happen, with more and less success across browsers, +/- useability, download times, etc, to any design you might want to implement.

I think that the design+development corner has been turned by every place, and that there's no going back. Design, always a last-minute thought for content developers, are now throwing in even more stress-inducement for designers, requiring the most difficult part, development, to be the "designer" task as well. In my experience anyway.... My title shouldn't even be design, it's more like content-"code"-repairman, most frequently anyway. Until they want something really "Flashy," that is ... but don't even get me started on Flash!</description>
		<content:encoded><![CDATA[<p>Whew, indeed, it&#8217;s about time someone actually wrote this in any sort of a published piece!!  </p>
<p>While I&#8217;ve been saying it personally for years, job listings continue to list designer as being someone who&#8217;s fluent in not only html and css but they love to add in there xml, php, ajax (if they&#8217;ve heard it mentioned somewhere), cgi, etc. </p>
<p>Only in my first Web [design] job, way back in 1998 was I deigned the luxury of working with a development team to translate designs. Now it&#8217;s all up to me, and frankly, I&#8217;m really sick of it, judging that about 75% of my tasks each day are fixing folks&#8217; code they get from, say, Word, guessing, et al. </p>
<p>A little bit true, now, is that I do understand some of what you can and are less able to present, though, after vast experimentation, I find that most IS able to happen, with more and less success across browsers, +/- useability, download times, etc, to any design you might want to implement.</p>
<p>I think that the design+development corner has been turned by every place, and that there&#8217;s no going back. Design, always a last-minute thought for content developers, are now throwing in even more stress-inducement for designers, requiring the most difficult part, development, to be the &#8220;designer&#8221; task as well. In my experience anyway&#8230;. My title shouldn&#8217;t even be design, it&#8217;s more like content-&#8221;code&#8221;-repairman, most frequently anyway. Until they want something really &#8220;Flashy,&#8221; that is &#8230; but don&#8217;t even get me started on Flash!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: milo</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-20231</link>
		<dc:creator>milo</dc:creator>
		<pubDate>Wed, 13 Sep 2006 15:42:41 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-20231</guid>
		<description>Excellent!</description>
		<content:encoded><![CDATA[<p>Excellent!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pauric</title>
		<link>http://bokardo.com/archives/99-of-web-design-books-are-not/#comment-20089</link>
		<dc:creator>Pauric</dc:creator>
		<pubDate>Tue, 12 Sep 2006 16:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=454#comment-20089</guid>
		<description>Ray, from your blog "Monday, March 14, 2005
Content of New Media is Old Media

I've always been attracted to McLuhan's concept that "the content of new media is old media."

Can you resolve that with your statement here "Interface is content."

Btw, I'm not trying to catch you out (o; I wont pretend to have any education in this area, just very interested and would like to understand more, thanks</description>
		<content:encoded><![CDATA[<p>Ray, from your blog &#8220;Monday, March 14, 2005<br />
Content of New Media is Old Media</p>
<p>I&#8217;ve always been attracted to McLuhan&#8217;s concept that &#8220;the content of new media is old media.&#8221;</p>
<p>Can you resolve that with your statement here &#8220;Interface is content.&#8221;</p>
<p>Btw, I&#8217;m not trying to catch you out (o; I wont pretend to have any education in this area, just very interested and would like to understand more, thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
