
Ticket To Ride Homepage
The Ticket To Ride site was the first major project that I took on as part of InGrid Design. The major component of the previous site was a utility to filter through area vanpools. This was something that the TTR staff wanted to further develop, as well as bring the rest of the site forward insofar as design and functionality. The version that is live as of July 1st, 2010 is Phase 1 of this process. Phase 2 will be coming during 2012 as part of an ongoing 2-year contract that I helped InGrid Design win.
The first stage was of course design, headed up by our Creative Director Katie Walker. I had some input, but the majority of the initial design was handled by her. Down the line, I re-laid out the homepage as well as handled the layout of interior pages based on her original designs.
The tougher part of the development cycle involved the new version of the vanpool finder. As the project was unfolding, TTR was gaining new vans and new routes. By the time the site launched, they were in charge of 60+ vans with at least 20 more on order. This meant a need to increase the ease of use by both the staff to keep up with all the routes as well as making it easier for potential riders to find vanpools.
The first version that I cooked up had Google Maps (using the MX Google Maps module) integrated into the header area where you see the van/cars above the main content. Each page focused on one vanpool and the aforementioned banner had plotted map locations of the pickup and the dropoff point locations. The body area had a description of the vanpool as well as
However, this early version ended up being a bit much to keep on top of. Especially when trying to plot out the pickup/dropoff points and be as accurate as possible, we were running into problems were it was just too much data to keep on top of. The routes shift all the time to account for different riders and changes in drivers, and keeping up with the map locations and other data could have been almost a full time job in and of itself. So we scaled back a bit and went back to basics. What resulted was what you see now on the site – simple selection boxes filtering the origin point and the destination point. When finding the locations that you desire, a table pops up with average pricing, relevant times, and contact information.
To do both ways, some custom php had to be written and some custom database calls. Luckily, an Expression Engine staffer had done something similar for an earlier version of EE, so there was at least a starting point. His code didn’t work for this at all, but at least gave some great insight into what needed to be done. He even took the time to update his scripts for EE2, but we still had to create our own due to our specific needs. In several cases – notably the Louisville and Ft. Knox vanpools, we needed a secondary selection box that wasn’t needed/available for the other options. This necessitated another level of work which looking back wasn’t that big of a deal. And.. what you see now is what you get.
Technology Used: HTML/CSS/Expression Engine/PHP/MySQL/Photoshop CS5/Coda/Flash CS5
EE info: Expression Engine 2, Solspace Freeform, EE Forums, MailChimp Subscribe,