How ParkingMapper Group started their web page design journey
ParkingMapper -- we provide innovative technology solutions to regional and local transportation problems by using Web 2.0 and spatial technology. We generate maps on the fly of parking availability, bus locations, bicycle spots, and cabs. You can remotely hail a cab, and find the bus using our mobile app or texting our short code. Buy or sell your parking spot for profit. Or get a bike at one of our kiosks.
Tell us a bit about who you are and the people you reach
Our users are anyone using regional or local transportation, whether by parking, taking cabs, or using bike-share in cities or taking a local bus in the city or the country. Our focus target is young adults, typically 18 - 35, who are using local transportation services but are also more technologically savvy than older age groups using the same services. We don't want to exclude anyone, though!
Our site contains two sides -- corporate pages describing our core business to investors and clients, and the user interface for the general user base. There should be a clear delination between the two, with the user interface featured prominantly but with the corporate features clearly visible as well.
Our products involve displaying a lot of information on a map. We need to make good use of screen real estate so that the maps display as much data as possible. I'm not at all opposed to understated margins to clearly separate information, but I don't want to lose a large portion of the page to wide, artistic margins.
We're looking for a layout that, when appropriate, can be applied to the following scenarios:
1. A home page / brand landing page. This layout will be used for pages that users will hit first upon visiting http://www.parkingmapper.com or our sub-brand sites, BusMapper, BicycleMapper, and CabMapper. This will also be used as a landing for our client administration interface.
2. A map page. This layout will be used whenever a map component will be displayed on the page, and it must include a sidebar that allows the user to select options to customize the map.
3. A content page. This layout will be used whenever we want to display simple content without a map.