Skip to content

A podcast for those who design, develop and run websites.

Boagworld is the personal website of Paul (the Wurzel) Boag who lives in the heart of rural Dorset. He produces a weekly podcast along with Marcus (pop star) Lillington on all things relating to building and running websites.

Latest shows

138. Freeform
In this week's show the entire boagworld production team answer listener questions.
137. Adobe
In this week's show, Aral Balkan joins us to discuss the release of Adobe CS4 and we discuss how not to get blacklisted by google.
136. Stagnation
In this week's show we talk about overcoming stagnation and Ed Merritt shares a technique to achieve fixed footers without the use of javaScript.
135. Libraries
In this week's show we talk with John Resig on javaScript libraries and address the question what is more important when we release an app: speed or quality?
134. Chrome
In this weeks show we give you advice on choosing the right hosting company, Teifion and John send us a review of dConstruct and of course we discuss the release of Google Chrome, can it topple IE?

or view all shows

Have your say

Leave a message for the show...

Buy my book: The website owners manual. A book for all those involved in designing, developing or running websites on a daily basis.

We are pleased to announce that Friday 10th October will be Boagworld discount day at the Head Conference site. Signup to attend on that day and you will get 20% off!

National Trails web site launched

Published on: July 1, 2005 by Paul Boag

Today sees the launch of the Countryside Agency's flagship website about the network of National Trails. This site is the culmination of month's worth of work by the team at Headscape and I thought I would share with you a few of the highlights and lowlights of the project.

The brief

It was a challenging brief. Take twelve separate trail web sites and unify them under a common brand while still maintaining some sense of individuality. In addition to this, we had to conform to basic levels of accessibility, integrate a content management system that allowed individual trail officers to manage their own sites and come up with a user-friendly way of accessing a large database of accommodation and services.

Problems of interface

For me personally the number one problem to solve was the inconsistent user experience across these multiple trail sites. Users were faced with inconsistent positioning of navigation, different information architectures and conflicting terminology. The only sensible solution was to standardise the interface across all sites. Not only would this solve the user experience problems it would avoid the overwhelming challenge of having to come up with designs for twelve different sites!

Of course, there were two downsides to this approach:

  • This did not solve the briefs demand for a sense of individually on each site
  • It made it harder for the user to instantly tell which trail they were on

The solution was to give each site its own unique colour scheme. By doing this, you could associate very different feels with each site while also giving the user clear visual clues when they moved between different trails.

Web standards, the cornerstone of this project

Once I had decided upon on the approach it became obvious that a web standards approach would rapidly accelerate the development cycle. By separating content from design, I could create one basic layout and use cascading style sheets to change the colour palette of each site.

Web standards brought other benefits too. By separating design from content, we could easily address the need to conform to single 'A' compliancy in regards to accessibility. What is more we could easily supply an alternative printable style that ensured the site only printed certain page elements. I felt this was particularly important, as much of the information on the site would actually be useful to visitors while physically visiting the trail.

Finally, web standards allow us the ability to continually tweak and refine the design through the life cycle of the project and indeed after launch. This enables us to be much more responsive to feedback and work out any user interface bugs that might be spotted along the way.

The lowlights

I have to confess that normally I get to the end of the project like this hating the site because I have just worked with it too long. However, in the case of this site I do not feel that way. Of course that is not to say there aren't a few things that still annoy me about it.

One of the biggest problems we have yet to overcome (although we are looking into some options) is the WYSIWYG editor we are using in the content management system. We seem unable to find an appropriate editor that produces clean code, which does not invalidate the occasional page. What is more there does not seem to be an editor on the market that forces the user into ensuring any content they add is accessible.

Another annoyance for me is that I have been forced to use some table layout on the homepage. This does not in anyway cause problems it is just a matter of principle on my part.

A crowning glory

Despite the odd annoyance listed above and a few hundred little bits and pieces, I am actually incredibly pleased with how this site has turned out. It truly is a crowning glory for Headscape and easily the best piece of work we have done to date (in my opinion). The size and complexity of the site as much as anything else makes it an incredible achievement. I have particular respect for Charlie Allen the project manager on the site who has dealt with 12 individual clients, and been responsible for the population of over 75000 web pages worth of content.

Another feature I particularly like are the flash maps created by Chris Sanderson one of our team of designers. He has come up with a brilliant way of giving people access to a large database of accommodation and services while also giving them a sense of the route the trail takes. This is an excellent example of how flash should be used rather than for nasty animated introduction with no skip button! Of course, in order to maintain accessibility we also had to provide a way of accessing the same information without flash.

