Ever since the new Coaster Crew website launched in September, I have been writing articles describing my design process and design decisions. The series began with a post about how I learned about both the roller coaster enthusiasts and the “general public” segment of The Coaster Crew’s audience and determined how to best target the site toward the general public while still meeting enthusiasts’ needs. Later posts outlined how several of the pages on the site came to be: the new homepage, the new In the Loop page, the events list, and a page inviting users to participate in the Coaster Crew Network Forums. I also went over a new membership signup flow which is not currently on the live site due to technical limitations.
Today, I’ll discuss how the Coaster Crew Network ties together with a feature that you can see now on CoasterCrew.net.
The Coaster Crew currently owns and operates ten live websites. Their official site has been live in various incarnations and web addresses since 2004. They started operating fansites for amusement parks several years ago when the Kings Dominion Fan Site went under their ownership. (Prior to this, several Kings Dominion fansites had come and gone over the years. Usually, these sites had one or two owners and would be maintained well for several years before the owners no longer had time or no longer had interest in working on the sites.)
They later launched fansites for Busch Gardens Williamsburg and Six Flags America. Most recently, they have added fansites for Cedar Point, Kings Island, Canada’s Wonderland, Dollywood, and Valleyfair. The Coaster Crew Network site originally just served as a gateway to their forums. Earlier this year, I launched a complete, responsive redesign of that site with a focus on tying together all of their fansites and social media channels and providing a consistent look and feel with the other sites I have been redesigning for them.
Selling users on the idea of the fansites as being part of a network is important for the Coaster Crew. The fansites have not always had a consistent way to navigate between them, and it can be hard to remember which fansites are in the network. The staff suggested a network bar in the sites’ header or footer. I decided that since tall footers with site maps are common in designs today, I could merge the network bar into a tall footer.
I sketched five different ideas for the network bar at the beginning of the project. The first was a simple listing of all of the fansites across one row. The second divided the list of sites into four columns. The third put the names of the parks with the fansites. The fourth arranged the sites in columns by the park chains represented by each fansite.
The layout that seemed to scale best arranged the parks by geographic region. It seemed to be the best at handling new sites’ being added to the network bar. If park chains sold a park, we would not need to update the network bar and users would not be wondering if we still had a fansite for that park.
I tested each idea’s strength by creating wireframes for them. The first three ideas seemed to work for a header or a footer, while the last two were definitely for footers. In addition to scalability, the fifth idea also seemed the best for the design since a tall footer on each page would allow for some strong design ideas there. I continued to work on that idea through the prototype and later stages.
In Axure, I initially added bright colors for the network bar before I knew what the background pictures would be. The copyright and footer links were initially very minimal at the bottom of the page.
I took this background picture of El Toro with a point-and-shoot camera. It has remained the desktop background on my old desktop computer for several years. This picture seemed to go very well with the network bar, so it became the background.
I built the network bar locally using Zurb Foundation 4.3. The fansite’s logos fill 100% of their container’s width with auto height. The copyright and map statements were minimal. User testers seemed to receive this layout well, but I thought more could be done with it. It also didn’t have the ribbon yet.
For performance reasons, the live site on mobile doesn’t keep the background in one place. It shows the fansites two to a row instead of four to a row to size the logos ideally for the smaller screen.
The footer now features a panel with the Coaster Crew’s mission statement.
The network bar currently takes almost exactly one screenful for a tablet in landscape orientation.
In portrait mode, most of the blue footer panel can also be seen. Zurb Foundation 4.3 automatically hyphenates words on mobile devices to keep the parks’ names from becoming too wide for their columns.
The desktop layout shows the blue footer panel mostly obscuring the roller coaster hill behind it. It gives clear access to The Coaster Crew’s social media channels under the club’s logo in the footer.
Lastly, here is a preview of how the network bar will look on the redesigned fansites. I did this as an overlay, similar to the In the Loop background, because each fansite has a different color scheme and that will allow each fansite’s personality to translate into its network bar design. This is a prototype and still subject to change as the sites move toward going live.
You can see the Coaster Crew network bar live on any page of the Coaster Crew site. The next and last article in this series will discuss the About page: the best example in this project of my consistently pushing myself toward a better design.
I am a user experience designer specializing in the amusement industry. I work for amusement parks, ride companies, coaster clubs, and any other company or organization affiliated with amusement. If you would like to hire me, please contact me through my website or tweet at @AmusementUX. You can also like my company’s Facebook page or follow me on Twitter.