Permalink
Browse files

remove trailing whitespace

  • Loading branch information...
1 parent acaaffe commit a764303941c83324b4c5b42b54d32489026334ae @hsbt hsbt committed Jan 25, 2014
View
@@ -1,4 +1,4 @@
-<!doctype html>
+<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
@@ -56,7 +56,7 @@ __COACH__: You can talk about RDBMS and the different ones out there, plus inclu
#### Adding rails\_12factor
-Next, we need to add rails\_12factor entry into our Gemfile to make our app available on Heroku.
+Next, we need to add rails\_12factor entry into our Gemfile to make our app available on Heroku.
This gem modifies the way Rails works to suit Heroku, for example Logging is updated and the configuration for static assets (your images, stylesheets and javascript files) is tweaked to work properly within Heroku's systems.
@@ -24,7 +24,7 @@ bundle install
## Step 2: Create comment scaffold
-Create comment scaffold, with the commentator name, the comment body (contents of the comment) and with the reference to the ideas table (idea_id).
+Create comment scaffold, with the commentator name, the comment body (contents of the comment) and with the reference to the ideas table (idea_id).
{% highlight sh %}
rails g scaffold comment user_name:string body:text idea_id:integer
{% endhighlight %}
@@ -53,8 +53,8 @@ rails s
## Step 4: Add relations to models
-You need to make sure that Rails knows the connection between objects (ideas and comments).
-As one idea can have many comments we need to make sure the idea model knows that.
+You need to make sure that Rails knows the connection between objects (ideas and comments).
+As one idea can have many comments we need to make sure the idea model knows that.
Open app/models/idea.rb and after the row
{% highlight ruby %}
class Idea < ActiveRecord::Base
@@ -118,7 +118,7 @@ add the row
<%= f.hidden_field :idea_id %>
{% endhighlight %}
-next, remove
+next, remove
{% highlight erb %}
<div class="field">
<%= f.label :idea_id %><br>
@@ -70,7 +70,7 @@ have weren't affected. So edit one of the existing ideas and re-add a picture.
## Displaying the thumbnails
To see if the uploaded picture was resized open
-`app/views/ideas/index.html.erb`. Change the line
+`app/views/ideas/index.html.erb`. Change the line
{% highlight erb %}
<td><%= idea.picture %></td>
@@ -12,7 +12,7 @@ Now the app is running well, but it still looks like scaffold. Let's add some de
## Step 1: Adjust the application layout
-First, let's use bootstrap.min.css to apply a more lightweight style set to your app.
+First, let's use bootstrap.min.css to apply a more lightweight style set to your app.
Open `app/views/layouts/application.html.erb` in your text editor and replace the line
@@ -38,7 +38,7 @@ with
body { padding-top: 60px; }
{% endhighlight %}
-Finally, delete the file `app/assets/stylesheets/scaffolds.css.scss` because we don't really need the default style generated by Rails.
+Finally, delete the file `app/assets/stylesheets/scaffolds.css.scss` because we don't really need the default style generated by Rails.
Now refresh the page at [http://localhost:3000/ideas](http://localhost:3000/ideas). You will not find much change but it's good preparation for the following steps.
@@ -83,7 +83,7 @@ Open `app/views/ideas/index.html.erb` in your text editor and replace all lines
**Coach:** Explain what the new code means line by line, and talk a little about Bootstrap 12 grids layout.
-Refresh it! We get a nice looking idea list. Click the "New Idea" button, and create more ideas with real text and pretty pictures - the page will look much better with content. There is a principle of contemporary web design: content is the best decoration.
+Refresh it! We get a nice looking idea list. Click the "New Idea" button, and create more ideas with real text and pretty pictures - the page will look much better with content. There is a principle of contemporary web design: content is the best decoration.
## Step 4: Design the idea details page
@@ -32,12 +32,12 @@ Rails Girls workshops give the first experience in software craftsmanship throug
### Time to complete app
-There's loads of time to complete the app, and so it is more important to slowly explain what is happening in each step, as it is a lot of copy pasting and if attendees rush through the guide, they will be done soon but not understand at all what happened.
-<br> There's a LOT (4-5) h reserved for the app, tweaking it and putting it online for others to see so there is no hurry :)
+There's loads of time to complete the app, and so it is more important to slowly explain what is happening in each step, as it is a lot of copy pasting and if attendees rush through the guide, they will be done soon but not understand at all what happened.
+<br> There's a LOT (4-5) h reserved for the app, tweaking it and putting it online for others to see so there is no hurry :)
### Swag
-Believe it or not, for most, it is really important. It makes the environment different. You decide how, but little crafts (making buttons), stickers, cupcakes, balloons, posters, or anything you can come up with makes all the difference.
+Believe it or not, for most, it is really important. It makes the environment different. You decide how, but little crafts (making buttons), stickers, cupcakes, balloons, posters, or anything you can come up with makes all the difference.
### Inclusivity
@@ -47,38 +47,38 @@ Rails Girls is a an inclusive, safe and welcoming experience to everyone. The wo
### What if I've never done anything in Rails?
-Why haven't you yet? Just kidding. That's not a problem at all, we've had a lot of coaches just like you and they were *super awesome*. As long as you're comfortable with any other similar framework, you'll be fine. Take a look at the [basic app guide][app] and you'll probably be able to figure out what's going on pretty soon. Pay attention to the "**Coach**" bits that tell you what you should be able to explain.
+Why haven't you yet? Just kidding. That's not a problem at all, we've had a lot of coaches just like you and they were *super awesome*. As long as you're comfortable with any other similar framework, you'll be fine. Take a look at the [basic app guide][app] and you'll probably be able to figure out what's going on pretty soon. Pay attention to the "**Coach**" bits that tell you what you should be able to explain.
-Usually there'll be at least somebody at the event who works with Rails on a regular basis, so don't be afraid to ask for help when bundle installs go all weird on you. Also, if you come across something unusual, just Google it with your group! It's ok to admit that you don't know everything and show the girls how you use Google to solve your everyday programming dilemmas.
+Usually there'll be at least somebody at the event who works with Rails on a regular basis, so don't be afraid to ask for help when bundle installs go all weird on you. Also, if you come across something unusual, just Google it with your group! It's ok to admit that you don't know everything and show the girls how you use Google to solve your everyday programming dilemmas.
### What exactly will I be doing as a coach?
-The structure of workshop varies a bit from city to city, so your local organizer group will be able you to guide you through the details. Usually there's a pre-event meeting or dinner with coaches where you can ask all you questions.
+The structure of workshop varies a bit from city to city, so your local organizer group will be able you to guide you through the details. Usually there's a pre-event meeting or dinner with coaches where you can ask all you questions.
### Answering questions
-Often coaches who are just one step ahead of attendees are the best at explaining :) Use real life metaphors and explain very high-level. Explaining too deep will cause a flood of information that is not necessary at the beginning.
+Often coaches who are just one step ahead of attendees are the best at explaining :) Use real life metaphors and explain very high-level. Explaining too deep will cause a flood of information that is not necessary at the beginning.
#### Installation Party
-Generally speaking, the Rails Girls workshops begin with an Installation party during which you'll be asked to help girls [install the required software][install] (Rails and a text editor). You don't have to be an expert on all operating systems, but you can help on those you are familiar with.
+Generally speaking, the Rails Girls workshops begin with an Installation party during which you'll be asked to help girls [install the required software][install] (Rails and a text editor). You don't have to be an expert on all operating systems, but you can help on those you are familiar with.
#### Helping girls build their first app
During the following day, you will be the star of the show and help your group of anywhere from 2 to 5 girls build their first [web app][app] in Rails with the help of the tutorial. Usually that happens just after the initial batch of lectures sometime after 11 AM (aka they'll serve you coffee first).
Going through the tutorial on your own at home will usually be all the preparation you need. The girls will have the app guide open on their screens, so just guide them through the process, providing explanations of what's going on at each step. The explanations shouldn't be highly technical; try to simplify the answer by providing easy to remember metaphors. And remember that there is no such thing as a stupid question at a Rails Girls workshop! Let girls know they can ask you about anything along the way; you can spend more time on parts they find more interesting.
-Also, don't be discouraged if you'll sometimes need to try a few different explanations. Most girls will be beginners, so they won't have many existing points of reference (bonus point: nor will they have any bad habits some programmers tend to pick up along the way). If you get to the end of the basic app tutorial, you can explore additional guides at the end or work on whatever your group is most interested in; design is usually a popular choice, but some girls will want to try building another app. You can also prepare your own challenges for girls or explore helpful resources (documentation etc).
+Also, don't be discouraged if you'll sometimes need to try a few different explanations. Most girls will be beginners, so they won't have many existing points of reference (bonus point: nor will they have any bad habits some programmers tend to pick up along the way). If you get to the end of the basic app tutorial, you can explore additional guides at the end or work on whatever your group is most interested in; design is usually a popular choice, but some girls will want to try building another app. You can also prepare your own challenges for girls or explore helpful resources (documentation etc).
If you need help with anything, don't be afraid to use Google or ask another coach to help you out. And don't be afraid to ask for a break if you need it, it's going to be a long day, but we can promise you'll get home with a big smile and a warm heart :)
* Check Lucy Bain's additional [teaching notes to the app](https://github.com/lbain/railsgirls)
### Are you in?
-Good, we're happy to have you on board! Get in touch with organizers of your local event (if you aren't already) and they'll answer all the other questions you might have. You can usually find their contact info on the event's page.
+Good, we're happy to have you on board! Get in touch with organizers of your local event (if you aren't already) and they'll answer all the other questions you might have. You can usually find their contact info on the event's page.
-If you're traveling abroad at the time of a Rails Girls workshop, do feel free to contact the organizers of the city you'll be visiting; we're always happy to welcome additional coaches! Not to mention that a Rails Girls workshop is a great excuse to visit a new city ;)
+If you're traveling abroad at the time of a Rails Girls workshop, do feel free to contact the organizers of the city you'll be visiting; we're always happy to welcome additional coaches! Not to mention that a Rails Girls workshop is a great excuse to visit a new city ;)
Some other great first-hand tips from Rails Girls coaches:
@@ -18,10 +18,10 @@ permalink: github
* In the terminal type `git --version` (1.8 or higher preferred)
* If not, download Git [here] (http://git-scm.com/downloads).
- Then, setup your local Git profile - In the terminal:
+ Then, setup your local Git profile - In the terminal:
* Type `git config --global user.name "your-name"`
* Type `git config --global user.email "your-email"`
-
+
* _To check if Git is already config-ed you can type_ `git config --list`
* Create a free [GitHub](https://github.com) account or login if you already have one
@@ -36,9 +36,9 @@ In the command line--make sure you `cd` into your railgirls folder--and type:
`git init`
-This initializes a git repository in your project
+This initializes a git repository in your project
-*Note:* If you've already done the [Heroku guide](/heroku), then you've already initialized a git repository & you can move on to the next steps.
+*Note:* If you've already done the [Heroku guide](/heroku), then you've already initialized a git repository & you can move on to the next steps.
Next type:
@@ -52,7 +52,7 @@ Then type:
`git status`
-This will list out all the files in your working directory.
+This will list out all the files in your working directory.
**COACH:** Talk about some of your favorite git commands
@@ -68,9 +68,9 @@ Then type:
This commits all of your files, adding the message "first commit"
-Next type:
+Next type:
-`git remote add origin https://github.com/username/rails-girls.git`
+`git remote add origin https://github.com/username/rails-girls.git`
_Your GitHub Repository page will list the repository URL, so feel free to copy and paste from there, rather than typing it in manually. You can copy and paste the link from your GitHub repository page by clicking the clipboard icon next to the URL._
@@ -82,7 +82,7 @@ Then type:
This sends your commits in your "master" branch to GitHub
-Congratulations your app is on GitHub! Go check it out by going to the same url you used above: https://github.com/username/rails-girls (without the .git part)
+Congratulations your app is on GitHub! Go check it out by going to the same url you used above: https://github.com/username/rails-girls (without the .git part)
If you want to continue making changes and pushing them to GitHub you'll just need to use the following three commands:
@@ -95,7 +95,7 @@ If you want to continue making changes and pushing them to GitHub you'll just ne
## What's next?
### Be a Part of the Open Source Community
-
+
* Follow your fellow Rails Girls & coaches on GitHub
* Star or watch their projects
* [Fork](https://help.github.com/articles/fork-a-repo) a repo, then clone and push changes to your fork. Share the changes with the originator by sending them a [pull request](https://help.github.com/articles/using-pull-requests)!
@@ -107,7 +107,7 @@ If you want to continue making changes and pushing them to GitHub you'll just ne
* Check out [trygit.org](http://try.github.io/)
* Use a [Git Cheatsheet](https://na1.salesforce.com/help/doc/en/salesforce_git_developer_cheatsheet.pdf)
* Look up Git Commands at [git-scm.org](http://git-scm.com/)
-
+
Oops, something went wrong.

0 comments on commit a764303

Please sign in to comment.