MLB Global Navigation
In an effort to move the entire MLB and club sites to a responsive grid, we needed to first look at creating a responsive global navigation that would work on all devices and would allow us the flexibility to merge with new content sections in the future. This project consisted of building a new a new navigation dropdown, new search and autocomplete, a new login template and new footers.
A Starting Point
To fully understand the process we embarked on, we have to look back at the last updated designs for navigation that were created in 2013. Our approach at the time was to have adaptive headers, one style for desktop and one for mobile devices.
Desktop (Above)
The desktop designs for navigation attempted to separate two types of content items, the game specific information from commerce. In addition, the top masthead on the nav included language links, search, login and register.
Tablet (Above)
The tablet view eliminated the separation of these two content types, game information and commerce and merged them into one list. Additionally, the teams section was called out as a button and any links unable to fit in the list would be added to the overflow menu.
Mobile (Above)
On mobile devices, the teams section moved up to be inline with the MLB.com logo while the overflow menu stayed persistent below.
Defining a new organization
When we looked at these older designs of the navigation, it was clear that there was disorganization between the content and the content structure. This was true especially as we looked through the club navigation which was slightly different in structure from MLB.com. We started by looking all the navigation units for all 30 clubs and MLB.com.
Total Sites
31
Avg Navigation Units
17 units
Avg Character Count
101 characters
Early Designs
In our analysis we learned a lot about how clubs and MLB structured their content and what we could do moving forward to simplify that. It was clear, that we needed to understand how many navigation units we would need to support, how much character space we should account for and what type of information should exist at a desktop and mobile display. Our first pass at designing that new structure can be seen below.
Final Design Concept
After an iterative process of designing, we quickly realized that we needed to have two distant but very connected templates for both the club and mlb.com sites. Two templates were needed because MLB.com and Clubs had very distant branding requirements. MLB.com did not require branding, so we could have navigation links inline with the logo, while Clubs required branding, as well as a dedicated space for skins. To accomplish this for Clubs we had to drop our navigation units below the header above viewports at 990px wide.
Club Branding
The complex branding requirements that we had to design for consisted of showing a branding element (logo) for each club, skins and countdown clocks (only shown above 990px) a sponsorship dedicated space allowing sponsors to brand the homepage, and a team url logo.
We compromised with clubs to showcase all of these branding requirements above 990px where they would have the visual real estate to place these items, but below 990x only the branding logo and url logo would persist. It was important to define this as a requirement so we could have a clean navigation on tablet and mobile devices.
Navigation Dropdowns
The remaining piece of the navigation that we needed to design for was the menu dropdown. We started by looking at the 2013 model for Clubs and MLB.com were we found patterns or breadcrumbs on how current club Marketing Producers were using these dropdowns, specifically how was content organized and what were the business requirements.
A New Dropdown Grid
Desktop Dropdown
The final designs that we landed on for the desktop dropdown was to have a horizontal space above 990px. In this dedicated space we wanted to create a cleaner interface highlighting news and video sections with two content items along with a reorganization of the information architecture.
Tablet Dropdown
On tablet devices we created a sections dropdown which would compile all the navigation units including those that were still persistent in the navigation bar. Additionally, on hover, a fly-out menu appears to allow users to see sub navigations all while staying consistent with the desktop visual language.
Mobile Dropdown
Our mobile approach was to take the tablet dropdown and double the list up to go full width. In each cell of the dropdown we made some distinctions to users regarding navigation. If a navigation link had child elements we included a pipe and an arrow. The left 70% of the cell, if clicked, takes users to the parent page, while the right 30% opens up the sub menu of that category. If there is no arrow added, that indicates there is no sub menu.