Challenge Overview
Project Overview:
Welcome to the FAST!! 96Hrs - eBay Intranet Search HTML5 UI Prototype! The goal of this challenge is to create an auto-complete search HTML5 Prototype using AngularJS and Bootstrap development frameworks.The prototype should be Responsive HTML5 to support both desktop and mobile browsers using Bootstrap.
NOTE: This application will use AngularJS Framework (http://angularjs.org, http://docs.angularjs.org/guide), AngularJS Filter (https://docs.angularjs.org/api/ng/filter/filter) 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 code up the search interactions for the provided Option A and Option B "Search Results". The "Home Page" is in the mockups for reference all we need for the home page is just a search box and a search button (we do not need the entire home page coded for this challenge).
This challenge should create:
1) The search auto-complete (from mock JSON data)
2) Search results page
We want this to be a working prototype so using AngularJS or other client side libraries are acceptable to use.
Required Pages:
Below are the required pages for this prototype to work on required browsers. Please create two different scenarios/prototypes for "Option A" and "Option B". We don't have any storyboard designs for this challenge, but you need to focus on search functionality only where styles are optional.
1. Option A - Content Search (ContentResults-A.pdf):
- For content search (non-name search), the autocomeplete starts pulling up an employee names and sites that has similar words as the query that the user is entering after 3rd letter.
- Autocomplete has two sections "People" and "Sites" as shown on screen (AutoComplete1-A).
- Once the autocomplete result list narrows down, show the link "View All Results for 'TEXT'" at bottom of the autocomplete (AutoComplete2-A).
- All the similar words in the names and sites get bold to show the matching with query.
- Refer the attached document for more details.
2. Option A - People Search (PeopleSearch-A.pdf):
- For people search(name search), the autocomeplete result list narrows down to "People".
- Once user will select "People" tab, show people search results (A-PeopleResults1).
- Refer the attached document for more details.
3. Option B - Content Search (B-ContentSearch.pdf):
- For content search(non-name search), the autocomeplete will again start populating names after 3rd letter but at the query gets completed the autocomplete disappears.
- Once user will hit enter or click on the search button to go to search results page (B-ContentResults-01).
- Refer the attached document for more details.
4. Option B - People Search (B-PeopleSearch.pdf):
- Once user will select "People" tab, show people search results (B-PeopleResults).
- The search functionality should work the similar way as like "Sites" tab.
- Refer the attached document for more details.
Specific HTML/CSS/JavaScript Requirements:
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.
- 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:
Browsers Requirements:
- IE 9+ Browsers on PC
- Latest Safari Browser on iPad, MAC and PC
- Latest Chrome Browser on MAC and PC
- Latest Firefox Browser on MAC and PC
- Latest Smart Phone Mobile Browsers (Android, iPhone, etc)
Documentation Provided:
Attached documents: mockup screens and instructions pdf
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.