Jukebox 302 was a collaborative team effort in Fall 2015. The idea was designed to allow students to choose the music they would like to listen to during lab hours for this particular class. Jukebox 302 is a server run through a local network that allows guest to load a webpage through their browser and select songs to be added to a queue. This queue then would play through the server.
This collaborative effort stretched beyond our original scope. In the end the main developer had incorporated scripts involving Ruby to assist with the streaming of music. My role in this project followed a more administrative role (recording meetings, documentation, and coordinating calendars), but also included some of the development since some team members became low to non-responsive. My part of the development involved front-end design and implementation. The landing page of the Apache server was given a basic logo, content area, and theme. These elements gave the potential end user a basic description of how to the use the product.
The Google Slides presentation for the project displays some of the graphic elements as well as the features of the product. View Presentation
Behind the Logo Design
The feedback I got from my design mentor mentioned that it look a bit like a tombstone, but I wasn’t sure how to diversify the draft without taking too much from other inspirations. The image on the right incorporated the possible additions to the logo, but was not used outside of the website’s implementation. I argued that the improved logo did not keep the 3D flat design, therefore, it was decided to keep the original draft for the final design [see below].