went directly to the topics list."
+
+ message "In this step we'll make that happen and learn a bit about routes in Rails."
+}
+
+steps {
+
+ step "Add a root route" do
+ message "Open `config/routes.rb`. Search the file for 'root' (near the top) uncomment that line and change it to read `root 'topics#index'`. When you are done the line should look like this:"
+
+ message "(Rails 3.x users should add `root to: 'topics#index'` and will need to remove their `public/index.html` file)."
+
+ end
+
+ source_code :ruby, <<-RUBY
+root 'topics#index'
+ RUBY
+
+
+ step "Confirm your changes" do
+ message "Go back to . You should be taken to the topics list automatically."
+ end
+}
+
+explanation {
+
+ message <<-MARKDOWN
+ * `root 'topics#index'` is a rails route that says the default
+ address for your site is `topics#index`. `topics#index` is the topics
+ list page (the topics controller with the index action).
+ * Rails routes control how URLs (web addresses) get matched with
+ code on the server. Similar to how addresses match with houses and
+ apartments.
+ * The file `config/routes.rb` is like an address directory listing the
+ possible addresses and which code goes with each one
+ * `routes.rb` uses some shortcuts so it doesn't always show all the
+ possible URLs. To explore the URLs in more detail we can use the
+ terminal.
+
+ At the terminal type `rake routes`. You should get something that
+ looks like this:
+
+ ````
+ $ rake routes
+
+ Prefix Verb URI Pattern Controller#Action
+ topics GET /topics(.:format) topics#index
+ POST /topics(.:format) topics#create
+ new_topic GET /topics/new(.:format) topics#new
+ edit_topic GET /topics/:id/edit(.:format) topics#edit
+ topic GET /topics/:id(.:format) topics#show
+ PATCH /topics/:id(.:format) topics#update
+ PUT /topics/:id(.:format) topics#update
+ DELETE /topics/:id(.:format) topics#destroy
+ root GET / topics#index
+ ````
+ This shows all the URLs your application responds to. The code that starts with colons are variables so :id means the id number of the record. The code in parenthesis is optional.
+
+ In Rails 4, you can also get this information on your site in development. Go to http://localhost:3000/rails/info and you'll see something like this:
+
+ 
+
+ You'll also see that table in Rails 4 whenever you try to access an invalid route (try http://localhost:3000/sandwich)
+
+### Exploring Routes (optional)
+
+ Now you can have a look at the paths that are available in your app.
+ Let's try looking at one of the topics routes we just generated.
+ Open up your rails console and play:
+
+ $ rails console
+ >> app.topics_path
+ => "/topics"
+ >> app.topics_url
+ => "http://www.example.com/topics"
+
+ `app` is a special object that represents your entire application.
+ You can ask it about its routes (as we just did), play with its
+ database connections, or make pseudo-web requests against it with
+ `get` or `post` (and lots more).
+
+ MARKDOWN
+}
+
diff --git a/sites/suggestotron-sans-scaffolds/add_a_topics_show_page.step b/sites/suggestotron-sans-scaffolds/add_a_topics_show_page.step
new file mode 100644
index 000000000..3b1f4b24b
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/add_a_topics_show_page.step
@@ -0,0 +1,76 @@
+message <<-MARKDOWN
+Turns out the descriptions are getting too long for the index page, and we need to hide them!
+
+Students will:
+
+* Add a show action to the controller
+* Add a show view
+* Change the index to just display the title w/a link to the view
+
+MARKDOWN
+
+next_step "redirect_to_the_topics_list_after_creating_a_new_topic"
+
+
+message "# Here's the old page for linkifying the title"
+
+goals {
+ message "Your friends recommended two changes for the site:"
+ goal "Don't show the description on the list page"
+ goal "Make the title a link and when it's clicked show the description"
+}
+
+steps {
+
+
+ step("Remove the description") {
+
+ message "Let's start by removing the description. Open `app/views/topics/index.html.erb` and delete the line that looks like this:"
+
+ source_code :erb, "<%= topic.description %> | "
+
+ message "Also delete the line that looks like this:"
+ source_code :erb, "Description | "
+
+ message "If you save and try to load it in the browser you should see that the description no longer appears."
+
+ }
+
+ step("Make the title a link") {
+
+ message "Now make the title a link by editing `app/views/topics/index.html.erb` (again) and replacing this line:"
+
+ source_code :erb, "<%= topic.title %> | "
+
+ message "with this:"
+
+ source_code :erb, "<%= link_to topic.title, topic %> | "
+ }
+}
+
+explanation {
+
+ source_code :erb, "<%= topic.description %> | "
+
+ message "This line was getting the description using .description and just printing it out."
+
+ source_code :erb, "Description | "
+
+ message "
+ `` stands for table header and everything between ` | ` and
+ ` | ` was being printed as a table header (bold). We removed it
+ since we removed the description and it would look funny to have the
+ header and the wrong thing below it."
+
+ hr
+
+ source_code :erb, "<%= link_to topic.title, topic %> | "
+
+ message "
+ Here's another use of `link_to` to create a link on the page. This
+ `link_to` creates a link using the text from the topic title and goes
+ to the topic#show page."
+}
+
+
+
diff --git a/sites/suggestotron-sans-scaffolds/add_an_edit_topics_form.step b/sites/suggestotron-sans-scaffolds/add_an_edit_topics_form.step
new file mode 100644
index 000000000..ecf028b86
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/add_an_edit_topics_form.step
@@ -0,0 +1,9 @@
+message <<-MARKDOWN
+
+This page will have the student pull their topics form into a partial and render it on the edit page.
+
+This will also involve adding edit and update actions to the topics controller.
+
+MARKDOWN
+
+next_step "add_topic_voting"
diff --git a/sites/suggestotron-sans-scaffolds/add_topic_voting.step b/sites/suggestotron-sans-scaffolds/add_topic_voting.step
new file mode 100644
index 000000000..844202de4
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/add_topic_voting.step
@@ -0,0 +1,84 @@
+message <<-MARKDOWN
+This page is going to have students:
+
+* write a migration to add "vote_count" to the topics model
+* add vote buttons to the UI with relevant controller actions
+
+MARKDOWN
+
+next_step "add_a_topics_show_page"
+
+message "## This is the old page, for reference"
+
+goals {
+ goal "Now we're going to add a button people can click to cast a vote."
+}
+
+steps {
+
+ step "Add the button to the view" do
+
+ message "Edit `app/views/topics/index.html.erb` so that the bottom loop looks like this:"
+
+ source_code :erb, <<-HTML
+ <% @topics.each do |topic| %>
+
+ | <%= topic.title %> |
+ <%= topic.description %> |
+ <%= pluralize(topic.votes.count, "vote") %> |
+ <%= button_to '+1', votes_path(topic_id: topic.id), method: :post %> |
+ <%= link_to 'Show', topic %> |
+ <%= link_to 'Edit', edit_topic_path(topic) %> |
+ <%= link_to 'Destroy', topic, confirm: 'Are you sure?', method: :delete %> |
+
+ <% end %>
+ HTML
+ end
+
+ step "Add the create method to the controller" do
+ message "Add the following method to `Vote` in `app/controllers/votes_controller.rb`:"
+ source_code :ruby, <<-RUBY
+class VotesController < ApplicationController
+ def create
+ topic = Topic.find(params[:topic_id])
+ vote = topic.votes.build
+ vote.save!
+ redirect_to(topics_path)
+ end
+end
+ RUBY
+ end
+
+ step "Confirm your changes in the browser" do
+ message "Go back to and play."
+ message "Revel in the fact that you didn't have to restart the server to see these changes. Hawt, no?"
+ end
+}
+
+explanation {
+
+ message "First we added these two lines to `app/views/topics/index.html.erb`"
+ source_code :erb, <<-HTML
+ <%= pluralize(topic.votes.count, "vote") %> |
+ <%= button_to '+1', votes_path(topic_id: topic.id), method: :post %> |
+ HTML
+
+ message <<-MARKDOWN
+ * `pluralize(topic.votes.count, "vote")` displays the number of votes the topic has, plus the word 'vote' or 'votes' accordingly.
+ * `button_to '+1'` creates an html button with the value '+1'.
+ * `votes_path(topic_id: topic.id)` creates the right url for the action we want to invoke. In this case, we want to create a vote for the current topic.
+ * `votes_path(topic_id: 42)` would output `/votes?topic_id=42`
+ * `method: :post` ensures we do the create action of CRUD, not the read action.
+
+ The changes we made to votes controller are a bit more complicated so let's work through them line by line.
+
+ * `topic = Topic.find(params[:topic_id])`
+ * Finds the topic in the database with that id and stores it in the variable 'topic'.
+ * `params[:topic_id]` corresponds to the topic_id part of the votes_path above (eg `?topic_id=42`).
+ * `vote = topic.votes.build` creates a new vote for the current topic.
+ * `vote.save!` saves the vote to the database.
+ * `redirect_to(topics_path)` tells the browser to go back to topics_path (the topics list).
+ MARKDOWN
+}
+
+insert 'consider_deploying'
diff --git a/sites/suggestotron-sans-scaffolds/creating_a_migration.step b/sites/suggestotron-sans-scaffolds/creating_a_migration.step
new file mode 100644
index 000000000..3ac1ab5ab
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/creating_a_migration.step
@@ -0,0 +1,73 @@
+section "Overview" do
+
+ model_diagram header: 'Topics', fields: %w(id title description)
+
+ message <<-MARKDOWN
+Suggestotron has a list of topics that people can vote on. We'll store our topics in the database.
+
+Rails communicates with the database using Active Record, which allows us to write Ruby code instead of SQL.
+ We change our database using a migration file.
+
+### What's a migration?
+
+Migration files allow you to recreate the state of the database from scratch at any point. When you run `rake db:migrate`, Rails
+goes through each of the files in the `db/migrate` directory to create all the tables in the database.
+
+Here is a fun tip: DON'T UPDATE MIGRATION FILES. It's terrible, albeit initially tempting, practice to realize you need another field and edit
+the original migration file. Instead, create a new migration (perhaps called `AddVotesToTopics`). This will keep your database
+in a reasonable state and not ruin everything if you're ever collaborating with other developers on a project.
+MARKDOWN
+end
+
+steps do
+
+
+ step { console "rails generate migration AddTopics" }
+
+ step do
+ message <<-MARKDOWN
+In your text editor, find the file that you just generated. It will be in the folder `db/migrate`
+and will end with `_add_topics.rb` (the first part is a timestamp). Double click on the file to
+open it in Sublime.
+ MARKDOWN
+ end
+
+ step do
+ message <<-MARKDOWN
+Now we'll tell ActiveRecord what we actually want the table to look like. Rails has given us
+`up` and `down` methods already, but we can actually combine all of our commands into a single method, `change`.
+
+Add the following text to your migration, replacing lines 2 through 6:
+ MARKDOWN
+ source_code <<-RUBY
+def change
+ create_table :topics do |t|
+ t.string :title
+ t.text :description
+ t.timestamps
+ end
+end
+ RUBY
+ message <<-MARKDOWN
+ActiveRecord will add the id to the table automatically, so we only have to specify the title and description.
+ MARKDOWN
+
+ end
+
+ step do
+ console "rake db:migrate"
+ message <<-MARKDOWN
+This tells Rails to update the database to include a table for our new model. Rails is also smart enough to create the database if it can't find it.
+ MARKDOWN
+ end
+end
+
+section "rake" do
+ message <<-MARKDOWN
+`rake` _(Ruby Make)_ is a tool that allows you to run small Ruby programs (**tasks**) that you use often in your application. Here, `rake db:migrate` is a task provided by the Rails framework.
+
+You can run `rake -T` to see a list of all the `rake` commands your app currently responds to, along with a short description of each task.
+ MARKDOWN
+end
+
+next_step "add_a_topics_model"
diff --git a/sites/suggestotron-sans-scaffolds/credits_and_next_steps.step b/sites/suggestotron-sans-scaffolds/credits_and_next_steps.step
new file mode 100644
index 000000000..dca0fe0b4
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/credits_and_next_steps.step
@@ -0,0 +1,36 @@
+message <rails new created a lot directories and
+files. We're going to focus on a few of them today:
+MARKDOWN
+
+ table border: "1", cellspacing: "0", cellpadding: "3", align: "center" do
+ tr {
+ th "File/Folder"
+ th "Purpose"
+ }
+ tr {
+ td "app/"
+ td "Contains the controllers, models, and views for your application. You will do most of your work here."
+ }
+ tr {
+ td "config/"
+ td "Configure your application's runtime rules, routes, database, and more."
+ }
+ tr {
+ td "db/"
+ td "Shows your current database schema, as well as the database migrations."
+ }
+ tr {
+ td "public/"
+ td "The only folder seen to the world as-is. If you put files in here, they will be served directly without any processing by Rails."
+ }
+ tr {
+ td "app/assets/"
+ td "This is where your images, JavaScript, stylesheets (CSS), and other static files should go. Rails apps use something called the Assets Pipeline, which combines all the JavaScript and CSS files in this directory into a single file for speediness."
+ }
+ end
+
+ message "There is a lot more that `rails new` created. Probably enough to fill a book, so we're going to ignore them for now."
+end
+
+next_step "start_using_git"
diff --git a/sites/suggestotron-sans-scaffolds/img/Seattle_list_with_topic.png b/sites/suggestotron-sans-scaffolds/img/Seattle_list_with_topic.png
new file mode 100644
index 000000000..f7e518ad2
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/Seattle_list_with_topic.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/Seattle_topic_created.png b/sites/suggestotron-sans-scaffolds/img/Seattle_topic_created.png
new file mode 100644
index 000000000..86f122160
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/Seattle_topic_created.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/Seattle_topic_list_page.png b/sites/suggestotron-sans-scaffolds/img/Seattle_topic_list_page.png
new file mode 100644
index 000000000..0de297b07
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/Seattle_topic_list_page.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/Start_page.png b/sites/suggestotron-sans-scaffolds/img/Start_page.png
new file mode 100644
index 000000000..3747ba762
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/Start_page.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/finished_app.png b/sites/suggestotron-sans-scaffolds/img/finished_app.png
new file mode 100644
index 000000000..dc197b277
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/finished_app.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/mvc.png b/sites/suggestotron-sans-scaffolds/img/mvc.png
new file mode 100644
index 000000000..79b26fb0a
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/mvc.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/rails-new-open-in-sublime.png b/sites/suggestotron-sans-scaffolds/img/rails-new-open-in-sublime.png
new file mode 100644
index 000000000..15c7092ef
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/rails-new-open-in-sublime.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/rails4_rails_info_routing.png b/sites/suggestotron-sans-scaffolds/img/rails4_rails_info_routing.png
new file mode 100644
index 000000000..463b07d50
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/rails4_rails_info_routing.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/seattle_display_vote_count.png b/sites/suggestotron-sans-scaffolds/img/seattle_display_vote_count.png
new file mode 100644
index 000000000..d718f8cf4
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/seattle_display_vote_count.png differ
diff --git a/sites/suggestotron-sans-scaffolds/img/workflow.png b/sites/suggestotron-sans-scaffolds/img/workflow.png
new file mode 100644
index 000000000..6513e0340
Binary files /dev/null and b/sites/suggestotron-sans-scaffolds/img/workflow.png differ
diff --git a/sites/suggestotron-sans-scaffolds/redirect_to_the_topics_list_after_creating_a_new_topic.step b/sites/suggestotron-sans-scaffolds/redirect_to_the_topics_list_after_creating_a_new_topic.step
new file mode 100644
index 000000000..beca69999
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/redirect_to_the_topics_list_after_creating_a_new_topic.step
@@ -0,0 +1,73 @@
+goals {
+
+ message "
+ When a user creates a new topic they are currently shown a page with
+ just that topic. For our voting app it makes more sense that they
+ would be taken back to the topic list."
+
+ goal "In this step we'll change the flow of our app so that the user is taken back to the topics list after they add a new topic."
+}
+
+steps {
+
+ step "Change the topics controller" do
+
+ message "Open `app/controllers/topics_controller.rb` and look at the create method. "
+
+ message "Find the line:"
+
+ source_code :ruby, "format.html { redirect_to @topic, notice: 'Topic was successfully created.' }"
+
+
+ message 'and change `@topic` to `topics_path` like this:'
+
+ source_code :ruby, "format.html { redirect_to topics_path, notice: 'Topic was successfully created.' }"
+
+ message 'so that the file looks like this:'
+
+ source_code :ruby, <<-RUBY
+def create
+ @topic = Topic.new(topic_params)
+
+ respond_to do |format|
+ if @topic.save
+ format.html { redirect_to topics_path, notice: 'Topic was successfully created.' }
+ format.json { render json: @topic, status: :created, location: @topic }
+ else
+ format.html { render action: "new" }
+ format.json { render json: @topic.errors, status: :unprocessable_entity }
+ end
+ end
+end
+ RUBY
+ end
+
+ step "Add the flash message to your application view" do
+ message "Open `app/views/layouts/application.html.erb`."
+
+ message "Find the `` HTML tag and immediately after add the following code:"
+
+ source_code :ruby, <<-RUBY
+<% flash.each do |name, msg| %>
+ <%= msg %>
+<% end %>
+ RUBY
+ end
+
+ step "Confirm your changes" do
+ message "Look at ."
+ end
+}
+
+
+explanation {
+
+ message <<-MARKDOWN
+ * `format.html { redirect_to topics_path, notice: 'Topic was successfully created.' }`:
+ * `format.html` means that the server should send html back to the browser
+ * `redirect_to topics_path` means show the **topics list page** when we're done creating a topic
+ * `notice: 'Topic was successfully created.'` puts the message into the flash so it will be displayed on the topics list
+ MARKDOWN
+}
+
+next_step "credits_and_next_steps"
diff --git a/sites/suggestotron-sans-scaffolds/running_your_application_locally.step b/sites/suggestotron-sans-scaffolds/running_your_application_locally.step
new file mode 100644
index 000000000..6ed4a2e89
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/running_your_application_locally.step
@@ -0,0 +1,42 @@
+section "Overview" do
+ message <<-MARKDOWN
+
+### What's a web server?
+
+A web server listens for incoming requests from the browser and then asks to your application what it
+would like to send back. This will usually be HTML in our case.
+
+### Why run our app locally?
+
+Running your app locally provides a very simple means to see your changes before you commit and push them to Heroku.
+
+MARKDOWN
+end
+
+steps do
+ step do
+ console "rails server"
+ end
+ step do
+ text "Point your web browser to "
+ url "http://localhost:3000"
+ p "See your web app actually running!"
+ end
+
+ step do
+ message "When at the terminal with your running rails server, type Control+C to stop rails server. You can do this now."
+ result <<-STOPPING_RAILS_SERVER
+^C[2012-03-31 08:33:11] INFO going to shutdown ...
+[2012-03-31 08:33:11] INFO WEBrick::HTTPServer#start done.
+Exiting
+ STOPPING_RAILS_SERVER
+ end
+
+ important <<-MARKDOWN
+On Windows, sometimes Control-C doesn't work. In that case, look for the key called 'Break' or 'Pause' and press
+Control-Break, then answer Y at the prompt. If there is no Pause/Break key on your keyboard, you can run `ruby script/rails server`
+instead of `rails server` which should allow Control-C to stop the server.
+MARKDOWN
+end
+
+next_step "creating_a_migration"
diff --git a/sites/suggestotron-sans-scaffolds/start_using_git.step b/sites/suggestotron-sans-scaffolds/start_using_git.step
new file mode 100644
index 000000000..706fc0859
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/start_using_git.step
@@ -0,0 +1,62 @@
+section "Overview" do
+ message <<-MARKDOWN
+### What is Git?
+Git is a version control system (VCS) that allows us to track changes to our application over time.
+By checking your application into git now, you're creating a record of your starting point.
+Whenever you make a change during today's workshop, we'll add it to git before moving on.
+
+### Why use it?
+Most practically, it's what Heroku expects (Heroku is the service we'll be using to put our app online.)
+But more than that, using Git means that if anything ever breaks, or you make a change you don't like, you can use git as an all-powerful "undo" technique.
+But that only works when you remember to commit early and often!
+
+### How does Git work?
+When you make a Git repository and then commit your work to it, it takes a snapshot of your work and saves it.
+Then, if you want to go back to that snapshot, you can! Git also does A LOT MORE, but we'll have to cover that another day.
+
+### Does this have anything to do with GitHub?
+GitHub is a service that allows people to collaborate, and it's very popular with open source projects.
+But Git itself is simply the version control system that GitHub uses, so you can use Git totally separate from GitHub.
+
+ MARKDOWN
+end
+
+steps do
+
+ step do
+ console "git init"
+ message "Now you have a Git repository (or repo for short)."
+ end
+
+ step do
+ console "git status"
+
+ message "`git status` tells you everything git sees as modified, new, or missing."
+ message "The first time you run this, you should see a ton of stuff."
+ end
+
+ step do
+ console "git add ."
+ message "`git add .` tells git that you want to add the current directory (aka `.`) and everything under it to the repo."
+ tip do
+ message <<-MARKDOWN
+With Git, there are usually many ways to do very similar things.
+
+* `git add foo.txt` adds a file named `foo.txt`
+* `git add .` adds all new files and changed files, but *keeps* files that you've deleted
+* `git add -A` adds everything, including deletions
+
+"Adding deletions" may sound weird, but if you think of a version control system as keeping track of *changes*, it might make more sense. Most people use `git add .` but `git add -A` can be safer. No matter what, `git status` is your friend.
+ MARKDOWN
+ end
+ end
+
+ step do
+ console "git commit -m \"Added all the things\""
+ message "`git commit` tells git to actually _do_ all things you've said you wanted to do."
+ message "This is done in two steps so you can group multiple changes together."
+ message "`-m \"Added all the things\"` is just a shortcut to say what your commit message is. You can skip that part and git will bring up an editor to fill out a more detailed message."
+ end
+end
+
+next_step "running_your_application_locally"
diff --git a/sites/suggestotron-sans-scaffolds/suggestotron-sans-scaffolds.step b/sites/suggestotron-sans-scaffolds/suggestotron-sans-scaffolds.step
new file mode 100755
index 000000000..312d26295
--- /dev/null
+++ b/sites/suggestotron-sans-scaffolds/suggestotron-sans-scaffolds.step
@@ -0,0 +1,71 @@
+message <<-MARKDOWN
+### Goal
+
+The goal of this curriculum is to teach you how the various pieces of a Ruby on Rails
+applications work together. You're going to create a voting system for you and your
+friends to play with. You've decided at a minimum, you'd like to
+allow users to:
+
+* view the topics sorted by number of votes
+* vote on topics
+* create, edit, and destroy topics
+
+You've sketched up an initial screenshot of what you want it to look like:
+
+
+
+You may have built the same app before using Rails helpers like `rails generate scaffold`. None of that here! We're going to connect the models, views, and controllers together ourselves, and hopefully you'll have a better idea of how things fit together by the end of today.
+
+### Requirements
+
+We're going to be working with:
+
+* ruby 1.9.3 installed via rvm (mac or linux) or RailsInstaller (mac or windows)
+* rails 3.2.x or rails 4.0.x
+* bundler
+* sqlite
+* the text editor of your choice
+
+Everything should be set up the night before during our
+installfest. Please ensure you have everything working _before_ you
+show up for the workshop on Saturday.
+
+You can verify that you have everything working by trying this out in your terminal:
+
+
+$ irb
+>> 1 + 2
+=> 3
+>> require "active_support"
+=> true
+>> exit
+$
+
+