Challenge Overview
Project Overview:
Welcome to the Sechi HTML5 Prototype Challenge! The goal of this challenge is to create a Responsive HTML5 Prototype application using jQuery and Bootstrap development frameworks.
As part of this challenge you will need to document all 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 Bootstrap 3 (http://getbootstrap.com/getting-started). Please follow coding standards and write clean code.
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 a Responsive HTML5 prototype based on the provided storyboard designs. Your prototype must work properly in all required browsers - (use HTML5shiv to support IE9 version).
Required Pages:
Below are the required pages for this prototype, make sure all pages are fluid layout using Bootstrap styles.
Note: You will use Storyboard-1st place.zip for all pages, and a mix of Storyboard-1st place.zip & Storyboard-2nd place.zip for Number of Static Pages page.
1. Application Type Page (Step1):
- User opens the application and will see the first step (01_1_flow.png).
- User will select iOS application type by clicking on “Select” button, notice the active state (01_2_flow.png).
- When user selects application type the “Next” link will be active (01_2_flow.png)
- When user clicks on “Next” button he will be redirected to Step2 (01_3_flow.png).
2. Supported Devices Page (Step2):
- When user clicks on “Back” button he will be redirected back to Step1 (01_2_flow.png)
- Notice the active/inactive states for device support and how you can toggle it.
- Notice the select state for supported views.
- When user clicks on “Next” button he will be redirected to Step3 (01_4_flow.png).
3. Number of Static Pages Page (Step3):
- When user clicks on “Back” button he will be redirected back to Step2 (01_3_flow.png)
- In this page we will use this graphic (graphic.png) from Storyboard-2nd place.zip (04_Step 3.png) along side the slider from Storyboard-1st place.zip.
- Notice the slider; user will select number of pages the application will need.
- When user clicks on “Next” button he will be redirected to Step4 (01_5_flow.png).
4. Application Description Page (Step4):
- When user clicks on “Back” button he will be redirected back to Step3 (01_4_flow.png)
- User will be able to describe his application here, use CK Editor.
- User will be able to attach files from his machine.
- Notice the upload process bar (01_6_flow.png) and how it looks like after uploading (01_7_flow.png)
- Clicking on (x) icon next to the uploaded file will remove it.
- When user clicks on “Next” button he will be redirected to Step5 (01_8_flow.png).
5. Application Specification Page (Step5):
- When user clicks on “Back” button he will be redirected back to Step4 (01_7_flow.png)
- When user clicks on (+) icon a new input field will appear.
- Notice the slider to indicate how technically savvy are they.
- When user clicks on “Next” button he will be redirected to Step6 (02_summary.png).
6. Summary Page (Step6):
- When user clicks on “Back” button he will be redirected back to Step5 (01_8_flow.png)
- When user clicks edit icon he will be redirected back to the cross bonding step page to edit it; so if the user clicks on edit icon next to “Supported Devices” he will be redirected back step2.
- When user clicks on “Next” button he will be redirected to Step7 (03_Payment.png).
7. Payment Page (Step7):
- When user clicks on “Back” button he will be redirected back to Step6 (02_summary.png)
- Change “Proceed” to “Submit”
- Add step 7/7 progress indicator at the top like rest of the pages
- When user clicks on “Submit” button he will be redirected to receipt of payment page (receipt of payment.png)
8. Receipt of Payment Page:
- Present the User with a “Thanks for your submission and order”
- It would be something like this (receipt of payment.png)
- Add “Print” button for the user; print button should open the print dialog.
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.
Font Requirements:
- Use font - OpenSans.
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
- Bootstrap 3
Browsers Requirements:
- IE 9+ Browsers on PC - (use HTML5shiv to support IE9 version)
- Latest Safari Browser on MAC and PC
- Latest Chrome Browser on MAC and PC
- Latest Firefox Browser on MAC and PC
Documentation Provided:
- Storyboards screens and PSD files can be found in challenge forums.
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.