FAST! 72Hrs - Meli Responsive HTML5 iPad Prototype Update

Project Overview:

Welcome to the FAST!! 72Hrs - Meli Responsive HTML5 iPad Prototype Update! The goal of this challenge is to update existing Prototype application for iPad browsers based on the requirements below.

As part of this challenge you will need to document all new HTML5/CSS3/JavaScript code. We need clear explanation of the code to help us figure all the HTML5/CSS3/JavaScript code functions and make it easier for future developers and the client to understand what you have built.

NOTE: This application will use AngularJS Framework (http://angularjs.org, http://docs.angularjs.org/guide) and Bootstrap 3 (http://getbootstrap.com/getting-started). Please follow coding standards and write clean code for AngularJS data binding instead of using plain HTML code.

IMPORTART: As per the project schedules and FAST challenge the review timelines are very close. Reviewers please note the review timelines for further reference.

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 update existing Responsive HTML5 prototype based on the requirements. Your prototype must work properly in iPad browsers.

Required Pages:

Below are the required pages in iPad for only Landscape orientation (Portrait orientation is out of scope for this challenge).

1. Dashboard Page:

• The gauges under 'Command Center' should be image for now, but the texts should not be images.
• The weather gauge was coded in improperly for quick demo purposes - fit it into the layout properly.
• Simulate Chatter actions:  Anywhere Chatter appears in the demo, simulate functionality of being able to comment.
• Have Chatter feed go off bottom of screen to allow for scrolling of Chatter items.

2. Assets Panel:

• Have Asset items continue off bottom of screen and allow for scrolling.
• Change transition animation so it slides in from the left with a slower movement.
• Add transition animation so Assets panel slides to the left when closing AND closes on a swipe left, same style and time sequence as open.

3. Spaces Panel:

• Create Space Detail Pages on same basic design as Asset Details Pages, but with content modified to indicate they’re Spaces.
• Make sure items in list on Spaces Panel click through to Space Details Pages.
• Change transition animation so it slides in from the left with a slower movement.
• Add transition animation so Spaces panel slides to the left when closing AND closes on a swipe left, same style and time sequence as open.

4. Alert Panel:

• Alert items going off bottom of screen view for scrolling.
• Should be a panel similar to the Assets panel, but sliding in from the top and interactions should fit this model (slide open/close, animation indicating it’s moving from the top down).
• Remove Chatter elements and interactions from the Alert items  (Comment, Share, Like).

5. Recommendations:

• Click on "Reject" button, ask for the reject reason (05_07_Recommendation-Details-Reject-Reason) and show rejected status (05_07_Recommendation-Details-Reject) - doesn’t work for all items.
• New: Instead of Reject modal, create version which has a label + select menu and label + text field that extends the size of the Recommendations Detail panel vertically to allow for the confirmation of the Reject status. (Recommendation-Wireframes.zip ->  recommendation-rejected-2.png)
• New: Have the Recommendation Details view that comes up when the left column item is selected be both related to the item (same data/information) and point towards the selected item using the design element.
• New: Add drop-down for reject reason + reject comment. (Recommendation-Wireframes.zip ->  recommendation-rejected-2.png) - Just add example content for now, but allow for at least 3 options.

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 lay out 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.
• Use CSS3 Media Queries to load different styles for each page and don't build different page for different device/layout.
• Images should be properly compressed while still having good visual quality.
• As possible using background color properties, instead of repetition usage of background based image.
• Use sprites technique for the image slicing.

Font Requirements:

Use font - Helvetica.

JavaScript Requirements:

All JavaScript must not have a copyright by a 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. We would like to use following JavaScript libraries:

• jQuery - (We prefer to use AngularJS over jQuery for most of the scenarios - here no penalty on scores)
• AngularJS
• Bootstrap 3

Browsers Requirements:

• Latest Safari Browser on iPad

Documentation Provided:

• Storyboard screens for reference on existing prototype: Storyboard.zip
• Existing Prototype: Prototype.zip

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.