The Denver International Airport truly flies high with outstanding features implemented on their website, flydenver.com. The site had already been migrated to Drupal 7 by the time I became involved. However, there was still much to be improved upon, particularly with the mapping, as well as solving challenges to sync updated information into the site via API's. The following slides show some of the fulfillment I executed when I took over the development role to add and enhance features on this Drupal site.

Category
Migrated Sites
Travel
This screenshot shows the home page of the Denver International Airport with focus on providing same access to travel info both on top menu and bottom blocks, recognizing that individuals think to browse sites in different ways. The site provides all travel info from flights to restaurants/shops to security to parking and more. ***The site even provides a feature for users to privately enter their parking space number to have reference - for when they return!
An essential purpose of flydenver.com is to provide mapping of the large airport for travellers to easily get where they need to go. In this screenshot, the map's toolbar (upper left) provides a general search box and categories for users to hone in on what they're looking for. At bottom of map, a zoom tool allows perspective. At mobile device view, the toolbar disappears replacing a tip for users to tap and zoom.
When the user chooses their focus from the map's toolbar, the info within it contextually changes to narrow in on the relevant details. In this example, with user having clicked on the flight category of the toolbar, a scrollable list appears, ordered by soonest to latest departing flights, along with a search box - specific to flights.
This screenshot shows example of a user having selected the restaurant category from the map's toolbar and further having selected a specific restaurant. In this context, the restaurant photo and description is given along with a menu link and directions to get there. Also the map zooms into a more detailed view of the restaurant's location. Other restaurant options in the area are numerically listed to the right.
This screenshot shows the expected wait times going through security lines at DIA. On the backend, wait times are calculated via expected algorythm. However, due to occasional unexpected events, DIA staff identified a need for superintendents to override time estimates as necessary from the website itself. If superintendent doesn't update again, wait times are reset to the algorithm (via API calls, outside of the Drupal website) after 30 minutes.
This example shows similar custom API work (noted in previous slide) I engineered for the parking information of the site. The open/closed status of each lot, along with travel times to and from airport, are synced by API - though can be manually updated by staff if needed.
This screenshot is from DIA'S subdomain: jobs.flydenver.com. It's a separate Drupal instance (website) designed for admin's ability to schedule dates to publish/unpublish new jobs at DIA. It's underlying structure is based on a Drupal view where user can search on terms, as well as browse by company and/or job category.
In this example, the user has selected the US Government jobs category. Some jobs, such as in this category, are automatically fed into the jobs site (without need for admin to manually enter). I created this feed and package to post relevant jobs from API calls to the publicly available USAJOBS API (www.usajobs.gov).