Not that this is the end of our work with the National Trails site. There is always more to be done. The site will need tweaking and maintaining. There is site promotion to consider as well as new functionality to consider. Just because a site goes live does not mean it is ever truly finished.

The clients verdict

I couldn't finish this entry without including a quote from an email I have just received from the client at National Trails:

I just wanted to give you my personal thanks for all your hard work on this site. I think its fabulous. I'm so proud of it and of the fact that we made the right choice of contractors to do the work!

Comments

Comments are for the discussion of this post. If you have other questions / comments then post them to the forum or send me an email

  • Post by Paul Boag on July 1, 2005 11:00 AM

    If you have time I would love to hear your impressions of the site. Good or bad, I can take it :)

  • Post by Darren Stephens on July 1, 2005 11:51 AM

    I've just had a quick flick around but I must say I really like it. The look is very clean and the coding and design are really nice. The information is also sensibly chunked and readable. Colour scheming works nicely. And it fares well on the accesibility front.

    From a developer's point of view I'd be interested to know what your criteria for measuring the build quality of your project were. It's research interest of mine and it would be nice to get the thoughts of someone who's just finished working on a (big) real-world project.

  • Post by Paul Boag on July 1, 2005 12:15 PM

    I guess that depends on your definition of build quality. However we ensure that as many pages as possible validate (although sometimes that is not always possible), we check for the WAI compliancy specified in the brief (in this case single A), we test against all major browser back to IE 5 to ensure visual continuity. We check other browsers further back to ensure good degredation. We try and minimise download time. Obviously there are also a whole load of other non technical criteria we judge a site by but those are the main build issues. Is that what you mean?

  • Post by Keith Instone on July 4, 2005 1:26 PM

    Hi - overall, most of the Trail sites are starting to fit in with each other. I did not visit each one, but easily noticed Offa's Dyke which appears more independent than the others. South West Coast and a few others have their own site as well but feel like part of the same system.

    Good job. I see a lot of potential for the next redesign, such as supporting cross-trail tasks for users. Like: "I am a geologist, what would interest me on each of the trails?". I did not see a consistent information architecture yet at that level of detail to even make that possible, but I suspect that is one reason one would even both creating a "national trails" site over all separate ones - your users must have cross-trail goals which that separate sites were not supporting.

    Also, one comment on breadcrumbs since I cannot resist. I noticed on some pages the breacrumb starts with "Nationwide", others start with ""National Trails" and the top of the page sometimes has a "National trails homepage" link. (Both go to the same place.) Keep an eye on that to see if it confuses people.

  • Post by Paul Boag on July 4, 2005 1:41 PM

    Hi Keith,
    thanks so much for your feedback. It means a lot coming from somebody who is obviously a specialist in usability. Just to address a couple of your points. Yes, you are correct that a number of the trails have chosen to "opt-out" of the new site. This is unfortunate and it is my hope this will change over time. I have to say I love your idea of cross trail tasks and I have already passed your comments on to the countryside agency in a hopes of encouraging them to move in that direction. As for breadcrumbs, you are right again. Didn't spot that one. Must have slipped through the net. We will get on to it :)

  • Post by Keith Instone on July 4, 2005 2:18 PM

    Hi Paul - good to hear that cross-trail task support makes sense at first blush. It is these types of things that actually make all of the hard work (of getting the organizations to work together on a more unified site) worthwhile. If your users think of the trails as a "system of trails", then the web site should as well. I have done a lot of "integrating silos" projects - very challenging but very rewarding, especially when you get user feedback on how it helped those geologists discover something new because the website helped them see the trails as a whole.

    And then at some point you have to even think outside your "national borders" - cross-Europe trail integration? Talk about politics then!

    As for the breadcrumb problem, well it may not actually be a problem - just something to watch out for.

    Also, I find it funny (in a geeky IA sense) that your site is about trails and breadcrumbs are about another kind of (navigation) trail.

  • Post by Paul Boag on July 4, 2005 2:29 PM

    Yes that is geeky!

  • Post by song lyrics on September 22, 2005 2:59 PM

    I realise I might be out of topic but check out this collection of best song lyrics http://www.lyricshosting.com

Leave a comment

Additional Information

Supporting boagworld

Boagworld only exists thanks to the kind support of the following people. Check them out.

Speaking and writing

In Association with feed dot informer dot com