This content was originally published Kyan’s blog at, but is no longer available at that location. Reproduced here with permission.

Colophon the 2nd

I’ve had some requests for more info on the challenges involved in building the new site; read on for more.

For the most part the design is actually fairly simple. Nice clean fonts and a clear rhythm, but I had strong design direction which always helps when building a new site. I sit back-to-back with the designer on this so I could just turn around and ask questions if I needed clarity.

The carousel

The carousel was interesting to build as the finalised design didn’t come into place until quite late in the project. We originally just had a ‘standard’ site carousel built, but we always knew we wanted to do something more. In the end I sat down with Lee and thrashed out an idea for the animation. He then went off and implemented exactly the design he wanted in Flash, which I then converted to CSS animation. This way of working appeals: I get design direction on the animation and timings as well as the static assets.

The carousel was initially built with standard absolute position & top animation using jQuery, but these turned out to be extremely slow on iPad (a target browser for the launch). Dropping in CSS3 translations fixed that, but obviously didn’t work on older browsers. In the end I found jquery.transform.js that abstracted the interface and made it work on everything. Unfortunately (with a couple of weeks to go) I ran into alpha-transparency glitches and performance issues in IE7 and 8 that meant that turning off the animation in those browsers was the most expedient route to getting the site launched. Together, those are currently running at <3% of total users anyway, so it’s not a huge issue and the site works better for them now regardless.

One interesting (and annoying) bug I ran into on the carousel was jerkiness in Chrome. I use Firefox as my main development browser so didn’t really notice the problem until more in-depth testing. It turned out that the problem arose from me triggering hardware acceleration for iOS using the -webkit-backface-visibility trick. Chrome’s animation was much smoother when that line was removed; Safari on OS X performed about the same with it in or out. In the end I used a media query filter to hide the trigger from desktop Webkits: hopefully browser progress will obviate the need for such workarounds in the future.

Difficult decisions

A design request I didn’t implement in the end was a request for the team carousel to blur the images out towards the edges. After a bit of thinking and research I came up with a way to blur the photos after the animation finishes, but nothing that would blur in realtime as the slide animation happened. I suspect given time I could have done something, but a performant solution in the development time available wasn’t going to happen.

Webfont problems

Regarding the fonts, for the most part they were trivial to implement using The only surprise in that was when we moved all our assets to Amazon S3. We were self-hosting League Gothic and it turns out that Amazon don’t have in place (or let you add) the cross-site request header that Gecko needs for font embedding across domains. Luckily we found that the original font that League was based on (Alternate Gothic #1) was on so we just moved over to that instead.

Fit and finish

What I really feel proud about with this site is not any one part of it, but that there was enough time available to add a really nice level of fit and finish to the whole thing. Even smaller subpages were graced with decent illustrations and I had time to make the interface feel as slick as possible to as many users as possible. This seems to have been borne out with the overwhelmingly positive feedback we’ve had from Twitter and our clients.