Challenge Summary
The Erebus consumer site allows customers to purchase stored-value tokens that can be used to purchase goods and services on participating merchant sites. This contest will produce the necessary HTML and CSS to apply the supplied design to the static and dynamic sections of the web site.
Entries must be your original work, and must not infringe on the copyright or licenses of others. Stock art, clip art, templates and other design elements from other sources are prohibited unless specifically permitted here in the Contest Details.
For this contest you will be developing the HTML and CSS for each of the pages in the supplied sitemap. Page Flow The page flow and site map can be referenced in the consumer site guide.pdf and ConsumerSiteMap.pdf files contained in the provided zip file. Please reference these. All pages must be linked correctly in the prototype. Design and Branding Your design and layout should match the supplied storyboard design (erebus_design_v1.psd) while integrating the content specified for each page in the mock-ups and page requirements document. Several pages in the "wireframe" folder have some branding and icons included. These items need to stay on the pages where indicated. Pages missing logos or navigation should be filled out completely as per the consumer site guide.pdf document. If anything is unclear PLEASE ASK QUESTIONS IN THE FORUM! We are happy to help explain any points that are not clear. HTML/CSS Your HTML should be structured so that there is a common structure for each page with common headers and footers. The content specific to each page will be inserted into a common section of the page template. - Your HTML code must be XHTML 1.0 Strict compliant - Validate your code - we will accept minor validation errors, but please comment your reason for any validation errors. - Your code must render properly in Internet Explorer 6, Internet Explorer 7, Firefox 2 and 3, Google Chrome and Safari in both Mac and PC environments. - Use CSS to space out objects, not clear/transparent images (GIFs or PNGs). - Proper use of structural CSS to lay out your page is strongly encouraged. - No inline CSS styles - all styles must be placed in an external stylesheet. - Use semantically correct tags - use H tags for headers etc... - Use strong and em tags instead of bold and italic tags - Only use table tags for tables of data/information and not for page layout. - Build upon the existing stylesheet - Class and ID names should not visually describe the content (e.g .bigRedTextLeft) JavaScript 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. You are allowed and encouraged to use the jQuery library for this contest. Judging Criteria Your submission will be judged on the following: - How closely the prototype matches the provided storyboards - How well items are styled that are not provided in the storyboards - Cleanliness and organization of source code Preview Image Your preview image should be a screenshot of one page of your choice with no added effects or skewing.
For this contest you will be developing the HTML and CSS for each of the pages in the supplied sitemap. Page Flow The page flow and site map can be referenced in the consumer site guide.pdf and ConsumerSiteMap.pdf files contained in the provided zip file. Please reference these. All pages must be linked correctly in the prototype. Design and Branding Your design and layout should match the supplied storyboard design (erebus_design_v1.psd) while integrating the content specified for each page in the mock-ups and page requirements document. Several pages in the "wireframe" folder have some branding and icons included. These items need to stay on the pages where indicated. Pages missing logos or navigation should be filled out completely as per the consumer site guide.pdf document. If anything is unclear PLEASE ASK QUESTIONS IN THE FORUM! We are happy to help explain any points that are not clear. HTML/CSS Your HTML should be structured so that there is a common structure for each page with common headers and footers. The content specific to each page will be inserted into a common section of the page template. - Your HTML code must be XHTML 1.0 Strict compliant - Validate your code - we will accept minor validation errors, but please comment your reason for any validation errors. - Your code must render properly in Internet Explorer 6, Internet Explorer 7, Firefox 2 and 3, Google Chrome and Safari in both Mac and PC environments. - Use CSS to space out objects, not clear/transparent images (GIFs or PNGs). - Proper use of structural CSS to lay out your page is strongly encouraged. - No inline CSS styles - all styles must be placed in an external stylesheet. - Use semantically correct tags - use H tags for headers etc... - Use strong and em tags instead of bold and italic tags - Only use table tags for tables of data/information and not for page layout. - Build upon the existing stylesheet - Class and ID names should not visually describe the content (e.g .bigRedTextLeft) JavaScript 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. You are allowed and encouraged to use the jQuery library for this contest. Judging Criteria Your submission will be judged on the following: - How closely the prototype matches the provided storyboards - How well items are styled that are not provided in the storyboards - Cleanliness and organization of source code Preview Image Your preview image should be a screenshot of one page of your choice with no added effects or skewing.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.