The examples of client work I am showing were completed during my time at AKQA. On these projects I served as the lead front end or web developer but the designs were produced by the talented members of the creative department. View the text only version of this page, download my resume, or view it online.
I was contracted by Doug Smith in the Washington, D.C. offices of AKQA to handle the front end development of the Crysis project they had won. I worked from New York with the D.C. based team to translate design PSDs into a functional front end. The client side code I created was made into templates by the Drupal developers in the D.C. office. Once the initial template creation and Drupal configuration was completed I worked directly in the PHP files, editing the template code along with the CSS and JavaScript.
Amanada Schultz, formerly at Droga5, brought me on board for a couple of weeks to clean up the code and fix some critical bugs on a short timeline just before the delivery to Suave of this site. The bulk of the front end work is not mine but I want to include this project because it highlights my ability to come into a project and quickly be productive fixing show stopper bugs on an unfamiliar code base. The majority of the issues I needed to address were problems getting IE6 to render elements correctly and getting the JavaScript components to behave properly.
Diageo was having trouble with an abnormally high dropoff rate at the age validation step prior to gaining access to the site and felt the dropoff was related to the Gateway being in Flash. So they asked AKQA to redesign and rebuild it for them.
Once the creative department had finished creating an updated look in psd format it was handed off to me for top to bottom implementation. One of the more interesting challenges of this was backporting a number of MooTools plugins (which I had previously written) for use with a legacy version which broke plugin compatibility in a bunch of ways. The most enjoyable part of this project was finally getting to add better keyboard support for the MooTools dropdown replacement script I wrote.
AKQA was commissioned to help Motorola rebrand, rearchitect, redesign and rebuild their global website and with the recently launched redesign my front end work is featured prominently on many of the templates/pages.
I created most of the JavaScript classes and components which control the interactions between the user and the site. These elements were created in JavaScript utilizing an object oriented approach in order to facilitate code re-use on subsequent endeavors with Motorola. This project was interesting and exciting in a lot of ways because it pushed me to create lots of flexible UI components many of which replaced standard browser controls without compromising keyboard accessibility.
Some of the pages I am most pleased with are the phones, accessories and the product comparison page. As with anything finished work there are some things I would like to change or tweak but all things considered I believe these turned out well.
The extranet project was another piece of work AKQA was commissioned to do, this time for Benjamin Moore. I'm sure by now this site is live, however as it is private all I can link to is the mock-up we delivered to them so they could integrate it with their back-end architecture. I was not as heavily involved in the coding of this project as I was in the Motorola or Smirnoff projects. I was, however, responsible for overseeing the front-end development as well as the bulk of the JavaScript work.
I enjoyed this project because it required me to really dive into jQuery whereas much of my other work utilizes the MooTools framework. I'm the type of person who wants to grok a framework or tool and it's best practices before using it heavily and this design and interaction required heavy scripting and the client required jQuery.
This is a project I've been working on off and on since mid-June 2008. It started a as a collection of relatively poorly implemented scripts and has evolved into a number of plugins I use on a fairly regular basis for client work. All of the code is released under the MIT license (same as the MooTools source). Currently the documentation and demos are lackluster (or wholly absent) but I've been much more focused on the implementation than on trying to wrap them up for 'release' but with the changes to the way MooTools More is being handled I'm a little more focused on updating the docs and demos.
One of my favorite plugins in this collection is Form.Dropdown which is a stylized replacement for a select dropdown. I like this plugin because as it has evolved I've been able to include a considerable amount of keyboard accessibility features making it, in my biased opinion, as or more (in the case of Internet Explorer) usable than the default browser selects.
The inclusion of this project is admittedly odd because it is no where near what I would call complete. However it is one of the few projects of mine which has gotten kudos from another developer. I used this vim plugin as my "I should learn Ruby" project. Prior to working on this I was relatively unfamiliar with Ruby's syntax because I had done nearly no development in the langage.
I originally started work on this after discovering TextMate's blogging plugin which I found to be useful for interacting with Wordpress but I was (and will continue to be) using MacVim as my primary editor so I wanted to be able to replicate the functionality of the TextMate blogging plugin in Vim. I really enjoyed digging into the Ruby language a bit with this project and it served to whet my appetite for more functional languages.