<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Produxion &#187; Web</title>
	<atom:link href="http://www.produxion.net/tag/web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.produxion.net</link>
	<description>Design &#124;&#124; Code &#38;&#38; Write</description>
	<lastBuildDate>Thu, 02 Sep 2010 08:32:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>North: website design process</title>
		<link>http://www.produxion.net/2009/10/20/north-website-design-process/</link>
		<comments>http://www.produxion.net/2009/10/20/north-website-design-process/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 19:40:01 +0000</pubDate>
		<dc:creator>Phil Powell</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://www.produxion.net/?p=123</guid>
		<description><![CDATA[I made this a while ago, but due to my slackness in updating the old blog for quite some time, it&#8217;s never made it on here. As part of the North project we&#8217;re developing in partnership with folly I needed to produce a new web presence. It was quite a quick job, as time and (&#8230;)]]></description>
			<content:encoded><![CDATA[<p>I made this a while ago, but due to my slackness in updating the old blog for quite some time, it&#8217;s never made it on here.</p>
<p>As part of the <a href="http://www.meetnorth.com">North</a> project we&#8217;re developing in partnership with <a href="http://www.folly.co.uk">folly</a> I needed to produce a new web presence. It was quite a quick job, as time and resource were at a premium, but I thought it would be fun to do a screen capture of the design process. I&#8217;ve condensed the entire process, which was about 5 hours spread over 3 days, into just under three minutes.</p>
<p>You can watch it below, or <a href="http://vimeo.com/5580891">head over to Vimeo to see it in glorious HD</a>.</p>
<p><object width="500" height="281"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=5580891&amp;server=vimeo.com&amp;show_title=0&amp;show_byline=0&amp;show_portrait=0&amp;color=00adef&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=5580891&amp;server=vimeo.com&amp;show_title=0&amp;show_byline=0&amp;show_portrait=0&amp;color=00adef&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="500" height="281"></embed></object></p>
<p>This was a really quick job, implementing a design which is flexible and which can be developed over time. The foundation is a fairly rigid grid system with a strong emphasis on typographic style. I went through three different iterations before arriving at the final blue/green version. Most of the work was done in Photoshop, with some of the graphical elements sketched in Illustrator.</p>
<p>I really liked the second iteration, with the paper plane sketches, but it just wasn&#8217;t cutting it with the rest of the team. I&#8217;ll shelve that idea for a future project though, as I really like the aesthetic.</p>
<p>I hope this is an interesting little insight into the way I develop concepts when working on a new design. Feel free to let me know what you think, and whether you found it useful/interesting.</p>
<p>If you want to see the finished design in all it&#8217;s HTML markup glory, or just want to know more about North, then <a href="http://www.meetnorth.com">head over to the website</a>.
<div class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fwww.produxion.net%2F2009%2F10%2F20%2Fnorth-website-design-process%2F&amp;via=philpowell&amp;text=North%3A+website+design+process&amp;lang=en&amp;count=horizontal" style="" class="twitter-share-button">Tweet</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.produxion.net/2009/10/20/north-website-design-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Websites &amp; Sausages &#8211; Prologue</title>
		<link>http://www.produxion.net/2009/01/18/websites-sausages-prologue/</link>
		<comments>http://www.produxion.net/2009/01/18/websites-sausages-prologue/#comments</comments>
		<pubDate>Sun, 18 Jan 2009 17:35:39 +0000</pubDate>
		<dc:creator>Phil Powell</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.produxion.net/?p=48</guid>
		<description><![CDATA[I've recently experienced a web design epiphany.

It's funny how you work with stuff for so long, and you become very entrenched in a certain way of doing things.  You follow the trends because that's the consensus.  You ocassionally push the boundaries in small ways, to create distinct designs and user experiences.  But there are certain guidelines you set yourself; basic rules you adhere to.  Many times it's subconscious: you do things a certain way because, well, you've always done things that way, everybody else does them that way, so there's no reason to change.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve recently experienced a web design epiphany.</p>
<p>It&#8217;s funny how you work with stuff for so long, and you become very entrenched in a certain way of doing things.  You follow the trends because that&#8217;s the consensus.  You ocassionally push the boundaries in small ways, to create distinct designs and user experiences.  But there are certain guidelines you set yourself; basic rules you adhere to.  Many times it&#8217;s subconscious: you do things a certain way because, well, you&#8217;ve always done things that way, everybody else does them that way, so there&#8217;s no reason to change.</p>
<p>That, I think, is there very defintion of complacency.  It&#8217;s creative apathy.</p>
<p>I&#8217;ve been fortnate enough to be able to spread a little more creativity around with my web designing in the past 6 months, and I&#8217;ve found myself slowly moving towards a new design aesthetic.  It started when I began to revisit Edward Tufte, and began using grids as a design foundation.  I&#8217;ve very much moved away from designing with pixels, putting things in boxes and placing restrictions on content &#8211; instead I&#8217;ve begun to think a lot more about flexibility, expnadibility and getting a lot deeper in the exploration of the beauty which can be extracted from the content.</p>
<p>What do I mean by that last bit?  Well, I guess it comes down the fact that I&#8217;ve grown to have a much better appreciation of how text, images and other media can really shine as the basis of a design.  Far too much web design (and I&#8217;m wholely guilty of this too) is based on the principle of creating a container which looks beautful and which functions wonderfully, but with less consideration for what is going to be <em>contained</em> therein: the content.</p>
<p>The best analogy I can think of is this: if you have a beautiful painting, you wouldn&#8217;t want to house it in a frame which overwhelms the picture &#8211; you want something which complements the painting and accentuates it&#8217;s beauty.  The painting is more important than the frame.</p>
<p>And so it is with websites.  The usual process for creating a website is to start with the structure, and the design.  Consideration <em>is</em> given to the content which will be contained within it, but it&#8217;s usually hypothetical.  From my experience, website copy is normally the last thing to be written, at the last minute, in a rush and with a &#8220;that&#8217;ll do&#8221; attitude.  In most situations, that&#8217;s the nature of the beast.  But I think that as the web matures, and as we move forward with new design ideologies to fit in with the evolution of people&#8217;s expectations of their online interaction, that is something which will need to change.</p>
<p>And I think that change will manifest itself very much in a move back towards the first days of the World Wide Web: when the value was in the free exchange of information, without bells and whistles; back when there was nothing to consider <em>other than</em> the content; no distractions, no advertising, no over-zealous design, no whizzy graphics &#8211; just pure-and-simple, straight to the point content.</p>
<p>Now, this may sound like I&#8217;m advocating a return to a Neolithic version of the Web &#8211; an age where everything is just boring text and ugly underlined links.  I&#8217;m not at all.  God forbid!  What I&#8217;m advocating is, as web designers, we need to back up the truck a little, and take stock of where we&#8217;ve come from in the relatively short life of the Web.  We need to think a little more philosophically about how we approach the design of information and how that information is applied.  The iPhone has already begun to show us a future where a device dictates how people interact with information, and the design principles which need to be applied to faciliaate that.  The Web has been confined to the computer screen for all these years, but that is all about to change.  And with it, I predict, will come a huge shift in the approach to interactive design.  Don&#8217;t know what, don&#8217;t know when, don&#8217;t know where &#8211; but it&#8217;s coming.</p>
<p>And so, how is this relevant ot my epiphany?  As I mentioned at the start of this post, I&#8217;ve been casually aware of a shift in my design aesthetic.  It wasn&#8217;t until I read <a href="http://www.wilsonminer.com/posts/2008/oct/20/relative-readability/">this post by Wilson Miner</a>, that it suddenly struck home, and I realised where I&#8217;d been heading:</p>
<blockquote><p>After years of wondering why browsers defaulted to 16pt text sizes I’m starting to be convinced that long text really <em>is</em> significantly more readable on screen at precisely that size.</p></blockquote>
<p>In that post, Wilson references <a href="http://informationarchitects.jp/100e2r/">a post by Oliver Reichenstein</a>, in which Oliver introduces the 100% Easy-2-Read Standard.  The main point he makes seems so glaringly obvious: the text size on most web pages is too small.  Wilson provides a brilliant visual example.  As the resolution of our monitors has increased, the size of the fonts used on web pages has gotten smaller and smaller, and through that complacent attitude of &#8220;having always done it that way&#8221;, us web designers haven&#8217;t considered compensating for the change.</p>
<p>Duh.</p>
<p>This was the final peice of the jigsaw which I&#8217;d seemingly been trying to put together in the back of my head.  I have a whole bunch of other unwritten rules which I follow (working with grids, clean document structure, progressive enhancement etc.) and now, this new one has been added to the imaginary list:</p>
<ul>
<li>Use a relevant and readable font.</li>
</ul>
<p>And so, to Websites &amp; Sausages (a phrase blatantly lifted from an episode of The West Wing I was watching recently).  I&#8217;m working on a couple of online projects at the moment which are allowing me almost complete creative control &#8211; mainly because they are in-house projects &#8211; and I thought it would be interesting to take one of them as a kind of case study, and to document the process I go through to bring it to life.  I&#8217;m going to consider my preconceptions along the way, and consider new ideas to refine my process.  I hope that the result will be a vigorous insight into my thought processes, and help me to question some of own habits.</p>
<p>And maybe, along the way, I&#8217;ll cause a small epiphany for someone else.
<div class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fwww.produxion.net%2F2009%2F01%2F18%2Fwebsites-sausages-prologue%2F&amp;via=philpowell&amp;text=Websites+%26+Sausages+-+Prologue&amp;lang=en&amp;count=horizontal" style="" class="twitter-share-button">Tweet</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.produxion.net/2009/01/18/websites-sausages-prologue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Announcement &#8211; Gridlet V0.1</title>
		<link>http://www.produxion.net/2009/01/15/announcement-gridlet-v01/</link>
		<comments>http://www.produxion.net/2009/01/15/announcement-gridlet-v01/#comments</comments>
		<pubDate>Thu, 15 Jan 2009 09:27:47 +0000</pubDate>
		<dc:creator>Phil Powell</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[jQuery]]></category>

		<guid isPermaLink="false">http://www.produxion.net/?p=36</guid>
		<description><![CDATA[I've been using grids in my CSS designs for quite a while now, inspired by frameworks like <a href="http://www.blueprintcss.org/">Blueprint CSS</a>.  Although I don't use Blueprint for production work (using a CSS framework starts to get a bit restrictive, and I prefer to build from scratch, rather than trying to override someone else's default), I do use the methodology in my own CSS to create structured, grid-based layouts, and consistent typography.

One of the clever things that Blueprint introduced was the idea of displaying the grid while you're working - this proves to be an invaluable aid as you try to refine CSS rules.  But I've found that - as good as the theory is - it has a few drawbacks.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been using grids in my CSS designs for quite a while now, inspired by frameworks like <a href="http://www.blueprintcss.org/">Blueprint CSS</a>.  Although I don&#8217;t use Blueprint for production work (using a CSS framework starts to get a bit restrictive, and I prefer to build from scratch, rather than trying to override someone else&#8217;s default), I do use the methodology in my own CSS to create structured, grid-based layouts, and consistent typography.</p>
<p>One of the clever things that Blueprint introduced was the idea of displaying the grid while you&#8217;re working &#8211; this proves to be an invaluable aid as you try to refine CSS rules.  But I&#8217;ve found that &#8211; as good as the theory is &#8211; it has a few drawbacks:</p>
<ol>
<li>Because it uses a background-image CSS property, it overrides any beautiful background design you might have implemented.</li>
<li>Because it uses images, if you change your grid size, you have to generate a new custom image &#8211; a bit of a faff.</li>
<li>You have to tweak your CSS every time you want to turn the grid on or off.</li>
</ol>
<p>Since I work with grids more and more often, I decided to have a stab at coming up with a solution which refines the Blueprint idea, adds a dash of <a href="http://www.jquery.com">jQuery</a> to produce something which is a little more flexible and user-friendly.</p>
<p>What I&#8217;ve come up with is a jQuery plugin called Gridlet.  Instead of using pure CSS, the plugin generates a grid on-the-fly, and it&#8217;s an improvement in the following ways:</p>
<ol>
<li>It doesn&#8217;t use images &#8211; instead it dynamically generates a grid on top of your page, so your design remains intact.</li>
<li>Changing your grid size is as simple as changing a setting &#8211; no need to generate images.</li>
<li>You, er, have to tweak your JS to turn it on or off (this is something I&#8217;m going to work on improving &#8211; it&#8217;s early days).</li>
</ol>
<p>It&#8217;s also worth noting that this first version only produces horizontal grids &#8211; that&#8217;s all I need at the moment  No doubt I&#8217;lla dd vertical grid spacing as and when it&#8217;s needed.  Any comments or suggestions are appreciated.</p>
<p><a href="http://www.produxion.net/wp-content/uploads/2009/01/jquerygridlet-01.js">You can download version 0.1 of Gridlet here</a>.  I&#8217;ve only tested in Safari 3 and Firefox 3 so far.</p>
<p>Implementing it is really easy &#8211; you just do something like this:</p>
<pre>$(document).ready(function() {
  $("body").gridlet();
});</pre>
<p>If you want to override the default grid height or colour, just pass in the settings like this:</p>
<pre>$(document).ready(function() {
  $("body").gridlet({
    height: 18,
    background: "#fcc"
  });
});</pre>
<p>And finally, for your curiosity, here&#8217;s the source code:</p>
<pre>(function($) {
  jQuery.fn.gridlet = function(options) {

    var opts = $.extend({}, $.fn.gridlet.defaults, options);
    var line_position = 0;
    $("&lt;div/&gt;").attr("id", "grid_container").appendTo("body").css({
      position: "absolute",
      top: 0,
      left: 0,
      height: "100px",
      width: "100%",
    })

    while(line_position &lt; $("body").height())
    {
      line_position += opts.height;
      $("&lt;div/&gt;").css({
        position: "absolute",
        top: line_position,
        left: 0,
        height: 1,
        width: "100%",
        background: opts.background
      }).appendTo("div#grid_container")
    }

    return this;

  };

  jQuery.fn.gridlet.defaults = {
    height: 24,
    width: 24,
    background: "#ddf"
  };

})(jQuery);</pre>
<div class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fwww.produxion.net%2F2009%2F01%2F15%2Fannouncement-gridlet-v01%2F&amp;via=philpowell&amp;text=Announcement+-+Gridlet+V0.1&amp;lang=en&amp;count=horizontal" style="" class="twitter-share-button">Tweet</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.produxion.net/2009/01/15/announcement-gridlet-v01/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cadence</title>
		<link>http://www.produxion.net/2008/12/23/29/</link>
		<comments>http://www.produxion.net/2008/12/23/29/#comments</comments>
		<pubDate>Tue, 23 Dec 2008 11:18:31 +0000</pubDate>
		<dc:creator>Phil Powell</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Language]]></category>

		<guid isPermaLink="false">http://www.produxion.net/?p=29</guid>
		<description><![CDATA[<a href="http://www.randsinrepose.com/">Rands</a> has written a <a href="http://www.randsinrepose.com/archives/2008/12/21/a_signature_cadence.html">really interesting post all about cadence</a>, and more specifically how the tone of language used on the Web has a direct impact on our trust.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.randsinrepose.com/">Rands</a> has written a <a href="http://www.randsinrepose.com/archives/2008/12/21/a_signature_cadence.html">really interesting post all about cadence</a>, and more specifically how the tone of language used on the Web has a direct impact on our trust.</p>
<blockquote><p>What does a lie sound like? How do we decide to trust? There’s a reason why you can figure out in an instant whether a mail is spam or not. It’s not a single, measurable thing, but a whole set of small, invisible variables with which you can instantly make a judgment — I do not trust this mail.</p>
<p>You have a complex set of analytical mental muscles that help you make critical snap emotional judgments. Whether it’s a mail, a website, or a person, your brain can instantly look at 12 imperceptible aspects of a thing to determine how you should feel.</p>
<p>Truth, love, or lies, human has a signature cadence.</p></blockquote>
<p>I always place a lot of emphasis on spending time developing the language of a website &#8211; the words used aren&#8217;t incidental: the language and tone should be an integral part of the design.
<div class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fwww.produxion.net%2F2008%2F12%2F23%2F29%2F&amp;via=philpowell&amp;text=Cadence&amp;lang=en&amp;count=horizontal" style="" class="twitter-share-button">Tweet</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.produxion.net/2008/12/23/29/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
