Template and view from moxie-js-client
Regrouped social/web links
Merge branch 'master' into poi-detail-links

* master:
  Style input box and pad content-browse for the additional-toggles
  Further styling on the MapLayout
  Style "additional-toggles" for transport options
  Refactored to use variables
  Added some variables for maps.ox styling
  Allow for toggleLocation to be called directly
  Style map-options widgets
  Set "active" class when location is enabled
  Add basic sorting options to search results template
  Added the public transport/driving/cycling button toggles
  Updated maki to a commit with the "car" icon
  Added Maki icons as a submodule
  Removed category titles from "categories" view, not needed for maps.ox
  Styling the results list
  MapBrowse layout styling
  Render ItemView with different context if we have a search term
  Shuffled the HTML in the ItemView template
  Updated wording on the search placeholder text
  Added content-browse-wrapper and moved the browse/location buttons here
Handle case of one or multiple parents
Add event listeners for the additional POI toggles
Added endpoint for geojson searches
Specify additional collections for each toggle
setCollection allows additionalCollections

We listen to events from these collections and show/hide them when
toggled
POICollection handle toggling collection / geojson responses
Added leaflet.markercluster to group icons

 - Used for additional collections (bus, car park, cycle parking)
Add markercluster to require.config
Removed debug logging
Added MarkerClusters to display the additional collections
getIcon function for clustered POIs
Added marker urls/sizes to additional POIs
Refactored the POIs collection to create AdditionalPOICollection

 - To be used for POIs we don't want models for
 - Currently GeoJSON objects
Refactored additionalPOIs config into the config file
Include AdditionalPOICollection
Updated POICollection "fetch" to call geoFetch when appropriate

 - Fixes issue with geoFetch being called for new pages
 - Causes issue where a first page of results may not be geolocated
   however the second could have it toggled on
Call the correct fetch (with the correct arguments)