Our public face is the website (http://www.telemetri.org) where we have a functional single page web application that allow users to search/browse and then view time series via a simple chart.
The charts are single series X/Y charts where we plot a value (Y-axis) over time (X-axis).
For example, the price of stock/weather/GDP/Crime rates vs Time and we can display several types of basic charts but only ever 1 series on a chart for this site.
Once the user finds data on interest one of several things can happen the most common of which will be to download the data as a CSV (for Excel) or application specific format for further use. But other options are posting to social media, e-mailing etc..
The work flow is very similar to most e-commerce sites.
1) Search for something (e.g. New York City Weather)
2) Browse the results
a) results could be available from several publishers (e.g. National Weather Service, UK Met Office)
b) within each publisher there could be groupings of data containers similar to Amazon's departments and categories (e.g. departments, category = North America : United States : New York and the item would be New York City) that help to organize the data
c) each data container may have one or more time series (Temp, Rainfall, Visibility, etc..). These may also be broken in to categories.
3) Click on a time series to see a chart
4) Download time series data or post to social media,etc..(this is currently disabled)
5) Users may continue on to 1, 2 or 3. We want to allow multiple charts or at least a quick way of moving between them. But there is no requirement or desire to have more than one series on a chart
We have a very small database on the site at the moment but the search results will return the top 1000 publishers
2a) For each publisher, we need space to provide a short description of the publisher as well as a link to the publisher's web site.
We link to the publisher at the moment by clicking on the blue background on the publisher name
2b) In native applications this is a tree structure and can be though of as a hierarchy of folders that organize can be use to organize a file helping to give it context
Our native applications are similar to iTunes and the categories are like music genres. The data containers are like albums and the time series are songs.
What we want
As we begin to release software/data to public we want to replace our current site which is functional but not up to current standards of design.
We'd like to approach Apple/Google levels of simplicity and tablet friendly functionality (USA Today is a good example).
- Mobile first design (tablet, but not phone)
- Tablet/ touch friendly UI elements
We don't have advertising or any other function so clean, simple and obvious is the goal.
Everything can be changed but:
- the chart itself (enclosed in a rounded rectangle) is something our system generates and is not part of the design brief.
- The landing page should leave a space for a carousel to display our products. This carousel will disappear on the first search (as it does now).
- the site should leave placeholders for the chart and the size is fixed.
- Use Atlassian style guidelines: https://developer.atlassian.com/dis…IVES/Style
- We're using Confluence for documentation so we'd like to be consistent with the look/feel
- We need to keep the blog/wiki/contact links but they can moved and formatted as needed. - The result should be white label friendly (for private clients) as we'll use it on several sites (public and private).
- Major browser support (IE/Chrome/Safari/Firefox/Opera) but only recent versions (last 2 years).
- We need to show a "Donate" button in a prominent but not annoying location
- A discrete but visible icon/link we can use to provide a "Help, How to Use" this service page.
- contest winner should be able to supply us with the graphics that are needed for the site in vector source format (e.g. Adobe Illustrator) as well as CSS and demo pages (these can be static).
- demo pages are so we can compare on different browsers/tablets
- if you can build the fully functional page we'd be happy to consider a 1-to-1 project following this contest