Rails is a popular back-end framework with an MVC architecture. Traditionally, Rails was responsible for all parts of your web application, including building and send HTML responses. Sending HTML responses is the "view" layer's responsibility.

In this program, we use Rails as an API, which means we won't be using the view layer. Instead, we'll use models and controllers and build and send JSON responses to incoming web requests.

• ga-wdi-boston/http-study
• ga-wdi-boston/json-study

By the end of this, developers should be able to:

• Define the responsibilities of the model layer in Rails.
• Define the responsibilities of the controller layer in Rails.
• Define the responsibilities of the router in Rails.
• Diagram how a Rails API responds to a web request.

1. Fork and clone this repository.
2. Change into the new directory.
3. Create and checkout a new branch, named response.
4. Follow the directions given in study.md.
5. When finished, push to your fork and submit a pull request.

You may wish to refer to FAQs related to forking, cloning, and pull requests.

1. All content is licensed under a CC­BY­NC­SA 4.0 license.
2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].