Web Design and Build

Website design – lessons learned Last updated:29 October 2010

I’ve just finished managing a web design project and was reflecting on lessons learned. Three big ones for me:

  • On this project we worked with an external design agency to develop the information architecture, user personas and user journeys. I was rather sceptical about this approach in this case as some work had already been done, but am now a convert to the cause. This work actually made a critical difference between a website that would have been just OK and one that’s really good.
  • We used a lot of mockups and clickable wireframes, and they really served to bring the project to life, and instil confidence in our project stakeholders. Even more true on a web project because it’s so visual. One prototype page is worth many Powerpoint slides.
  • As part of the design we did some “quick and dirty” user testing, where we rounded up a few potential users and sat them in front of a working mockup. This was useful for the design, but had the additional effect of adding a huge amount of weight to the design decisions, to the extent that these were almost never questioned subsequently – which I’m pretty sure would have happened without the testing.

Useful lessons for next time.

A glimpse into the future… Last updated:29 October 2010

I’ve been writing a little application over the last week for my wife’s website to do some behind the scenes stuff maintaining a shop inventory. Nothing excessively complicated.

What’s been different however is that since these aren’t pages intended (or even accessible) for public consumption, I’ve been able to write them solely for Firefox3 – and haven’t had to test them in anything else. Consequently, no worries about what IE6 will do to my nice layout. No worries about unsupported css. Very refreshing.

A little window into the future (hopefully) on what web design would be like if all browsers were standards compliant.

The joys of IE6 Last updated:29 October 2010

IE6 logo

Find myself in an interesting situation at the moment – enforced usage of IE6 at work. Good reasons for this of course, one application used in this organisation will only work with IE6. Quite a common situation.

What’s interesting is what doesn’t work in IE6 – including two websites for web design agencies I was looking at last week. One of these actually said that their site didn’t work in IE6 and told me to upgrade my browser (I can’t), and the other one just broke (badly) in IE6. Another different site I viewed on the same day used transparent pngs, which aren’t natively supported by IE6. Update: Found another two web design agencies whose pages break in IE6 this week – and these were New Media Age Top 100 agencies as well.

Although I use IE6 at home, I use it exclusively for testing websites I’ve built to make sure they’re OK, so don’t normally come across so many issues.

Personally, at the moment, much as I’d like to ignore IE6, I don’t think it’s acceptable to do so. Excluding people using IE6 from using your website is equivalent to saying, in UK terms, that it’s unavailable in Scotland and Northern Ireland. Or, in US terms, unavailable to most of the people in California.

Loading a webpage in stages Last updated:29 October 2010

I reworked my homepage this weekend and wanted to display the latest WordPress blog post on it. No problem there. However, the initial response times for my blog are sometimes quite slow, and this then meant that the whole of my homepage was slow to display, because the page was waiting for the blog to respond before displaying anything.

So what I wanted to do was display the home page immediately, and then load the blog post when it’s available. The solution was to use AJAX, which turned out to be very straightforward. More information on AJAX here, but essentially it allows a page to communicate with a server without refreshing the whole page.

First things first – here’s the php code to retrieve the latest post from WordPress as follows (I originally had this on the homepage itself):

<?php require($_SERVER['DOCUMENT_ROOT']."/blog/wp-blog-header.php");
query_posts('showposts=1');
while (have_posts()): the_post();?> 
<h2><a href="<?php the_permalink(); ?>" title="Blog">
Latest blog: <?php the_title(); ?></a></h2>
<?php the_excerpt(); ?>
<?php endwhile;?>

I saved this code separately into a file called latest_post.php (stored in my “includes” folder).

In my homepage file I added some “placeholder” code where I want the blog post to appear. This will be displayed until the data comes back from WordPress:

<div id="latest_post">
<h2>Latest blog: loading...</h2>
</div>

Note the id of latest_post assigned to the div. Then I added the following javascript code to the <head> section of the homepage:

<script type="text/javascript">
window.onload = new Function("loadXMLDoc('/includes/latest_post.php');");
function loadXMLDoc(url)
  {
  if (window.XMLHttpRequest)
  {// code for IE7+, Firefox, Chrome, Opera, Safari
  xmlhttp=new XMLHttpRequest();
  }
  else
  {// code for IE6, IE5
  xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
  }
  xmlhttp.open("GET",url,false);
  xmlhttp.send(null);
  document.getElementById('latest_post').innerHTML=xmlhttp.responseText;
  }
</script>

The function loadXMLDoc retrieves the php file I’ve created above (latest_post.php) and then the last line replaces the text within the element with id “latest_post” with whatever is retrieved. This is standard ajax code which can be used for any purpose. Only the last line is specific to my page.

The code window.onload... calls this function when the page is loaded.

So, when the page is requested the php and html that’s on the page display the page with the placeholder text, but without the blog post, so the page loads nice and quickly. Once the page loads, the javascript is fired which calls the AJAX function to retrieve the blog post, and this loads on the page when it’s available.

This was the first time I’ve used AJAX, and it seemed quite a neat little solution, so I thought I’d post it here. This is the basic solution which could be further enhanced with some error handling.

A song for the frustrated developer Last updated:29 October 2010

Came across this little song this morning. Very funny and very true……if a bit geeky.