Challenge Summary
System configuration is always tricky since it affects the way the system behaves; a small change in configuration parameters could have a huge implication on the behavior of the system. This is even trickier when there are a number of systems, each with a different way of dealing with configurations. Thus it is paramount for systems to have a reliable, secure, and traceable configuration system.
The purpose of this application is to create a centralized and unified configuration interface that allows users to set the configurations without using scripts. This competition will define the HTML prototype for the given application. Since this is an internal application, no storyboards have been provided, and it is expected to be simpler than the usual HTML prototype competition.
The following pages will be required (see the Sitemap): - Login Page - Business User Home Page - Audit History - Admin Homepage - Edit Configuration Tool Setup - Setup Configuration Tool - Audit Reports (Including reports for specific tool and recent configuration) - Audit Configuration Changes The prototype should satisfy all the use cases outlined in the provided Application Requirement Specification, except for 2.6 View Tool, since that is external to the application. The HTML prototype should provide all the necessary functionality in order to satisfy the given use cases (most of it should already be covered by the wireframe, but if any inconsistencies are noticed, then please ask questions in the forums). Development Considerations - Submissions must render correctly in Internet Explorer 6, Internet Explorer 7, Firefox 2 and 3, Google Chrome and Safari in both Mac and PC environments. - Follow all functionality and navigation shown in the wireframes Specific HTML/CSS Requirements - Your HTML code must be XHTML 1.0 Strict compliant - Validate your code - we will accept minor validation errors, but please comment your reasons for any validation errors in a text file you provide. - 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). - If alpha channel PNGS are used be sure to include script to use filters for IE 6 - Do not use graphical text (for buttons use the graphics as backgrounds)- 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. - Provide as much semantic code as possible. Elements such as ABBR, ACRONYM, ADDRESS, CITE and CODE enhance the semantics of content when used appropriately. - 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. Target Audience This is an internal tool, and the users of this will be the internal administrators of the client. You should aim for a professional look that is implemented well in HTML. Branding Guidelines Since this is an internal tool, no images will be needed for this application. However, it is desired that the fonts, colors and image header from www [dot] tree [dot] com be used. Reference Design See www [dot] tree [dot] com Judging Criteria Your submission will be judged on: - Overall neatness and cleanliness of the HTML code. - The visual appeal of the web page. - Whether all the needed functionality from the Application Requirement Specification and Wireframes have been provided.
The following pages will be required (see the Sitemap): - Login Page - Business User Home Page - Audit History - Admin Homepage - Edit Configuration Tool Setup - Setup Configuration Tool - Audit Reports (Including reports for specific tool and recent configuration) - Audit Configuration Changes The prototype should satisfy all the use cases outlined in the provided Application Requirement Specification, except for 2.6 View Tool, since that is external to the application. The HTML prototype should provide all the necessary functionality in order to satisfy the given use cases (most of it should already be covered by the wireframe, but if any inconsistencies are noticed, then please ask questions in the forums). Development Considerations - Submissions must render correctly in Internet Explorer 6, Internet Explorer 7, Firefox 2 and 3, Google Chrome and Safari in both Mac and PC environments. - Follow all functionality and navigation shown in the wireframes Specific HTML/CSS Requirements - Your HTML code must be XHTML 1.0 Strict compliant - Validate your code - we will accept minor validation errors, but please comment your reasons for any validation errors in a text file you provide. - 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). - If alpha channel PNGS are used be sure to include script to use filters for IE 6 - Do not use graphical text (for buttons use the graphics as backgrounds)- 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. - Provide as much semantic code as possible. Elements such as ABBR, ACRONYM, ADDRESS, CITE and CODE enhance the semantics of content when used appropriately. - 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. Target Audience This is an internal tool, and the users of this will be the internal administrators of the client. You should aim for a professional look that is implemented well in HTML. Branding Guidelines Since this is an internal tool, no images will be needed for this application. However, it is desired that the fonts, colors and image header from www [dot] tree [dot] com be used. Reference Design See www [dot] tree [dot] com Judging Criteria Your submission will be judged on: - Overall neatness and cleanliness of the HTML code. - The visual appeal of the web page. - Whether all the needed functionality from the Application Requirement Specification and Wireframes have been provided.
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.