Review

Complete Exit Ticket: http://ix-exit-tickets.herokuapp.com/

It's almost final project time! As extra review, take a look at the resources on the bottom of the Course Page. If you have any questions about Github, Rails or Heroku, now is the time to ask Ian or Erica. In particular, check out the following resources:

• Github: How to create a Github repo
• Rails Review (Part I): Cheat Sheet for building Rails apps
• Rails Review (Part II): Cheat Sheet for forms and validations
• Example Rails App with Notes: Clone this repo, open up the entire folder in sublime, and read the code + comments.
• Heroku: Checklist for pushing to Heroku

Final Project

With your partner, choose your top 2 ideas, and create a short proposal document (1 page max) for at least one of them. You will be discussing your idea and proposal document with either Erica, Ian, or Brian tomorrow morning. The proposal document must have the following components.

Proposal Guidelines

Don't worry: you don't need to have everything fully fleshed out right now.

In your proposal, answer the following questions:

• What is the problem you want to solve?
• What is the solution you are proposing?
• How does your system work?
• What kinds of external tools do you think you will need? (ex: APIs, gems)
• What do you think you still need to learn to make your app a success? (ex: JQuery, Search, etc.)

Keep in mind that your app must have:

• at least 2 controllers
• at least 1 devise User model
• at least 2 app models
• at least 1 has_many OR has_many :through OR has_and_belongs_to_many relationship
• RESTful routes for app models
• deployed on Heroku
• Bootstrap
• CSS/HTML(/JS) organized correctly

Try to keep it as close to these requirements as possible when you design your proposal so have time to finish. Remember, Twitter originally had 2 app models and 1 user model and they launched a billion dollar empire.

BruGram: Due Tomorrow!