<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" xml:lang="en">

    <title type="text">Squawk - Weblog</title>
    <subtitle type="text" />
    <link rel="alternate" type="text/html" href="http://www.squawkdesign.com/weblog/" />
    
    <updated>2008-09-07T17:03:33Z</updated>
    <rights>Copyright (c) 2008, Dominik Lenk</rights>
    <generator uri="http://expressionengine.com/" version="1.6.0">ExpressionEngine</generator>
    <id>tag:squawkdesign.com,2008:03:18</id>


    <link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-nc-nd/3.0/" /><link rel="self" href="http://feeds.feedburner.com/squawk/weblog" type="application/atom+xml" /><feedburner:emailServiceId>1176495</feedburner:emailServiceId><feedburner:feedburnerHostname>http://www.feedburner.com</feedburner:feedburnerHostname><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.rojo.com/add-subscription?resource=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://blog.rojo.com/RojoWideRed.gif">Subscribe with Rojo</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://feeds.feedburner.com/squawk/weblog" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fsquawk%2Fweblog" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><entry>
      <title>Keats’ Negative Capability and the creative process</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/253354313/" />
      <id>tag:squawkdesign.com,2008:weblog/2.145</id>
      <published>2008-03-18T01:00:00Z</published>
      <updated>2008-03-18T01:45:46Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Criticism &amp;amp; Discussion" scheme="http://www.squawkdesign.com/site/C38/" label="Criticism &amp;amp; Discussion" />
      <content type="html">
        &lt;blockquote&gt;&lt;p&gt;Negative Capability, that is when man is capable of being in uncertainties, mysteries, doubts without any irritable reaching after fact &amp;amp; reason. (John Keats, 1817)&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;
Negative Capability is a perplexing concept that is often made to be more difficult than it really is, even though Keats provides us with a detailed definition that is almost too concise to paraphrase. Nevertheless the accounts of what Negative Capability &lt;em&gt;truly&lt;/em&gt; is seem to differ a great deal.
&lt;/p&gt;
&lt;p&gt;
Negative Capability could be seen as a creative trance, which is supported by its references in Keats&amp;#8217; odes: In &lt;a href="http://www.bartleby.com/101/624.html" title="Ode to a Nightingale"&gt;&amp;#8220;Ode to a Nightingale&amp;#8221;&lt;/a&gt; the speaker hears a nightingale from a forest, upon which he enters a trance-like journey &amp;#8220;on the wings of poesy&amp;#8221;, which is only interrupted when he remembers events from his past, therefore invoking reason.
&lt;/p&gt;
&lt;p&gt;
Alternatively, you can describe Negative Capability as an intentional state of mind, allowing you to effectively ignore fact &amp;amp; reason in favour of &amp;#8220;a sense of beauty.&amp;#8221;
&lt;/p&gt;
&lt;p&gt;
These are just some quick attempts at trying to box in what the concept of Negative Capability stands for. However, what I am much more interested in doing is discussing what it means in relation to the creative process. While Negative Capability is most commonly associated with literature, it translates easily any area of expertise as it is simply a &amp;#8220;quality that forms a man of achievement&amp;#8221;.
&lt;/p&gt;
&lt;p&gt;
A while ago I had a discussion with Anne from &lt;a href="http://www.hotcards.com/blog/" title="Hot Cards' Blog"&gt;Hot Cards&lt;/a&gt; about how Negative Capability could influence the creative process. According to her Negative Capability allows you &amp;#8220;to explore creativity without the constant self-editing that can paralyse productivity&amp;#8221;.
&lt;/p&gt;
&lt;p&gt;
On the other hand she suggested that Negative Capability can be &amp;#8220;an excuse for laziness&amp;#8221;; a trance of creative expression can prevent a &amp;#8220;passionate intellectual struggle&amp;#8221;. Yet this is exactly what Keats was trying to explain in his letter to his brothers: Abolishing the intellectual ping-pong game in favour of a sense of beauty. Genuine Negative Capability might circumvent the classical creative process, yet that does not reveal anything about the quality of it&amp;#8217;s outcome.
&lt;/p&gt;
&lt;p&gt;
Negative Capability is a creative ideal, which some argue cannot be achieved. This forces us to re-evaluate Negative Capability as an excuse for laziness yet again: A false sense of Negative Capability may be an excuse, while sincere Negative Capability is an artistic ideal that even Keats struggled to achieve.
&lt;/p&gt;
&lt;p&gt;
Negative Capability always has a final outcome, one that ignores fact &amp;amp; reason in favour of a sense of beauty. I agree with Anne that &amp;#8220;languishing in a state of euphoric uncertainly could be career suicide&amp;#8221; as selling your idea becomes increasingly difficult when you are locked into trance.
&lt;br /&gt;
Knowing when to stop is the key to producing anything beautiful, whether produced through the laborious process involving fact &amp;amp; reason or through Negative Capability, even though true Negative Capability is not an eternal trance and should signal resolution automatically. 
&lt;/p&gt;
&lt;p&gt;
No matter whether Negative Capability is achievable or not, it is a creative asymptote, something that you should always try to reach. And if you believe that Negative Capability is unattainable, do not forget that it is you, who has to end your creative process after having found beauty.
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=ot0rRTF"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=ot0rRTF" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=zOiH87f"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=zOiH87f" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=WTWpynf"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=WTWpynf" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=HEqEOwf"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=HEqEOwf" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/253354313" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fnegative_capability%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/negative_capability/</feedburner:origLink></entry>

    <entry>
      <title>The dos &amp;amp; donts of online portfolios</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/233466509/" />
      <id>tag:squawkdesign.com,2008:weblog/2.138</id>
      <published>2008-02-12T01:26:01Z</published>
      <updated>2008-09-07T17:03:33Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Others" scheme="http://www.squawkdesign.com/site/C43/" label="Others" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;p&gt;&lt;img src="http://www.squawkdesign.com/img/uploads/main/paper_stack.jpg" border="0" alt="Paper Stack" width="538" height="211" /&gt;
