Overview

For this project, you will create a scaffold-based application and customize all of its components.

Application Design

You may choose the design and model for the scaffold. Your choice of model and application should be substantively different than the examples presented in class (e.g. no movie applications are allowed).

Scaffold customizations

Your application should include the following customizations:

• Modify the routes.rb file so that the root path takes the user to an appropriate starting view.
• Modify the model so that it uses validations appropriate for your application.
• Modify the model so that it has at least one virtual attribute that can be used for alternate presentations.
• Modify views so that alternate web controls (e.g. radio buttons, menus) or alternate data displays are used.
• Modify the layout template (in app/views/layouts) so that a constant message, header or image appears across all of the site's pages.
• Modify the css file so that your application has a visual presentation that is appropriate for your application. Small, simple changes are fine. Changes that hinder usability should be avoided. You can find the scaffold css file in public/stylesheets.
• Make additional customizations that is appropriate for your application.

Report

Write a one-page portfolio-quality report that summarizes the accomplishments for your project. The level of professionalism for the report should be such that you would want to show it to potential employers. The report may make use of section headers, bullet points, numbered lists and other formatted presentations. I will use the report to guide my review of your application.

Submission

The summary document should use a common presentation format, ideally PDF. Create a zip file from the folder and submit the zip file using the D2L online submission site.

Grading

This project is worth 20 points and will be reviewed using the following criteria:

• Clarity. The summary document should concisely and efficiently present the project accomplishments.
• Accomplishment. The project accomplishments should surpass the project requirements.
• Soundness. Explanations and implementation should be technically correct.
• Understanding. The summary document should use terms (e.g. model, controller, view, HTML, etc.) to show understanding of the project concepts.