Exercise: Fill in the blanks app

Clone (git clone) this app to your local drive
cd into fill_in_the_blanks and run bundle
Oh no! One of your gems has gone rogue! Find it and remove it. While you're there, add the pry-rails gem to your app. Which group block does this gem go inside?
Run bundle again
Run rails server
Navigate to localhost:3000 in your browser. What does the error indicate?
Run the proper command to resolve the error.
Run rails server again, is localhost:3000 working? Read the new error then continue on to step 9...
There's a controller already made for you (not application_controller), navigate to that controller and inspect the name, what's wrong with it? (Think convention) Find the problem and correct it.
Navigate to your routes and fix the code there to resolve the error from your browser (Hint: It has to do with your root).
Your controller has all of your CRUD actions and a private method for whitelisting, but they're empty. We'll fill them out as we move through the following steps, use the comments inside of the actions as guidelines.
Create corresponding views for each of your actions.
Which actions do we not create views for? Why?
Navigate to localhost:3000/posts/new in your browser
Oh no, we get an error! What does the error indicate? How can we fix it?
Create routes for your posts. Does the error go away?
We have some seeded data already in the app, where is it located? What command do we run to seed the data?
Run the seed command in your terminal.
Now we have some seed data, how can we get that data to display on our index view?
Fill in the code to have our posts display properly.
We want to add some more posts, edit your new view and the corresponding _form partial to allow creation of new posts via a form.
What other files do we need to fill in before the new form will work properly? Be sure to add validations to the Post model.
Go back to your posts_controller and fill in the corresponding actions to allow creation and viewing of a Post.
Now we want to go back and edit one of our existing posts. Fill in the corresponding view and actions to make this work.
Almost done! Add a button next to each Post that allows us to destroy that post.

BONUS:

Edit your layout to have a custom, site wide, title (i.e., "Ian's Rails App!")
Add links for easy navigation between pages

Your app should:

Be error free
Have your index page display all of your posts
- Including the seeded data that came with the app
Allow your to Create, Read, Update, and Destroy posts
Have your root set to your posts index

Push this app to a new repo in your GitHub called fill_in_the_blanks then submit the link via Piazza

Lekker Plekke

So far our app doesn't do much, so let's make it a bit more interesting by adding in comments. Use your newly acquired knowledge to build in a second model and an appropriate association!

Create a new model called Comment which will handle comments on places. Each comment needs to have the name of the person posting (commenter), the text of the comment (text), as well as a reference to the place. What are the datatypes of these attributes? (Hint: refer to the weblog app. Speficially, how do you associate comments to a place?).

Don't forget to run your migration! (Bonus: What happens after you run rake db:migrate?)

Add in the appropriate associations in the Comment and Places model. What is the relationship between the two? (Bonus: How is this represented in the schema?)
Add in your appropriate routes for comments. This is what you call a "nested resource". (Bonus: How many more routes are created?)
Now let's add a comments controller. Define and fill in a method for create. Don't forget about comment_params!
Concept Question: Where do we want our comments to show up? Ideally we want all comments associated with a specific place to be displayed on the bottom of that place's specific page. Which view is that? What is the url the view maps to?

We will first create a partial for the comments form, and then render that partial onto the aforementioned view.

Create a file called _comment.html.erb under `app/views/comments/_comments.html'. What does the underscore mean? Why do we use these?
In that file, create two paragraph elements. In the first element, display the comment's commenter, and in the second, display the comment's text. Add any supporting text you'd like to help a potential user navigate the form (ie "Commenter: " or "Comment: ").
Navigate to app/views/places/show.html.erb, which is the view for any specific place (Checkpoint: was this the view you were thinking of earlier?). Add code to display all comments and also a form to add new comments. (BONUS: How can we refactor our current code in our form to make it better? Why is that better?)

Lekker!!

BONUS: Judge a Book by its Cover

Let's add some styling. An easy way of making your web apps look instantly better is to use Bootstrap. Bootstrap provides you with custom CSS, Javascript, and some other fun things that you can use once installed into your app. For example, Bootstrap pre-defines CSS classes to make your HTML elements look a certain way. To make your site match, you can just add the same CSS class to your HTML. To read more, you can check out this resource.

For our purposes, we just need to install the css into our rails app. To install: 1. Go to your Gemfile 2. Add gem "twitter-bootstrap-rails" to the list. 3. Run bundle install. 4. Run rails generate bootstrap:install static

Some background on gems: you can view gems as libraries or plug-ins specifically made for rails apps. It's some functionality (ie styling, passwords) that you install to fill a specific need. Gems are super powerful, and you should definitely use them in your final project!

Voila! Play around with adding certain CSS classes to your HTML elements! You can refer to the css page of Bootstrap for reference.

BONUS BONUS: Extensions

Think like a product manager. What are some other cool features you can add to Lekker Plekker? Try to think of a few and then see if you can implement them.