Overview

This first project is a continuation of the starter project. It requires more extensive customizations to the scaffolded output and a summary document describing the application.

Give your application the name appOne.

Required Customizations

1. Modify the model so that it uses validations appropriate for your application.
2. Modify the controller's index method (or create a new controller method) so that entries can be grouped, searched or otherwise restricted by some appropriate conditions (e.g. only show recently added items).
3. Modify views so that alternate web controls (e.g. radio buttons, menus) or alternate data displays are used.
4. Modify the layout template (in app/views/layouts) so that a constant message, header or image appears across all of the site's pages.
5. 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.
6. Make additional customizations that is appropriate for your application. This might include adding additional content to the "show" page that is based on the entry's attributes (e.g. adding up a score, showing text that corresponds to a rating).

Summary Document

Prepare a one-page document that summarizes your application and the work you did to create it. The document should show evidence of your understanding of the application components by explaining your scaffold customizations. In your application, make sure you specify the versions used for ruby and rails.

Submission

The summary document should use a common presentation format, ideally PDF. Using a Zip application, package both the summary document and your rails folder containing all of the code into one Zip file. Submit the zip file using the D2L online submission site.

Double check that your application is named appOne.

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 and reflect
• 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.