To teach you Ruby on Rails we are going to use a "Real World"
example. You've decided 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:
What topics do you want to vote on? What races to run in? What theme to have for a party?
Want to see a finished version of the voting system? Visit [introtorails.railsbridgecapetown.org](http://introtorails.railsbridgecapetown.org/).
When you have completed today's goal of getting the basic
application online you should understand:
* Basic Ruby syntax
* How to try your Ruby code (irb)
* How to go from requirements to a new working Rails application
* How to get your application online
* The basic tools a RoR developer uses (source control, editor, console, local server)
* 1-ish hour of ruby
* 4-ish hours of rails, broken up in 1-ish hour steps
This is just a rough guideline, not a mandate. Some steps you'll go
over and some you'll go under. It'll all work out by the end of the
day... unless I really screwed something up. :D
We're going to be working with:
* ruby 1.9.3 or 2.0.0 installed via RVM (Mac or Linux) or RailsInstaller (Mac or Windows)
* rails 4.0.x
* the text editor of your choice
Everything should be set up the night before during our
install-fest. Please ensure you have everything working _before_ you
show up for RailsBridge on Saturday.
You can verify that you have everything working by trying this out in an IRB session:
>> 1 + 2
>> require "active_support"
If you can do that, you are probably good to go. Exit IRB by typing `quit` and then continue.
### Working Effectively and Efficiently
I highly recommend you do the following:
* Bring up your terminal and open 2 tabs:
* One is for regular terminal stuffs
* One will be for irb (aka rails console). We'll explain later
* Open your browser fresh or hide any windows you already have open.
* Bring up one window with two tabs
* One for this content
* One for interacting with your app.
* Open your text editor and _do not ever close it_. We're not quitters.
* Hide all extra applications. Turn off twitter, IM, and all other distractions.
By minimizing the number of things you interact with, you reduce the
amount of time spent switching between them and the context lost as
you work through the lessons. Having 50 tabs open in your web
browser gets confusing and wastes time.
Each lesson will look like this:
<div style="background: white; border: 1px solid black; padding-left: 4em;">
<h1 class="doc_title" style="margin-top: 0em;">Step Title</h1>
<p>Description of the current step.
<p>Red because big goals are scary.
<pre class="term">steps to take.</pre>
1 + 1
<p>Yellow because we've gotten it done, but we have no clue what's going on.
<p>Details of what the steps actually did... spell out the cause and effect.
<p>Green because we can tie everything together now.
If you find something that could be improved, please make a pull request or drop us a note via GitHub Issues (no technical knowledge required).