Merge pull request railsbridge#115 from lilliealbert/intermediate_rails

Add intermediate rails curriculum

Author: tjgrathwell

lib/doc_page.rb

@@ -49,7 +49,7 @@ def head_content
   end
 
   def site_title
-    "Railsbridge #{site_name.capitalize}"
+    "Railsbridge #{site_name.split("_").map(&:capitalize).join(" ")}"
   end
 
   def page_title

lib/step.rb

@@ -16,7 +16,15 @@ class Step < Erector::Widget
     padding-left: 1.5em;
     margin-left: .25em;
   }
+}
+
+img.noborder {
+  border: none;
+  display: inline;
+}
 
+.centered {
+  text-align: center;
 }
 
 .message img.icon {
@@ -87,6 +95,22 @@ class Step < Erector::Widget
   background-color: #B0DEE7;
 }
 
+.requirements>h1 {
+  background-color: #93B5DA;
+}
+
+.discussion>h1 {
+  background-color: #92F59A;
+}
+
+.hints>h1 {
+  background-color: #86DFD4;
+}
+
+.tools_and_references>h1 {
+  background-color: #C8A9E0;
+}
+
 .console > pre {
   border: 4px solid #dde;
   @include border-radius(4px);
@@ -134,20 +158,22 @@ def page_name
 
   ## steps
 
-  def steps
-    div :class => "steps" do
-      h1 "Steps"
-      blockquote do
-        yield
-      end
-    end
-  end
+  @@header_sections = {
+    steps:"Steps",
+    explanation:"Explanation",
+    discussion:"Discussion Items",
+    hints:"Hints",
+    tools_and_references:"Tools and References",
+    requirements:"Requirements to advance",
+  }
 
-  def explanation
-    div :class => "explanation" do
-      h1 "Explanation"
-      blockquote do
-        yield
+  @@header_sections.each do |type, header|
+    define_method type do |&block|
+      div :class => type do
+        h1 header
+        blockquote do
+          block.call if block
+        end
       end
     end
   end
@@ -161,7 +187,7 @@ def consider_deploying
       end
     end
   end
-  
+
   def step name = nil, options = {}
     num = next_step_number
     a(:name => "step#{current_anchor_num}")
@@ -264,7 +290,7 @@ def important text = nil, &block
   def tip text = nil, &block
     message text, class: "tip", icon: "info", &block
   end
-  
+
   def todo todo_text
     message nil, class: "todo" do
       span do
@@ -276,10 +302,10 @@ def todo todo_text
   end
 
   ## special
-  
+
   TERMINAL_CAPTION = "Type this in the terminal:"
   RESULT_CAPTION = "Expected result:"
-  
+
   def console msg
     div :class => "console" do
       span TERMINAL_CAPTION

sites/intermediate-rails/add_other_features_of_your_choosing.step

@@ -0,0 +1,16 @@
+message <<-MARKDOWN
+What other features do you want?
+
+Suggestions:
+
+* Profile pages for users (enter user’s name or details, have it display alongside posts).
+* Post/Comment history for individual users (on their profile page?).
+* Easy user profile pictures with [Gravatar](https://gravatar.com/).
+* Add login options with [Omniauth](https://github.com/intridea/omniauth), including Twitter, Facebook, Github, Google, and more.
+  * Check out the Devise [documentation for integrating with Omniauth](https://github.com/plataformatec/devise/wiki/OmniAuth:-Overview).
+* Fiddle with the layout of the show page so it doesn’t look bad. If it looks bad. It probably looks great.
+* Perhaps fancier post markup with Markdown or something similar.
+* Deploy to Heroku and send your message board to all your friends!
+
+## ...and that's that! Good luck! Make more things! Come back again!
+MARKDOWN

sites/intermediate-rails/add_pages_to_create_and_look_at_individual_posts.step

@@ -0,0 +1,53 @@
+requirements do
+message <<-MARKDOWN
+* The user should be able to create a post with a title, author, date published, and content. The author should be the current user. 
+* The complete post should appear on its own page (aka its show page).
+* If the user doesn’t submit all required fields, they should see some error messaging, but shouldn’t lose any of their work.
+MARKDOWN
+  table do
+    tr do
+      td do
+        h2 'Create View', class: 'centered'
+      end
+      td do
+        h2 'Show View', class: 'centered'
+      end
+    end
+    tr do
+      td do
+        img class: 'noborder', src: 'img/create_post.png'
+      end
+      td do
+        img class: 'noborder', src: 'img/show_post.png'
+      end
+    end
+  end
+end
+
+discussion do
+message <<-MARKDOWN
+* How do you create a resource? What parameters do you need to pass?
+  * How will you associate the current user with the post? 
+* Then: what did rails make for you when you used the resource generator? Find all the new files. Maybe even list them out on a whiteboard.
+* What's the difference between the `new` and `create` methods in the posts controller? 
+MARKDOWN
+end
+
+tools_and_references do
+message <<-MARKDOWN
+* RailsGuides - Form Helpers, section 2.2: <http://guides.rubyonrails.org/form_helpers.html#binding-a-form-to-an-object>
+* RailsGuides - Routes - CRUD, Verbs, and Actions: <http://guides.rubyonrails.org/routing.html#crud-verbs-and-actions>.
+* RailsGuides - Active Record Validations and Callbacks: <http://guides.rubyonrails.org/active_record_validations_callbacks.html>
+MARKDOWN
+end
+
+hints do
+message <<-MARKDOWN
+* Don't hand code the form! You don't have to! Rails will help. See RailsGuide link above! 
+* Rails has a built-in way to note when something was stored in the database. Probably handy for showing the date / time a post was created.
+* For now, we're going to use the user's email address to identify them. You can add names or other identifiers later! (Also, even though you're going to get the current user's email address from the User model, you'll still need a user parameter for your Post resource.)
+* You need a `create` method to store your post data - scroll down a little bit in this section of the Getting Started guide for very helpful information and to see an example of a create method: <http://guides.rubyonrails.org/getting_started.html#creating-new-posts>.
+MARKDOWN
+end
+
+next_step "make_a_posts_index_page"

sites/intermediate-rails/add_replying.step

@@ -0,0 +1,42 @@
+requirements do
+message <<-MARKDOWN
+* The user should see a 'New Reply' link or button on a post's show page which takes them to a form. The form should include the title of the post being replied to.
+* The user should be able to create a new reply to a post using the 'New Reply' form.
+* The user should see all the replies to a post on the post’s show page.
+* If the user doesn’t submit all required fields, they should see some error messaging, but they shouldn’t lose any of their work.
+MARKDOWN
+  table do
+    tr do
+      td do
+        h2 'Create View', class: 'centered'
+      end
+      td do
+        h2 'Show View', class: 'centered'
+      end
+    end
+    tr do
+      td do
+        img class: 'noborder', src: 'img/create_reply.png'
+      end
+      td do
+        img class: 'noborder', src: 'img/show_replies.png'
+      end
+    end
+  end
+end
+
+discussion do
+message <<-MARKDOWN
+* What is a nested resource? When is it appropriate and how does it help?
+* How do the replies_controller and posts_controller interact?
+* What should happen to the routes file for this nesting business to work?
+MARKDOWN
+end
+
+tools_and_references do
+message <<-MARKDOWN
+* RailsGuides - Rails Routing from the Outside In http://guides.rubyonrails.org/routing.html
+MARKDOWN
+end
+
+next_step "inline_replying_on_a_post"

sites/intermediate-rails/create_a_new_rails_app_with_a_static_home_page.step

@@ -0,0 +1,35 @@
+requirements do
+message <<-MARKDOWN
+* You should have a new rails app with with a static home page that's under your control. Make sure the controller for this page is called **HomeController**.
+* You, the developer, should explain to a teacher, TA, or fellow student how Rails knows to render the home view.
+MARKDOWN
+  img class: 'noborder', src: 'img/static_home_page.png'
+end
+
+discussion do
+message <<-MARKDOWN
+* In order to have a static home page, you will need a route, a controller, a view. Discuss!
+  * Seriously. If you don't discuss this stuff, things will be SO much harder.
+* We’re using `rails g resource` instead of `rails g scaffold` because it forces you, the developer, to do more understanding-building brain work. The teacher/TAs can perhaps comment on what they would do in the real world and their thoughts on the excellence of this choice for learning-purposes.
+* What do you need to add to your home controller (after you've made it) to have a static home page?  
+* How does the home/index.html.erb view file relate to the layouts/application.html.erb view file?
+* What’s the significance of yield in the application view?
+* What does the home controller do?
+MARKDOWN
+end
+
+tools_and_references do
+message <<-MARKDOWN
+* RailsGuides - Setting the Application Home Page: <http://guides.rubyonrails.org/getting_started.html#setting-the-application-home-page>.
+* Rails Guides - controllers overview: <http://guides.rubyonrails.org/action_controller_overview.html>.
+MARKDOWN
+end
+
+hints do
+message <<-MARKDOWN
+* You'll definitely want to delete the index.html that Rails provides. If you can't find it, ask your neighbor! 
+* If you have no idea what to put in your home controller, maybe try looking back at a past-Railsbridge app? Or another rails app you have lying about? 
+MARKDOWN
+end
+
+next_step "install_devise"