Challenge Overview
Welcome to the Google Executive Dashboard Prototype Challenge! In this challenge, we are looking for a clean and easily scalable code base to bring the included designs to life. We hope to see a working prototype with test data to support the clickable actions.
As part of this challenge we need you to document your HTML5/CSS3/JavaScript code (using best practices). We are looking for a clear explanation of the code to allow us the ability to quickly update and integrate with future development. We will allow documentation updates during final fixes (but still required).
Tips for Success: Asking questions early and getting Copilot or PM's feedback is very important for the success of this challenge.
Competition Task Overview:
The main task of this competition is to develop an HTML5 prototype based on the provided storyboard designs. Your prototype must work properly in all the required browsers.
Project Background:
This dashboard will be used by Google executives are looking to understand how Google products are being represented at various retail venues. The information that supports the dashboard is being gathered by Google agents who visit various retail venues and evaluate how they are doing in terms of presenting and supporting Google products in the store.
Screens:
- This application should work on 1280 x 800 screen size for desktop
Key Requirements:
- We would like to ensure the prototype is responsive, please use Bootstrap (latest version) as your css framework
- Browser Compatibility: Current version of Chrome, Firefox and Safari, IE9 and above.
- Ensure your submission is clear of validation errors and warnings (HTML, CSS, JS).
- style.css - use this name for all custom css
- Please use proper id’s and classes in your naming conventions
- For all the charts in the screen, we would like you to use D3 charts..
Page Requirements:
We need below sections in this challenge..
1) Header:
Reference: Executive Summary.png
Create the top header as seen in the prototype
Top Header
Please make all these as dead links..
- Search field
- Share Icon
- Email Icon
- Download Icon
Hamburger Menu
Allows users to navigate the application, make all the below as dead links and clicking on the hamburger icon should toggle this menu view (i.e. hide and show navigation something like this: https://plus.google.com/ - please login to google plus to see how it works)...
- Executive Summary (This will be the active selection)
- Merchandizing
- Sales & Inventory
- Training
- Cases
- Photo Audit
Top Filter Section
Country - drop down menu
- Austria
- Belgium
- Bulgaria
- Croatia
- Cyprus,
- Czech Republic
- Denmark
- Estonia
- Finland
- France
- Germany
- Greece
- Hungary
- Ireland
- Italy
- Latvia
- Lithuania
- Luxembourg
- Malta
- Netherlands
- Poland
- Portugal
- Romania
- Slovakia
- Slovenia
- Spain
- Sweden
- UK
Country Region - drop down menu
- European Union
- Africa
- Middle East
Product - dropdown menu
- Chromecast
- Chromecast Audio
- Chromebook
- Nexus
- Android Wear
- Google Play
Retailer - dropdown menu
- Best Buy
- Fry’s Electronics
- Target
- Walmart
Period - drop down menu
- Date ranges in one week increments for 2015
Refresh button (make this a dead link)
Overall Compliance Card
- % vs 6 week average
- Percentage Number
- Time period selection (Week, Month, 2 Months - please allow them to switch between the tabs but its okay to have the same line graph for all three tabs)
Line graph
- Percentage over date
- Line
- If you rollover a node, a callout displays the percentage number in a blue box
Below that we need these cards...
Location Card
Fixture Card
Demo Card
Messaging Card
OSA Card
Sell-Out Card
- Ku number
- Side bar graph
- - Blue bar with 0 to 100 with “to Quar Target”
- - Ku number in gray part of the bar
- - % vs last week
- - % vs forecast
Line graph
- Number over date
- Line - dummy data
- If you rollover a node, a callout displays the Ku number in a blue box
Inventory Card
- WoS number
- Channel Number
- Warehouse Number
Bar graph
- Number over date
- Channel lower blue bar
- Warehouse upper gray bar
- If you select a bar, a callout displays the channel number + the Wos number in a blue box
Staff Trained Card
- Metric Number (Blue state 0 to 100 - dummy data)
Side bar graph - dummy data
- Blue bar 0 to 100 percent with “to Quar Target”
- Remaining bar in gray
- % vs last week
- % vs 6 week average
Line graph
- Percentage over date
- Line graph
- If you rollover a node, a callout displays the percentage number in a blue box
Modules Card:
- Number (Blue state 0 to 100 - dummy data)
- Side bar graph - Need dummy data
- - Blue bar 0 to 100 percent with “to Quar Target”
- - Remaining bar in gray
- Avg Level - Need dummy data (Red down, Green up)
- Training Spd - Need dummy data (Red down, Green up)
Pie Chart with average in middle
- Five parts - various shades of blue with percentage number in each part
Hours Card:
- Number (Blue state 0 to 450)
- Side bar graph
- - Blue bar 0 to 100 percent with “to Quar Target”
- - Remaining bar in gray
- % vs last week
- % vs 6 week average
- Line graph
- - 0 to 400 over data
- - Line - dummy data
- - If you rollover a node, a callout displays the hours number in a blue box
Specific HTML/CSS/JavaScript Requirements:
HTML/CSS Requirements:
- Your HTML code must be valid HTML5 and follow best practices
- Validate your code - reviewers may accept minor validation errors, but please comment your reason for any validation errors. Use the validators listed in the scorecard
- Use CSS to space out objects, not clear/transparent images (GIFs or PNGs) and use proper structural CSS to layout your page. Only use table tags for tables of data/information and not for page layout.
- No inline CSS styles - all styles must be placed in an external style-sheet.
- Use semantically correct tags - use H tags for headers, etc. Use strong and em tags instead of bold and italic tags.
- Element and Attribute names should be in lowercase and use a "-" or camel naming to separate multiple-word classes (i.e.. "main-content", or "mainContent)
- Label all CSS, JavaScript, or HTML hacks with explanations so others will understand.
- Your code must render properly in all browsers listed in the scorecard in both Mac and PC environments.
JavaScript Requirements:
- All JavaScript used must not have any copyrights to any third party. You are encouraged to use your own scripts, or scripts that are free, publicly available and do not have copyright statements or author recognition requirements anywhere in the code.
- You are allowed to use JQuery (MIT License) for this contest.
Browsers Requirements:
- Internet Explorer 9+ on PC
- Firefox on Mac / PC
- Chrome on Mac / PC
- Safari on Mac
Documentation Provided:
- Storyboard and Source files
Final Submission Guidelines
Submission Deliverables:
- A complete list of deliverables can be viewed in the UI Prototype Competitions Tutorial.
Final Submission:
- For each member, the final submission should be uploaded to the Online Review Tool.