&lt;br /&gt;
&lt;small&gt;If your online portfolio looks like this, you might as well not bother uploading it. Image by &lt;a href="http://www.flickr.com/photos/striatic/" title="Striatic on Flickr"&gt;striatic&lt;/a&gt;&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
It is lots of little details that make a great portfolio. A well-executed portfolio could be the difference between receiving a commission or not. There are enough online portfolios with amazing content that fail when it comes to usability. Even the best work will not keep visitors on your site, so make sure that your portfolio is accessible.
&lt;/p&gt;
&lt;p&gt;
Over the last year I have seen a lot of different takes on what portfolio design should look like, especially during the build up of trying to design my own one. Therefore, I would like to share some of the dos and donts of presenting work online.
&lt;/p&gt;
&lt;p&gt;
Before I start rambling about how the eye moves along a page or whether users like to scroll, lets establish a basic premise: The internet is the medium that it is because it allows users to quickly access information. If this information is not available or not presented in a friendly manner, users will not absorb your information, scroll on or leave your page.
&lt;br /&gt;
Therefore, it must be your goal to present your portfolio as user-friendly as possible.
&lt;/p&gt;
&lt;h4&gt;The basics&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Keep your portfolio up to date.&lt;/li&gt;
&lt;li&gt;Make sure that your portfolio loads quickly. This is pretty obvious, but I have seen portfolios that took a couple of minutes to load all the images (on a broadband connection).&lt;/li&gt;
&lt;li&gt;Sort your projects either by date or in such a way so that what you want people to see is at the top.&lt;/li&gt;
&lt;li&gt;Give visitors the means to contact you.&lt;/li&gt;
&lt;li&gt;Reserve a spot on your webpage to tell your visitors that you are available for hire/freelance work. Most people are shy and might not contact you otherwise.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;&amp;quot;Creative&amp;quot; interfaces&lt;/h4&gt;
&lt;p&gt;
Unless your want to bore your visitors with loaders, next buttons and fancy animations, &lt;strong&gt;stay away from Flash&lt;/strong&gt;. Great things can be done in Flash, but I believe that it should complement any page (including your portfolio) and not replace it.
&lt;br /&gt;
Flash portfolios might look impressive but I find them very hard to navigate. The place where you try to win new customers is not the place for interface experiments: Keep it simple and let the content speak.
&lt;/p&gt;
&lt;h4&gt;Portfolio pictures&lt;/h4&gt;
&lt;p&gt;
A portfolio should showcase your work and make it look its best. Use big, representative images. I found that sometime cropping helps to make an image look more interesting, even if you are essentially missing information.
&lt;/p&gt;
&lt;p&gt;
Additionally, consider the environment for your images. A plain screenshot of a webpage looks boring, but if you show it in a browser window of the right size with a subtle drop-shadow, the matter starts to look different. (&lt;a href="http://www.artofadambetts.com/weblog/?p=186" title="Mac OS X drop shadows"&gt;A photoshop style to create OS X like window drop shadows.&lt;/a&gt;)
&lt;/p&gt;
&lt;h4&gt;One page vs. multiple pages&lt;/h4&gt;
&lt;p&gt;
Some portfolios, especially those with flash interfaces, use the next/previous system to let users navigate their portfolio. Personally, I dislike this approach, as it creates the need for unnecessary clicks. Letting the user scroll though a list of projects is not only more effective, it also allows them to see the overall picture, the relationship between your work.
&lt;/p&gt;
&lt;p&gt;
Independent of which approach you choose, include a brief, yet juicy descriptions for all the items in your portfolio. If you need more space, create a &amp;quot;Click here for more&amp;quot; link. (In my portfolio I created &amp;#8216;detail&amp;#8217; pages.)
&lt;/p&gt;
&lt;h4&gt;The number of items in your portfolio&lt;/h4&gt;
&lt;p&gt;
The number of items in my portfolio is what I though about the most when I redesigned this site. Too few items, and visitors will doubt your skills. Too many and they will become bored or think that you do not make a selection of what goes into your portfolio. Neither impression is good and the line between too few and too many is very thin.
&lt;/p&gt;
&lt;p&gt;
Personally, I prefer to have a smaller selection of work in my portfolio, rather than creating a large all encompassing list. Smaller, newer pieces of work that wouldn&amp;#8217;t necessarily make my portfolio will then be published in my blog. This also has the advantage of allowing visitors to provide you with feedback.
&lt;/p&gt;
&lt;h4&gt;What do you think?&lt;/h4&gt;
&lt;p&gt;
Quite a few of my points are subjective, so I would like hear your input on this. If you have already created your online portfolio, what was important to you during its creation. And if you are in the process of building it, what do you value in a well-executed portfolio?
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=4jkAiPE"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=4jkAiPE" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=FEkQOhe"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=FEkQOhe" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=OIeFdXe"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=OIeFdXe" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=3Yo6fne"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=3Yo6fne" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/233466509" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fthe_dos_and_donts_of_online_portfolios%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/the_dos_and_donts_of_online_portfolios/</feedburner:origLink></entry>

    <entry>
      <title>Blackletter black sheep</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/223682389/" />
      <id>tag:squawkdesign.com,2008:weblog/2.135</id>
      <published>2008-01-26T19:11:01Z</published>
      <updated>2008-01-27T13:29:29Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="From my sketchbook" scheme="http://www.squawkdesign.com/site/C47/" label="From my sketchbook" />
      <category term="Illustration &amp;amp; Animation" scheme="http://www.squawkdesign.com/site/C46/" label="Illustration &amp;amp; Animation" />
      <category term="Others" scheme="http://www.squawkdesign.com/site/C43/" label="Others" />
      <content type="html">
        &lt;p&gt;It is time again to upload a page from my sketchbook. I withheld this particular one for a while as I thought that it might be used somewhere else&amp;#8230; it wasn&amp;#8217;t&amp;#8230; so here it is:
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/blackletter_black_sheep.jpg" border="0" alt="image" name="image" width="538" height="356" /&gt;
&lt;br /&gt;
&lt;small&gt;The Blackletter Black Sheep: (In)proper capitalisation makes you lonely&lt;/small&gt;
&lt;/p&gt;
&lt;h4&gt;Blackletter black sheep&lt;/h4&gt;
&lt;p&gt;
The typographers out there probably already know this, but the story goes as follows: In 1936 the type-designer Fredric Goudy received a certificate for excellence in type design. After having glanced at it, he remarked that the person who designed this certificate would probably also steal sheep. The reason for this assault was that the type was set in all-caps Blackletter, which not only looks ridiculous but is also incredibly illegible.
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=J6nbnsD"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=J6nbnsD" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=DTldSBd"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=DTldSBd" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=XWx96Kd"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=XWx96Kd" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=ilhy9Td"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=ilhy9Td" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/223682389" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fblackletter_black_sheep%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/blackletter_black_sheep/</feedburner:origLink></entry>

    <entry>
      <title>Targeted marketing &amp;amp; Sesame Street</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/199500699/" />
      <id>tag:squawkdesign.com,2007:weblog/2.128</id>
      <published>2007-12-13T01:45:00Z</published>
      <updated>2008-02-12T01:52:09Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Blogging" scheme="http://www.squawkdesign.com/site/C48/" label="Blogging" />
      <category term="Criticism &amp;amp; Discussion" scheme="http://www.squawkdesign.com/site/C38/" label="Criticism &amp;amp; Discussion" />
      <category term="Others" scheme="http://www.squawkdesign.com/site/C43/" label="Others" />
      <content type="html">
        &lt;p&gt;A couple of days ago I posted a link to a video of a Sesame Street episode: Suspicious looking salesman Lefty is trying to sell Enie an O. While everybody agrees that one could not possibly refuse this offer to buy an O for only a nickel, the video ends with Ernie not buying the O. 
&lt;/p&gt;
&lt;p&gt;
&lt;object width="425" height="355"&gt;&lt;param name="movie" value="http://www.youtube.com/v/ajHVLJG0298&amp;amp;rel=0&amp;amp;color1=0xd6d6d6&amp;amp;color2=0xf0f0f0&amp;amp;border=0" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;embed src="http://www.youtube.com/v/ajHVLJG0298&amp;amp;rel=0&amp;amp;color1=0xd6d6d6&amp;amp;color2=0xf0f0f0&amp;amp;border=0" type="application/x-shockwave-flash" wmode="transparent" width="425" height="355"&gt;&lt;/embed&gt;&lt;/object&gt;
&lt;/p&gt;
&lt;p&gt;
You can deduce a great deal about talking to your own customers or weblog visitors from the conversation that takes place between Lefty and Ernie, even if you do not sell letters of the alphabet. I re-watched Lefty&amp;#8217;s sales pitch multiple times and jotted down some notes:
&lt;/p&gt;
&lt;h4&gt;You are special&lt;/h4&gt;
&lt;p&gt;
&amp;#8220;Hey you. Who, me? Ssshh. Who, me? Riiiight.&amp;#8221; This one of the standard openings to any Sesame street video that features Lefty trying to sell Ernie some totally useless object. Whether it is a letter of the alphabet, an empty box or a bit of air, Ernie always turns around and starts a conversation with Lefty.
&lt;/p&gt;
&lt;p&gt;
A more successful version of the opening line is &amp;#8220;Hey Ernie. Who, me? Sssh. Who, me? Riiiight.&amp;#8221; The only difference is that Lefty addressed Ernie with his name, instead of &amp;#8220;Hey you&amp;#8221;. One of the best way to reach someone that you don&amp;#8217;t know is using their name. Research shows that the most suggestive word for people to listen up to is their name and not &amp;#8220;Free&amp;#8221; or &amp;#8220;New&amp;#8221;. Let&amp;#8217;s face it: We are all a bit egocentric and literally flattered when someone wants to identify with us.
&lt;/p&gt;
&lt;h4&gt;Differentiate yourself and do not sell O&amp;#8217;s&lt;/h4&gt;
&lt;p&gt;
Even though Lefty&amp;#8217;s sales pitch is slightly ridiculous, he tries to differentiate himself and tailors his offer specifically to Ernie. He provides reasons why Ernie should buy the O, (even if they are not as substantial as you would hope that they would be.) &amp;#8220;It is not often that I offer, what could you ask for more&amp;#8221;, &amp;#8220;And for no extra money&amp;#8221; or even the hint of additional services such as quick checkout. ("Just buy the O and take it home tonight.")
&lt;/p&gt;
&lt;p&gt;
Ernie does not buy the O in the end. The reasons for this are twofold. Even though Lefty provides a great performance trying to sell his O, the O is really useless. In the &lt;em&gt;real&lt;/em&gt; world you need to set yourself apart and offer something of &lt;em&gt;real&lt;/em&gt; value. This needs to be great content or even better service. If you try to sell O&amp;#8217;s, customers will quickly turn their back on you.
&lt;/p&gt;
&lt;p&gt;
Whenever trying to create repeat visitors to your weblog or selling your services, give them something to remember you by. The one thing that they tend to remember is the fact that you remember them. If you reinforce this impression with great content and services you are set to go. Riiiight.
&lt;br /&gt;

&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=GMIZ1yC"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=GMIZ1yC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=7QsXUec"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=7QsXUec" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=hN5aUDc"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=hN5aUDc" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=CkR0UDc"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=CkR0UDc" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/199500699" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Ftargeted_marketing_and_sesame_street%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/targeted_marketing_and_sesame_street/</feedburner:origLink></entry>

    <entry>
      <title>Adjust your posting frequency to keep the quality of your weblog entries high</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/195868941/" />
      <id>tag:squawkdesign.com,2007:weblog/2.126</id>
      <published>2007-12-06T02:34:00Z</published>
      <updated>2007-12-06T02:42:08Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Blogging" scheme="http://www.squawkdesign.com/site/C48/" label="Blogging" />
      <category term="Criticism &amp;amp; Discussion" scheme="http://www.squawkdesign.com/site/C38/" label="Criticism &amp;amp; Discussion" />
      <content type="html">
        &lt;p&gt;The worst way to start an entry in your blog is by apologising to your readers that you have not posted more often.
&lt;/p&gt;
&lt;p&gt;
So here is what I will do: I would like to apologise for not posting on this weblog over the past two weeks. Partially because I really have not written anything over that period, but mainly because I want to make a point.
&lt;/p&gt;
&lt;h4&gt;Quality vs. quantity&lt;/h4&gt;
&lt;p&gt;
There are many people who say that it is not your posting frequency that attracts readers but rather the quality of your content. While this is true, it is also a blatant lie.
&lt;/p&gt;
&lt;p&gt;
The quality of your content attracts readers, especially RSS subscribers. Yet these readers will quickly abandon your ship if you cannot continue to provide quality content.
&lt;/p&gt;
&lt;h4&gt;Continuity is key&lt;/h4&gt;
&lt;p&gt;
That being said, it is important to find a rhythm. Readers do not expect weblog entries every day, in fact it thoroughly annoys them if their RSS reader gets flooded with posts from only one site.
&lt;/p&gt;
&lt;p&gt;
If you are comfortable with posting every day, do so. If you are comfortable with posting every week or even every two weeks, this is also fine. Yet &lt;strong&gt;visitors should be able to anticipate your next weblog entry by looking at your archive.&lt;/strong&gt;
&lt;/p&gt;
&lt;h4&gt;Taking quantity out of the equation&lt;/h4&gt;
&lt;p&gt;
It should not really be a question of quality vs. quantity, but whether you manage to find a posting frequency that allows you to keep the quality weblog entries  at a high level. Take quantity out of the equation.
&lt;/p&gt;
&lt;p&gt;
Applying this to my own habits, comes as a harsh realisation: I have one of the worst posting frequencies, ranging from daily to almost monthly. I will hopefully learn from it and no longer have to apologise to readers in the future. Hopefully.
&lt;/p&gt;
&lt;p&gt;
I would like to hear from you, which posting frequency you find comfortable to read? If you have your own weblog which frequency do you find comfortable to write for? What dictates this frequency? Should you increase or decrease it? Answers and questions alike, please find your way into the comments.
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=vzBVEsC"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=vzBVEsC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=sJRW8Nc"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=sJRW8Nc" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=pF2pB4c"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=pF2pB4c" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=3Yk4XYc"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=3Yk4XYc" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/195868941" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fposting_frequency%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/posting_frequency/</feedburner:origLink></entry>

    <entry>
      <title>The hidden Inspector of Safari 3</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/188472118/" />
      <id>tag:squawkdesign.com,2007:weblog/2.122</id>
      <published>2007-11-21T20:13:59Z</published>
      <updated>2008-02-13T22:06:47Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Mac" scheme="http://www.squawkdesign.com/site/C18/" label="Mac" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;p&gt;Quite a few web-developers use &lt;a href="http://www.getfirebug.com/" title="Get Firebug for Firefox"&gt;Firebug&lt;/a&gt;, a Firefox plugin that allows you to view, inspect and debug your source code. A graphical load-time graph is also included to analyse performance.
&lt;/p&gt;
&lt;p&gt;
With a few Terminal hacks, &lt;a href="http://www.apple.com/macosx/features/safari.html" title="Apple Safari"&gt;Safari 3&lt;/a&gt; now supports this without a plugin. Even though the new Safari browser still crashes regularly, I really like this feature.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/safari_3_time.jpg" border="0" alt="Load-time graph in Safari 3" width="538" height="355" /&gt;
&lt;br /&gt;
&lt;small&gt;Safari&amp;#8217;s new Inspector showing a load-time graph of squawkdesign.com&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
Since Safari&amp;#8217;s new inspector is not enabled by default you have to open &lt;em&gt;Terminal&lt;/em&gt; (which you can find inside your Utilities folder) and run the following command:
&lt;br /&gt;
&lt;/p&gt;&lt;div class="codeblock"&gt;&lt;code&gt;
&lt;span style="color: #0000BB"&gt;defaults&amp;nbsp;write&amp;nbsp;com&lt;/span&gt;&lt;span style="color: #007700"&gt;.&lt;/span&gt;&lt;span style="color: #0000BB"&gt;apple&lt;/span&gt;&lt;span style="color: #007700"&gt;.&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Safari&amp;nbsp;WebKitDeveloperExtras&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;bool&amp;nbsp;true&lt;/span&gt;
&lt;/code&gt;&lt;/div&gt;&lt;p&gt;
Re-launch Safari and you will find a new list item when you control-click on any element on your page: Inspect.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/safari_3_menu.jpg" border="0" alt="Right-click menu" width="538" height="198" /&gt;
&lt;br /&gt;
&lt;small&gt;Control-click (right-click) on any element and you will see a new menu item: &amp;#8216;Inspect&amp;#8217;&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
Initially, the Inspector is shown in a new window. However, if you click on &lt;img src="http://www.squawkdesign.com/img/uploads/main/safari_3_window.jpg" style="vertical-align:middle;" border="0" alt="a small button displaying a set of rectangles in the bottom-left of the Inspector window" width="20" height="20" /&gt;, then it is shrunk into the window that it is inspecting.
&lt;/p&gt;
&lt;p&gt;
Additionally, if you click on &lt;img src="http://www.squawkdesign.com/img/uploads/main/safari_3_collapse.jpg" border="0" style="vertical-align:middle;" alt="a small button displaying a downward facing triangle in the bottom-left of the Inspector window" width="20" height="20" /&gt;, then you will get some additional items in the sidebar. One of them shows a load-time graph, shown in the first image of this article.
&lt;/p&gt;
&lt;p&gt;
Of course you can also simply look at your html code, stylesheets or any file that is being loaded. Just select it in the sidebar on the left.
&lt;/p&gt;
&lt;p&gt;
Have a play around with Safari&amp;#8217;s new Inspector and tell me what you think. I have been using it for a couple of days and up to now I cannot complain.
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=n78CAMB"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=n78CAMB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=Or5Katb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=Or5Katb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=PskaYgb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=PskaYgb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=6DzYKRb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=6DzYKRb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/188472118" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fhidden_inspector%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/hidden_inspector/</feedburner:origLink></entry>

    <entry>
      <title>How to capitalise headlines?</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/186338268/" />
      <id>tag:squawkdesign.com,2007:weblog/2.118</id>
      <published>2007-11-17T13:43:00Z</published>
      <updated>2007-11-17T13:44:34Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Typography" scheme="http://www.squawkdesign.com/site/C40/" label="Typography" />
      <content type="html">
        &lt;p&gt;With the introduction of the weblog to this site I often asked myself how I ought to capitalise my headlines. This gets especially tricky as I was born in Germany, where &lt;em&gt;all&lt;/em&gt; nouns are always capitalised.
&lt;/p&gt;
&lt;p&gt;
The practice of capitalising all nouns was also common in English before the 1800&amp;#8217;s but has gradually become extinct.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/USA_declaration_independence.jpg" border="0" alt="image" name="image" width="538" height="230" /&gt;
&lt;br /&gt;
&lt;small&gt;The American Declaration of Independence. Observe the capitalised &lt;em&gt;Representatives&lt;/em&gt;.&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
An example for this is the American Declaration of Independence, in which all nouns were capitalised.
&lt;/p&gt;
&lt;h4&gt;Capitalisation in today&amp;#8217;s publications&lt;/h4&gt;
&lt;p&gt;
Nowadays, capitalisation is a science of its own with every major publication adopting a different technique.
&lt;/p&gt;
&lt;p&gt;
As a rule of thumb, British publishers tend to use &lt;strong&gt;sentence-style capitalisation&lt;/strong&gt;, which capitalises only the first word and all proper nouns. A proper noun represents a specific person, place or thing, unlike a common noun, which is more generic. All names are automatically proper nouns, as there is only one instance of the person, place or thing. &lt;em&gt;London&lt;/em&gt; or the &lt;em&gt;French&lt;/em&gt; are both proper nouns, while &lt;em&gt;city&lt;/em&gt; or &lt;em&gt;people&lt;/em&gt; are common nouns.
&lt;/p&gt;
&lt;p&gt;
Practice among U.S. publishers is more varied. Some choose to capitalise all words except prepositions, internal articles or conjunctions, while others simply capitalise words with more than 3 or 4 letters.
&lt;/p&gt;
&lt;p&gt;
In the English language there have been relatively few style-guides for capitalisation. One which I did come across was the &lt;a href="http://www.ritter.org.uk/AboutOGS.html" title="The Oxford Guide to Style"&gt;The Oxford Guide to Style&lt;/a&gt;. (Also check out their link section: It has some typographic goodies.)
&lt;/p&gt;
&lt;p&gt;
Unfortunately, due to the few regulations on capitalisation, almost anything is allowed, including the bad practice of SHOUTING. Please, even though it might be allowed, do not fall to such depths, do not resort to getting attention at the cost of good typography. (If you are interested check out &lt;a href="http://groups.google.com/group/capsoff" title="CAPSoff"&gt;the initiative to abolish the CAPS key&lt;/a&gt;.)
&lt;/p&gt;
&lt;p&gt;
The equally varied capitalisation in creative works is just as ignorant of (the few) typographic rules, yet is acceptable as it aims for feedback from the viewer/reader.
&lt;/p&gt;
&lt;p&gt;
Bringing our attention back to headlines, it does not matter (to a certain extent) how you choose to capitalise them, but rather that you are persistent in your practice.
&lt;/p&gt;
&lt;p&gt;
In the future I will employ sentence-style capitalisation with the possible, occasional exception as long as it is justified. I still have to fix a couple of older weblog entries, but from now on, sentence-style capitalisation is all that you will see on this weblog.
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=ZKyrcDB"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=ZKyrcDB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=ESOz8Qb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=ESOz8Qb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=8SJAiQb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=8SJAiQb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=insGEwb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=insGEwb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/186338268" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fhow_to_capitalise_headlines%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/how_to_capitalise_headlines/</feedburner:origLink></entry>

    <entry>
      <title>99 Reasons why we should put an end to bullet lists</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/185685945/" />
      <id>tag:squawkdesign.com,2007:weblog/2.117</id>
      <published>2007-11-16T00:48:02Z</published>
      <updated>2007-11-21T02:06:52Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Others" scheme="http://www.squawkdesign.com/site/C43/" label="Others" />
      <content type="html">
        &lt;p&gt;Many blogs have now specialised in internet marketing, providing tips on how to increase the number of RSS readers or how to write content that &amp;#8216;goes viral&amp;#8217;. While these resources are very helpful I believe that they are often too long.
&lt;/p&gt;
&lt;p&gt;
Imagine the headline &amp;#8220;99 ways to gain RSS subscribers&amp;#8221;. I am sure that most of these ninety-nine tips will work, but most readers will not be able to focus on any of them due to their sheer quantity.
&lt;br /&gt;
The article ceases to be helpful and simply becomes a marketing machine to attract more visitors to the authors blog, instead of also helping you do the same.
&lt;/p&gt;
&lt;p&gt;
Due to the information bombardment that many of the weblogs practise today, I have decided to start something different: I want to highlight &lt;em&gt;one&lt;/em&gt; issue at a time.
&lt;br /&gt;
I might not be able to make the information as easily digestible as a bullet list with ninety-nine items, but thorough explanation will make up for this.
&lt;br /&gt;
Of course this does not mean that I will abolish bullet lists, but simply that I want to focus on a single topic in an article.
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;For those still waiting for a sensational revelation about my choice of headline, read the last paragraph again. (This weblog post is an announcement of the juicy things to come.)&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
Stay tuned for some in-depth analysis to captivate your readers on your own blog. I hope I am doing the same on my own right now. (If I am, good. Otherwise,&amp;#8230; tell me in  the comments.)
&lt;/p&gt;
&lt;h4&gt;A non-related addendum&lt;/h4&gt;&lt;p&gt;
Some of the other weblog entries that I will be planning are packaged as the plain old goodie. Fasten your seat-belts for some more photoshop brushes, a roundup of great free icons and a couple of illustration blurbs.
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=qhEGD3B"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=qhEGD3B" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=d83FKfb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=d83FKfb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=YJkVHfb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=YJkVHfb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=rvySDrb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=rvySDrb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/185685945" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2F99_reasons_why_we_should_put_an_end_to_bullet_lists%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/99_reasons_why_we_should_put_an_end_to_bullet_lists/</feedburner:origLink></entry>

    <entry>
      <title>Can the blogosphere see beyond black &amp;amp; white?</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/181184229/" />
      <id>tag:squawkdesign.com,2007:weblog/2.113</id>
      <published>2007-11-07T16:48:00Z</published>
      <updated>2007-11-07T16:51:10Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Criticism &amp;amp; Discussion" scheme="http://www.squawkdesign.com/site/C38/" label="Criticism &amp;amp; Discussion" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;p&gt;A couple of days I eagerly commented on a weblog entry over at the German &lt;a href="http://www.fontblog.de/roter-teppich-die-fontstars-2007-kommen" title="FontBlog.de"&gt;FontBlog.de&lt;/a&gt; that announced the arrival of the so called FontStars 2007: This years newcomers to the  world of type.
&lt;/p&gt;
&lt;p&gt;
Later I recognised through the aid of a fellow commenter that my positive reaction in my comment was most likely not justified. While this might simply be a difference of taste, I can see hasty comments all over the internet and I have to ask myself whether the blogosphere can see beyond black &amp;amp; white.
&lt;/p&gt;
&lt;p&gt;
Common comments are based either on like or dislike: Yes, this is great or no, I do not like it. However, these comments do not add anything to the conversation and are often not well-thought out as they have been written too quickly.
&lt;/p&gt;
&lt;p&gt;
Most things are not black or white and neither are weblog comments. The blogosphere can be improved greatly if readers refrain from giving a biased account of their own opinion, if they are no longer afraid to be in the grey.
&lt;/p&gt;
&lt;p&gt;
Of course, it does happen that you completely disagree with the content of a weblog post. In this case, the &amp;#8216;ideal negative comment&amp;#8217; should include constructive criticism and not a blatant attack on the author.
&lt;/p&gt;
&lt;p&gt;
And if you truly agree with the author, ask yourself why you agree with him, as well as how you can put this into words. This not only increases the level of the conversation, it also prevents you from writing a comment that you might regret later. (For example, after you read the weblog post a second time.)
&lt;/p&gt;
&lt;p&gt;
This is a short weblog post from my site with a short conclusion: Think about your comments and &amp;#8216;do not be afraid to be in the grey&amp;#8217;.
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;P.S.: An illustration that would fit this weblog post brilliantly is &lt;a href="http://www.bearskinrug.co.uk/_articles/2007/05/09/the_amorphous_blob/" title="The Amorphous Blob"&gt;Kevin Cornell&amp;#8217;s Amorphous Blob&lt;/a&gt;.&lt;/em&gt;
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=RHlXL4B"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=RHlXL4B" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=NawXCGb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=NawXCGb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=S6RFXIb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=S6RFXIb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=xJ3Xxwb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=xJ3Xxwb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/181184229" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fcan_the_blogosphere_see_beyond_black_and_white%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/can_the_blogosphere_see_beyond_black_and_white/</feedburner:origLink></entry>

    <entry>
      <title>13 Free Photoshop Brushes: Coffee Stains</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/179021803/" />
      <id>tag:squawkdesign.com,2007:weblog/2.110</id>
      <published>2007-11-02T16:37:59Z</published>
      <updated>2007-11-02T18:26:42Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Goodies" scheme="http://www.squawkdesign.com/site/C24/" label="Goodies" />
      <category term="Photoshop &amp;amp; Illustrator" scheme="http://www.squawkdesign.com/site/C35/" label="Photoshop &amp;amp; Illustrator" />
      <content type="html">
        &lt;p&gt;&lt;img src="http://www.squawkdesign.com/img/uploads/main/coffee_stain_title.png" border="0" alt="Coffee Stain Title Image"  width="535" height="158" /&gt;
&lt;/p&gt;
&lt;p&gt;
If you spend a couple of nights working on one or the other project you will appreciate coffee.
&lt;br /&gt;
However, I found that I seem to like the coffee stains on paper even more. So I decided to share this visual sensation and created 13 free coffee stain Photoshop brushes.
&lt;/p&gt;
&lt;h4&gt;Download .abr file&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.squawkdesign.com/img/uploads/main/coffee_brushes.zip" title="Click here to download the .abr file"&gt;Click here to download the coffee stain brushes&lt;/a&gt;
&lt;br /&gt;
8.4MB&amp;#8212;Includes one .abr file&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;How to install&lt;/h4&gt;
&lt;ol&gt;
&lt;li&gt;Download the .abr file.&lt;/li&gt;
&lt;li&gt;Copy the file into your &lt;em&gt;Photoshop/Presets/Brushes&lt;/em&gt; folder.&lt;/li&gt;
&lt;li&gt;Restart Photoshop or load the file manually by clicking on the small arrow on the top right of your brushes palette.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;
&lt;em&gt;Alternatively you can just double-click the .abr file once you downloaded it to append it to your current brush selection.&lt;/em&gt;
&lt;/p&gt;
&lt;h4&gt;More Brushes&lt;/h4&gt;&lt;p&gt;
Earlier this year I collaborated with &lt;a href="http://www.bittbox.com" title="BittBox"&gt;BittBox&lt;/a&gt; to create &lt;a href="http://www.squawkdesign.com/weblog/comments/photoshop_ink_splatter_brushes/" title="Photoshop ink splatter brushes"&gt;Photoshop Ink Splatter Brushes.&lt;/a&gt;. The &lt;a href="http://www.squawkdesign.com/weblog/comments/splatter_splatter_drop_drop/" title="original ink splatter images can still be found here"&gt;original ink splatter images can still be found here.&lt;/a&gt;
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=UhrCLuB"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=UhrCLuB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=KFAoDZb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=KFAoDZb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=h7OLU3b"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=h7OLU3b" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=0FlWIrb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=0FlWIrb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/179021803" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2F13_free_photoshop_brushes_coffee_stains%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/13_free_photoshop_brushes_coffee_stains/</feedburner:origLink></entry>

    <entry>
      <title>Squawk redesign part 3: Type choices &amp;amp; SIFR</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/177976877/" />
      <id>tag:squawkdesign.com,2007:weblog/2.104</id>
      <published>2007-10-26T10:40:00Z</published>
      <updated>2008-01-11T01:43:50Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Current Projects" scheme="http://www.squawkdesign.com/site/C13/" label="Current Projects" />
      <category term="Typography" scheme="http://www.squawkdesign.com/site/C40/" label="Typography" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;p&gt;This is the third instalment of the series on how the redesign of this site developed. This time I will be focusing mainly on typography, as well as on the implementation of SIFR.
&lt;/p&gt;
&lt;p&gt;
If you have scanned my archives you might have found a link to a site explaining &lt;a href="http://www.philweavers.net/articles/view/id/48/" title="Lucida Hybrid: The 'Grande' Alternative"&gt;the differences between the versions/substitutes of &lt;em&gt;Lucida Grande&lt;/em&gt;&lt;/a&gt; on different operating systems. I will reiterate the content of this link, mainly because I want you to stay on my site;-)
&lt;/p&gt;
&lt;p&gt;
I am big fan of &lt;em&gt;Lucida Grande&lt;/em&gt;, but unfortunately it is not installed by default on windows machines. I do not know about Linux, but I suspect that the font is also missing on quite a few systems.
&lt;/p&gt;
&lt;p&gt;
Since &lt;em&gt;Lucida Grande&lt;/em&gt; is not installed on at least half of the systems visiting this website, we revert to &lt;em&gt;Lucida Sans Unicode&lt;/em&gt; and &lt;em&gt;Lucida Sans&lt;/em&gt;. Both of these have a couple of flaws:&lt;em&gt;Lucida Sans Unicode&lt;/em&gt; looks almost like &lt;em&gt;Lucida Grande&lt;/em&gt;, yet is a menace to look at in &lt;strong&gt;Bold&lt;/strong&gt; and &lt;em&gt;Italic&lt;/em&gt;.
&lt;br /&gt;
On the other hand &lt;em&gt;Lucida Sans&lt;/em&gt; looks great in bold and italic, yet is an insult to look at, when displayed normally.
&lt;/p&gt;
&lt;p&gt;
So what can be done to make sure that we get the nice traits from the different font-families: Selective CSS here we come....
&lt;br /&gt;
&lt;/p&gt;&lt;div class="codeblock"&gt;&lt;code&gt;
&lt;span style="color: #007700"&gt;*&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#123;&amp;nbsp;font&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;family&lt;/span&gt;&lt;span style="color: #007700"&gt;:&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'Lucida&amp;nbsp;Sans&amp;nbsp;Unicode'&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'Lucida&amp;nbsp;Grande'&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'&amp;nbsp;Trebuchet&amp;nbsp;MS'&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Helvetica&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Verdana&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Arial&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;sans&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;serif&lt;/span&gt;&lt;span style="color: #007700"&gt;;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#125;&lt;br /&gt;strong&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;em&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;#123;&amp;nbsp;font&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;family&lt;/span&gt;&lt;span style="color: #007700"&gt;:&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'Lucida&amp;nbsp;Sans'&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'Lucida&amp;nbsp;Grande'&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'&amp;nbsp;MS'&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Helvetica&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Verdana&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;Arial&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;sans&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;serif&lt;/span&gt;&lt;span style="color: #007700"&gt;;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#125;&lt;br /&gt;strong&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;#123;&amp;nbsp;font&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;weight&lt;/span&gt;&lt;span style="color: #007700"&gt;:&lt;/span&gt;&lt;span style="color: #0000BB"&gt;bold&lt;/span&gt;&lt;span style="color: #007700"&gt;;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#125;&lt;br /&gt;em&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;#123;&amp;nbsp;font&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;style&lt;/span&gt;&lt;span style="color: #007700"&gt;:&lt;/span&gt;&lt;span style="color: #0000BB"&gt;italic&lt;/span&gt;&lt;span style="color: #007700"&gt;;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#125;&lt;/span&gt;
&lt;/code&gt;&lt;/div&gt;&lt;p&gt;
This way all strong or italic elements use &lt;em&gt;Lucida Sans&lt;/em&gt;, while all other text is rendered in &lt;em&gt;Lucida Sans Unicode&lt;/em&gt;. &lt;em&gt;Lucida Grande&lt;/em&gt; is invoked on most Macs, because they have neither of its alternatives. &lt;em&gt;Trebuchet MS&lt;/em&gt;, &lt;em&gt;Helvetica&lt;/em&gt;, &lt;em&gt;Verdana&lt;/em&gt; and &lt;em&gt;Arial&lt;/em&gt; are the remaining fallback options for those that do not have any Lucida version installed.
&lt;/p&gt;
&lt;h4&gt;The headings&lt;/h4&gt;
&lt;p&gt;
As you probably saw the headings on this website are not displayed using &lt;em&gt;Lucida Grande&lt;/em&gt;. If everything works well, you should see them drawn in a slabserif font. (Let&amp;#8217;s thank SIFR for font goodness at this point. Go on, kneel on the floor...)
&lt;/p&gt;
&lt;p&gt;
The choice of font for my headings was determined by &lt;strong&gt;readability&lt;/strong&gt; and &lt;strong&gt;price&lt;/strong&gt;. By the latter I am referring to &amp;#8216;free&amp;#8217;, which (of course) limits my selection significantly.
&lt;br /&gt;
Through some research online I decided that a slabserif font would be the best choice for displaying titles, especially because it remains readable down to very small sizes.
&lt;/p&gt;
&lt;p&gt;
The font used in the titles is called &lt;em&gt;GeoSlab703 Md BT&lt;/em&gt;. If you do a standard search with &lt;a href="http://www.google.com/search?q=GeoSlab703%20Md%20BT" title="Search for GeoSlab703 Md BT on Google"&gt;Google&lt;/a&gt; you are bound to find a download link. I will not link to one directly, because they seem to change every couple of days.
&lt;/p&gt;
&lt;h4&gt;SIFR: Font heaven &amp;amp; testing hell&lt;/h4&gt;
&lt;p&gt;
I used &lt;a href="http://novemberborn.net/sifr3" title="SIFR 3"&gt;SIFR 3&lt;/a&gt; to dynamically replace my standard Times font with the &lt;em&gt;GeoSlab703 Md BT&lt;/em&gt;. If you are interested in SIFR you can read up on how to use it in the &lt;a href="http://wiki.novemberborn.net/sifr3" title="SIFR 3 wiki"&gt;SIFR 3 wiki&lt;/a&gt;. Remember to do lots of testing in different browsers.
&lt;br /&gt;
There is only one thing about SIFR that took me a long time to find out: How to style child nodes of a sifrerised element differently. So I will quickly outline my mistake and method, hoping that it will save you time:
&lt;br /&gt;
&lt;/p&gt;&lt;div class="codeblock"&gt;&lt;code&gt;
&lt;span style="color: #0000BB"&gt;sIFR&lt;/span&gt;&lt;span style="color: #007700"&gt;.&lt;/span&gt;&lt;span style="color: #0000BB"&gt;replace&lt;/span&gt;&lt;span style="color: #007700"&gt;(&lt;/span&gt;&lt;span style="color: #0000BB"&gt;font&lt;/span&gt;&lt;span style="color: #007700"&gt;,&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#123;&lt;br /&gt;&amp;nbsp;&amp;nbsp;selector&lt;/span&gt;&lt;span style="color: #007700"&gt;:&amp;nbsp;&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'&lt;br /&gt;&amp;nbsp;,wmode:&amp;nbsp;'&lt;/span&gt;&lt;span style="color: #0000BB"&gt;transparent&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'&lt;br /&gt;&amp;nbsp;,css:&amp;nbsp;&amp;#91;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;'&lt;/span&gt;&lt;span style="color: #007700"&gt;.&lt;/span&gt;&lt;span style="color: #0000BB"&gt;sIFR&lt;/span&gt;&lt;span style="color: #007700"&gt;-&lt;/span&gt;&lt;span style="color: #0000BB"&gt;root&amp;nbsp;&amp;#123;&amp;nbsp;color&lt;/span&gt;&lt;span style="color: #007700"&gt;:&lt;/span&gt;&lt;span style="color: #FF8000"&gt;#2f3d4a;&amp;nbsp;font-size:23px;&amp;nbsp;background-color:#fff;&amp;nbsp;&amp;#125;'&lt;br /&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'a:link&amp;nbsp;&amp;#123;&amp;nbsp;text-decoration:none;&amp;nbsp;color:#2f3d4a;&amp;nbsp;&amp;#125;'&lt;br /&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'a:visited&amp;nbsp;&amp;#123;&amp;nbsp;text-decoration:none;&amp;nbsp;color:#2f3d4a;&amp;nbsp;&amp;#125;'&lt;br /&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'a:hover&amp;nbsp;&amp;#123;&amp;nbsp;text-decoration:none;&amp;nbsp;color:#105496;&amp;nbsp;&amp;#125;'&lt;br /&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'a:active&amp;nbsp;&amp;#123;&amp;nbsp;text-decoration:none;&amp;nbsp;color:#ffa000;&amp;nbsp;&amp;#125;'&lt;br /&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #DD0000"&gt;'.span&amp;nbsp;&amp;#123;&amp;nbsp;color:#969086;&amp;nbsp;&amp;#125;'&lt;br /&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#93;&lt;br /&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;ratios&lt;/span&gt;&lt;span style="color: #007700"&gt;:&amp;nbsp;&lt;/span&gt;&lt;span style="color: #0000BB"&gt;&amp;#91;8&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.41&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;10&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.33&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;14&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.31&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;16&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.26&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;20&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.27&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;24&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.26&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;25&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.24&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;26&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.25&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;35&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.24&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;46&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.23&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;67&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.22&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;70&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.21&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;71&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.22&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;75&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.21&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;76&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.22&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;80&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.21&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;81&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.22&lt;/span&gt;&lt;span style="color: #007700"&gt;,&lt;/span&gt;&lt;span style="color: #0000BB"&gt;1.21&amp;#93;&lt;br /&gt;&amp;#125;&lt;/span&gt;&lt;span style="color: #007700"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/div&gt;&lt;p&gt;
In this case the &lt;em&gt;&amp;#8216;.span { color:#969086; }&amp;#8217;&lt;/em&gt; styles all the elements with a class of &amp;#8216;span inside the h3 element. I found out that I have to specify a class, just selecting a span element like this &lt;em&gt;&amp;#8216;span { color:#969086; }&amp;#8217;&lt;/em&gt; does &lt;em&gt;not&lt;/em&gt; work. (Effectively I use a span element with a class of span. Talk about doubling up here...)
&lt;/p&gt;
&lt;h4&gt;To be continued&lt;/h4&gt;
&lt;p&gt;
Next time (the last part of this series), I will have a look at the coding process for this site. Expression Engine goodies all inclusive.
&lt;br /&gt;

&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=HOAjtLA"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=HOAjtLA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=cYjTaTa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=cYjTaTa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=gjvPera"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=gjvPera" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=YsTlt7a"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=YsTlt7a" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/177976877" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fsquawk_redesign_part_3_type_choices_and_sifr%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/squawk_redesign_part_3_type_choices_and_sifr/</feedburner:origLink></entry>

    <entry>
      <title>The LZ Avocado</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/177976878/" />
      <id>tag:squawkdesign.com,2007:weblog/2.101</id>
      <published>2007-10-22T16:42:01Z</published>
      <updated>2008-01-26T21:35:48Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="From my sketchbook" scheme="http://www.squawkdesign.com/site/C47/" label="From my sketchbook" />
      <category term="Illustration &amp;amp; Animation" scheme="http://www.squawkdesign.com/site/C46/" label="Illustration &amp;amp; Animation" />
      <category term="Others" scheme="http://www.squawkdesign.com/site/C43/" label="Others" />
      <content type="html">
        &lt;p&gt;This is one of the more random doodles resulting from the redesign of this site. I have gone slightly astray, but then again&amp;#8230; lets call it postmodernist content.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/lz_avocado.jpg" border="0" alt="image" name="image" width="538" height="328" /&gt;
&lt;br /&gt;
&lt;small&gt;The LZ Avocado: A discontinued thought from my notebook.&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
Zeppelins have never been known as a very secure way of travelling. Supposedly, they were very comfortable, though.
&lt;/p&gt;
&lt;p&gt;
But what is comfort to anyone, when you know that there is a couple hundred cubic meters of flammable hydrogen above your head? Just like so many things today, comfort seems to come at a prize! A high one in this case.
&lt;/p&gt;
&lt;p&gt;
Imagine all the people, ehm, I mean imagine all the passengers frantically clamping on their armrests when the flight attendant asks whether they would like to buy some cigarettes, with a free lighter. Duty-free, of course!
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=Hdvoa0A"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=Hdvoa0A" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=rh5GNfa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=rh5GNfa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=5RM95xa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=5RM95xa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=9uxA6Ya"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=9uxA6Ya" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/177976878" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fthe_lz_avocado%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/the_lz_avocado/</feedburner:origLink></entry>

    <entry>
      <title>Squawk redesign part 2: Colour palette &amp;amp; illustration</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/177976879/" />
      <id>tag:squawkdesign.com,2007:weblog/2.98</id>
      <published>2007-10-19T20:33:00Z</published>
      <updated>2007-10-26T10:51:15Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Current Projects" scheme="http://www.squawkdesign.com/site/C13/" label="Current Projects" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;p&gt;Welcome to part 2 of the write-up on the new site. In this weblog entry I will focus on the illustrations that I used on this site.
&lt;/p&gt;
&lt;p&gt;
As I mentioned in &lt;a href="http://www.squawkdesign.com/weblog/comments/squawk_redesign_part_1_requirements_amp_establishing_the_grid/" title="Squawk redesign part 1 - Requirements &amp;amp; establishing the grid"&gt;an earlier weblog post about the requirements for this redesign&lt;/a&gt; I wanted to add a personal attachment to this site. By personal attachment I do not only mean something by which a visitor will remember this site, but also something that allows me to emphasise with it.
&lt;/p&gt;
&lt;p&gt;
In the beginning of this redesign process I had a play with words revolving around the existing &amp;#8216;Squawk&amp;#8217;. In fact I did not change the concept of Squawk being onomatopoetic for the noise that a surprised chicken would make when it discovers a juicy worm (Excellent content and design), yet the brainstorming/sketching allowed me to outline the new style of this site.
&lt;/p&gt;
&lt;h4&gt;The colour palette&lt;/h4&gt;
&lt;p&gt;
I started experimenting with a rural image in the background of the page, partially relating back the henhouse/squawk idea, yet this greatly decreased readability: No font renders great on crops.
&lt;br /&gt;
What stuck was the beige/blue combination. The dark-blue heading just looked great on a light Toscana sky and grey text was very readable on the beige that the image faded out to. The basic colour palette was determined.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/part_2_colour_palette.jpg" border="0" alt="image" name="image" width="538" height="89" /&gt;
&lt;br /&gt;
&lt;small&gt;The colour palette for the redesign of this site.&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
Resulting from the many doodles that I did during the brainstorming for this site, a style was born. Below is the first menu that I drew in a small sketchbook. I don&amp;#8217;t know where the boards, pipes and gloves came from, but after all this was only one of the first ideas.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/part_2_menu_idea.jpg" border="0" alt="image" name="image" width="538" height="263" /&gt;
&lt;br /&gt;
&lt;small&gt;One of the first ideas for the menu. The Contact &amp;amp; About sections were later combined and the links themselves transformed into text-only-links&lt;/small&gt;
&lt;/p&gt;
&lt;h4&gt;The typewriter&lt;/h4&gt;
&lt;p&gt;
Through some more doodling, the typewriter idea, as means of representing the weblog section of the site, was born. One of my old English teachers used to brag that he had the exact same model of typewriter as Ernest Hemingway, and I remember being rather fond of that particular typewriter as well. 
&lt;/p&gt;
&lt;p&gt;
If you think that this is a little odd, take a good look at the next typewriter that you find: Unlike computers they have style and are also much more productive, since you do not get annoyed by emails, update notifications and God knows what.
&lt;br /&gt;
&lt;em&gt;(Check out &lt;a href="http://hogbaysoftware.com/products/writeroom" title="WriteRoom"&gt;WriteRoom&lt;/a&gt;, a very productive writing environment for the Mac.)&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/part_2_typewriter.jpg" border="0" alt="image" name="image" width="538" height="355" /&gt;
&lt;br /&gt;
&lt;small&gt;The typewriter that identifies the weblog section.&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
The typewriter was later joined by the pencil for the portfolio section of the site.
&lt;/p&gt;
&lt;h4&gt;The doodlebush&lt;/h4&gt;
&lt;p&gt;
On the double page that I drew the typewriter on there were also a great amount of random doodles: leaves, arrows, flowers, gloves and umbrellas. 
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/part_2_flower_doodles.jpg" border="0" alt="image" name="image" width="538" height="299" /&gt;
&lt;br /&gt;
&lt;img src="http://www.squawkdesign.com/img/uploads/main/part_2_more_doodles.jpg" border="0" alt="image" name="image" width="538" height="250" /&gt;
&lt;br /&gt;
&lt;small&gt;Two pages from my notebook that later formed the doodlebush. (There were many more, though.)&lt;/small&gt;
&lt;/p&gt;
&lt;p&gt;
While the glove hasn&amp;#8217;t made it to the final layout due to some negative connotations, all the other elements were mixed in Photoshop to create what I call the doodlebush.
&lt;/p&gt;
&lt;p&gt;
This rather disorderly style is something that you seem to find in quite a bit of my work, and I decided that it was something that could identify me on my website.
&lt;br /&gt;
By &amp;#8216;my work&amp;#8217; I obviously do not mean commercial work as not many people would be thrilled to have sketchy lines on their site that is trying to &amp;#8216;sell a professional product&amp;#8217;. Rather I am referring to some of my fine art based work and more importantly my sketchbooks. (In the future I might post some examples from these...)
&lt;/p&gt;
&lt;p&gt;
For those interested on how I created the images that I used in Photoshop: A healthy supply of fine-liners and lots of doodling is all you need. 
&lt;/p&gt;
&lt;h4&gt;To be continued&lt;/h4&gt;
&lt;p&gt;
In the next instalment of how the redesign of this site developed, I will focus on font choices and Typography. See you then&amp;#8230;
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=4rGBNeA"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=4rGBNeA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=T17Otta"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=T17Otta" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=CTINxVa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=CTINxVa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=QRqmKYa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=QRqmKYa" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/177976879" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fsquawk_redesign_part_2_colour_palette_illustration%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/squawk_redesign_part_2_colour_palette_illustration/</feedburner:origLink></entry>

    <entry>
      <title>Should you aim to develop flawless web-projects?</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/183729680/" />
      <id>tag:squawkdesign.com,2007:weblog/2.95</id>
      <published>2007-10-17T15:04:01Z</published>
      <updated>2007-11-12T15:31:14Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Criticism &amp;amp; Discussion" scheme="http://www.squawkdesign.com/site/C38/" label="Criticism &amp;amp; Discussion" />
      <category term="HTML, Scripting &amp;amp; CSS" scheme="http://www.squawkdesign.com/site/C37/" label="HTML, Scripting &amp;amp; CSS" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;p&gt;Browser discrepancies are normal. You have to accept them if you are developing for the web.
&lt;br /&gt;
Of course, there are ways to circumnavigate these &amp;#8216;bugs&amp;#8217; as some web-designers and developers like to call them, yet it is a labour intensive process that sometimes is rooted more in gut-feeling and common sense than logical analysis.
&lt;/p&gt;
&lt;p&gt;
Therefore, I dare to ask whether web-developers should aim to hand off flawless products to their clients? Please note that I am not suggesting that you create faulty code that does not validate, but rather I am questioning the almost holy ritual that some developers seem to run through for every project in order to make their site work perfectly in Internet Explorer 4.
&lt;/p&gt;
&lt;p&gt;
Of course, you should always aim to keep the basic functionality of a site, yet small browser differences usually take more time to resolve than what they are really worth.
&lt;/p&gt;
&lt;p&gt;
In fact, it is impossible to create a website that renders and functions exactly the same in all browsers. So rather than trying to achieve this golden goal, web-developers should embrace browser differences and only create suitable fall-back options.
&lt;/p&gt;
&lt;p&gt;
An important aspect of achieving this is the separation of content, style and scripting, as well as the use of semantic code.
&lt;br /&gt;
I will not reiterate the almost unlimited sources on how to achieve this; I want to ask whether web-developers should go even further and stop trying to provide full functionality to older browsers? 
&lt;/p&gt;
&lt;p&gt;
Not only could we save time and money, but over time users might actually be re-educated to use new browsers.
&lt;/p&gt;
&lt;p&gt;
How far can we go in only creating a box, within which a site is freely able to transform across browsers? There is a fine line between a compatible, well formed site and a fanatic developer who is wasting his clients money.
&lt;br /&gt;
Where do you place that line?
&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=fODIgLB"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=fODIgLB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=cPRLlwb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=cPRLlwb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=C5nhaIb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=C5nhaIb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=FAfu2Zb"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=FAfu2Zb" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/183729680" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fshould_you_aim_to_develop_flawless_web_projects%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/should_you_aim_to_develop_flawless_web_projects/</feedburner:origLink></entry>

    <entry>
      <title>Squawk redesign part 1 - Requirements &amp;amp; establishing the grid</title>
      <link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/squawk/weblog/~3/177976881/" />
      <id>tag:squawkdesign.com,2007:weblog/2.93</id>
      <published>2007-10-15T23:06:00Z</published>
      <updated>2007-10-30T18:36:40Z</updated>
      <author>
            <name>Dominik Lenk</name>
            <email>info@squawkdesign.com</email>
                  </author>

      <category term="Current Projects" scheme="http://www.squawkdesign.com/site/C13/" label="Current Projects" />
      <category term="Interweb" scheme="http://www.squawkdesign.com/site/C12/" label="Interweb" />
      <content type="html">
        &lt;div id="GridLayout"&gt;
    &lt;div id="GridLayout-params"&gt;
        {
            column_width:75,
            column_count:12,
            subcolumn_count:1,
            column_gutter:3,
            align:'left'
        }
    &lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;Just like I promised I will outline the steps that I took to redesign my own site. (If you are reading this in a RSS reader you are missing out.)&lt;br /&gt;Firstly I will describe what requirements I had for the new design and how I used these to develop its grid and general layout.&lt;/p&gt;
&lt;p&gt;The previous version of this site used a 14 column grid layout.&lt;br /&gt;8 columns were used by the main content, while two sidebars filled up 3 columns each. &lt;/p&gt;
&lt;p&gt;&lt;img src="http://www.squawkdesign.com/img/uploads/main/squawk_v1_banner.jpg" border="0" alt="image" name="image" width="538" height="286" /&gt;&lt;small&gt;Version 1 of squawkdesign.com&lt;/small&gt;&lt;/p&gt;
&lt;p&gt;The advantage of this was that there was more room for sidebar content, such as 'Recent Weblog Posts', 'Recent Comments' or my 'Sidenotes'&lt;br /&gt;
Unfortunately, the relatively high number of columns meant that content was squashed, decreasing readability.&lt;/p&gt;
&lt;p&gt;As many of you will not actually have seen the previous design; I dug up an html version: &lt;a href="/img/uploads/main/squawk_v1/index.html"&gt;Click here to check out v1 of Squawk.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Something else that bothered me about the old version of Squawk was the lack of colour and the relatively high loading time for the background image.&lt;/p&gt;
&lt;p&gt;But most importantly, I was not able to identify with the design: The grunge splatter image in the background looked nice, but it did not tell visitors anything about me. (The initial idea was dirt in a henhouse, but this was far from obvious.)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;A small note in between:&lt;/strong&gt; Just because I redesigned this site, this does not mean that the grunge images that have been used in the old design are no longer available. The &lt;a href="http://www.squawkdesign.com/weblog/comments/splatter_splatter_drop_drop/" title="original ink splatter images can still be found here"&gt;original ink splatter images can still be found here&lt;/a&gt;, while the corresponding &lt;a href="http://www.squawkdesign.com/weblog/comments/photoshop_ink_splatter_brushes/" title="Photoshop ink splatter brushes"&gt;Photoshop ink splatter brushes&lt;/a&gt; are referenced here.&lt;/em&gt;
&lt;/p&gt;
&lt;h4&gt;Requirements for the new site&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Distinct use of colour. Move away from the black&amp;amp;white&lt;/li&gt;
&lt;li&gt;Wider text in the sidebars&lt;/li&gt;
&lt;li&gt;Better readability&lt;/li&gt;
&lt;li&gt;Fast loading times&lt;/li&gt;
&lt;li&gt;A personal attachment to the site&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Additionally, I also decided to completely redesign the portfolio and the contact section of this site.
&lt;/p&gt;
&lt;p&gt;I tried to realign my grid for this website, in order to accommodate for most of the above requirements.
&lt;/p&gt;
&lt;h4&gt;Grid development&lt;/h4&gt;
&lt;p&gt;I started my grid development, by listing all the elements that would go into the different sections of this site. After having completed an extensive list I embarked on the process of making it shorter: Which elements do not really serve any purpose? Do I need this on that page? Yes? No? Let's cross it out...
&lt;/p&gt;
&lt;p&gt;Using my list of definite page elements, I outline my grid by folding a sheet of A4 paper. This allowed me to quickly test different grid combinations by drawing on my page elements using a permanent marker.
&lt;/p&gt;
&lt;h4&gt;Grid release candidate&lt;/h4&gt;
&lt;p&gt;In the end I settled for a 12 column grid. It is divisible by both 2,3,4 and 6 giving me wide range of possible page layouts. As I wanted to make the text in the sidebar wider, I decided to move from using two sidebars to only one. As I already killed quite a few page elements, this could easily be done.
&lt;/p&gt;
&lt;p&gt;If you want to see how the new grid works with the new design, press &lt;strong&gt;CTRL+SHIFT+G&lt;/strong&gt;, or if you are using Firefox on Windows, &lt;strong&gt;CTRL+ALT+G&lt;/strong&gt; to toggle the grid on or off in the background. This works using the the &lt;a href="http://gridlayouts.com/" title="Grid Layout JS"&gt;Grid Layout JS&lt;/a&gt; script developed by Teevio.&lt;br /&gt;&lt;em&gt;You cannot actually use the site while the grid is visible, so if you want to press a link, toggle the grid off again using the same keyboard shortcut&lt;/em&gt;
&lt;/p&gt;
&lt;h4&gt;To be continued&lt;/h4&gt;
&lt;p&gt;So much about my initial requirements for this redesign and its grid.&lt;br /&gt;
In the next weblog post I will start talking about how I made the choice about the illustration style that is supposed to add 'personal attachment' and how these illustrations were created.&lt;/p&gt;
      &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=rUOZBfA"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=rUOZBfA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=bGkkGoa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=bGkkGoa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=6D2HvVa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=6D2HvVa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/squawk/weblog?a=tQJyZRa"&gt;&lt;img src="http://feeds.feedburner.com/~f/squawk/weblog?i=tQJyZRa" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/squawk/weblog/~4/177976881" height="1" width="1"/&gt;</content>
    <feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetItemData?uri=squawk/weblog&amp;itemurl=http%3A%2F%2Fwww.squawkdesign.com%2Fweblog%2Fcomments%2Fsquawk_redesign_part_1_requirements_amp_establishing_the_grid%2F</feedburner:awareness><feedburner:origLink>http://www.squawkdesign.com/weblog/comments/squawk_redesign_part_1_requirements_amp_establishing_the_grid/</feedburner:origLink></entry>


<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetFeedData?uri=squawk/weblog</feedburner:awareness></feed>
