The Course Project will be an ongoing accumulation of the Course Project Milestones due each week based on the assigned readings, lectures, and Labs. For the final product of this Course Project, you must complete a stand-alone website of around five to seven pages.
You may choose any content you desire for the site, such as a work-related site or personal interest site. In addition to criteria listed throughout the process, you will be evaluated on cohesiveness, accessibility, and design.
The overall objective of the Course Project is to give the opportunity to create a functioning website from initial conception, planning, development, testing, and publishing to a web server.
Create a Project Proposal document stating the basic elements you will include in your website. Include a cover sheet with your name, course, and week number. The body of your report must include
Update the project proposal/design document based on any feedback given from milestone 1.
Extend the Week 1 Project Proposal/Design document by adding a site diagram using MS Visio that includes the following:
This layout will be the main design template for all of the pages in your site. In future weeks, you will be altering the main content areas as needed. In the diagramming application, use the Save As option to create an image file (jpg, gif, or png) of your site. Copy this image file into your Project Proposal document.
Extend the Week 2 Project Proposal/Design and create a detailed page layout design in Visio that you will use as a template for all the web pages in your site. The template should include
1.a header area;
2.a link area;
3.a main content area; and
4.a footer area.
In the diagramming application, use the Save As option to create an image file (jpg, gif, or png) of your site. Copy this image file into your Project Proposal document.
Create blank content pages as per your site diagram. To do this, you must have the filenames of major site pages determined. You should have a home page (index.htm) and all of the subpages created, but content information is not required. Create the navigation links between the site pages. The pages do not need to have much content, but they must be created and contain the navigation elements and placeholder elements for your content. Begin to implement the box model with < div> tags and CSS.
Based on the site, page layout, and navigation developed in prior steps, begin to add content to your site. Include appropriate typography, colors, and imagery as per the lecture and Lab assignments. Begin to implement the box model through the use of < div> tags and absolute positioning. Use inline and embedded where appropriate.
Upon completion of this step, zip up all of the files for the site into one single file and submit the file.
Continue to develop the site content as directed in milestone 4. At this point, at least 3 of the pages for the site should be completed.
Use the knowledge gained in this week's lecture and Lab to create a user feedback form. Include all necessary controls (text boxes, radio buttons, check boxes, text areas, dropdown lists, and buttons) to allow the user to effectively interact with the form. Use CSS to control the layout of the form. Include reset and submit buttons with the form. The reset button should clear the form and the submit button should load a "Your information has been received" page.
Move all site and page level styles to an external CSS file.
Upon completion of this step, zip up all of the files for the site into one single file and submit the file.
Continue to develop content for the site.
Use the knowledge gained in this week's lecture and Lab to implement dynamic content to a page in your site. Use JavaScript features to perform such things as basic calculations, image rollovers, user prompts, and alerts.
Upon completion of this step, zip up all of the files for the site into one single file and submit the file.
All content pages are completed for the site and the site is uploaded to the course web server per instructions from your professor.
Visit http:www.w3.org/WAI/RC/tools/ (Links to an external site.) to locate tools to check for accessibility. There are some free online tools listed there, such as EvalAccess, which you can use to check your HTML code. Check your site and make any necessary corrections in your code. Conduct a user test with at least two people (spouses and kids are fine to use as testers). In addition to observing them using your site, have them fill out the form you created in Week 5. Take screenshots of the filled out forms to collect the user feedback. Create a short report (one page or less) detailing the results of the testing, including user suggestions and your response to those suggestions (whether you feel they are valid and whether they can be accommodated). Compare the user responses to your expectations of the user working with your site.