Challenge Overview
Project Overview:
Welcome to the DocuSign - HTML5 iPad UI Prototype Challenge! The goal of this challenge is to create a HTML5 Prototype application for iPad based on provided storyboards.
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 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.
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 iPad Safari Browser.
Required Pages:
Below are the required pages in Portrait orientation (browser bar hidden)
1. Visitor Sign In Page:
- User opens the application and will see the welcome page (01- Visitor Sign In Page.png).
- When user clicks on “Continue” button he will be redirected to reason of visiting page (02 - Reason for visiting.png).
2. Reason of Visiting Page:
- When user selects his reason of visiting that field will be active as shown (02.b - Reason for visiting Selected.png).
- Also notice a “NEXT” button will appear when the user selects the reason of visiting.
- When user clicks on “NEXT” button he will be redirected to name and title page (03 - Name and title.png).
3. Name & title page:
- When user clicks on “BACK” button he will be redirected back to reason of visiting page.
- When user clicks on “NEXT” button he will be redirected to email page (04 - email.png).
4. Email Page:
- Add error validation to email field.
- When user clicks on “BACK” button he will be redirected back to name and title page.
- When user clicks on “NEXT” button he will be redirected to who are you visiting page (05 - Who you are visiting.png).
5. Who are you visiting Page:
- When user clicks on “BACK” button he will be redirected back to email page.
- When user clicks on “NEXT” button he will be redirected to welcome page (06 - Welcome Screen.png)
6. Welcome Page:
- When user clicks on “SIGN IN” button he will be redirected admin login page (08 - Administration Login Ipad.png).
- When user clicks on “SIGN OUT” button he will be redirected to logout page (07 - Log-out complete.png)
7. Logout Page:
- When user clicks on “BACK TO SIGN IN” button he will be redirected back to visitor sign in page.
8. Administration Login Page:
- This will be a password field.
- When user clicks on “CONTINUE” he will be redirected to admin console menu page (09 - Admin Console Menu.png).
9. Admin console menu Page:
- When user clicks on “Application Settings” button he will be redirected to settings page (11 - settings.png).
- When user clicks on “Log History” button he will be redirected to log history page (12 - Log History.png).
- When user clicks on “Visit Reasons” button he will be redirected to visit reasons page (13 - Edit visit reasons.png)
- When user clicks on “List of Hosts” button he will be redirected to list of hosts page (14 - List of hosts.png)
10. Settings Page:
- Make sure to prototype all the fields in this page.
- “Back to Dashboard” link will take you back to admin console page.
11. Log history Page:
- The table should be functional; means show us how the pagination work, and how the view options work.
- “Back to Dashboard” link will take you back to admin console page.
12. Visit reasons Page:
- The table should be functional; means show us how the pagination work, and how the view options work.
- “Back to Dashboard” link will take you back to admin console page.
13. List of hosts Page:
- The table should be functional; means show us how the pagination work, and how the view options work.
- “Back to Dashboard” link will take you back to admin console page.
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 - Arial.
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
- AngularJS
- Bootstrap 3
Browsers Requirements:
- Safari Browser on iPad.
Documentation Provided:
- Storyboard screens and PSD files: Attached in 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.