translate remaining /intro-to-rails pages to zh-tw

Author: yorkxin

sites/zh-tw/intro-to-rails/_consider_deploying.step

@@ -1,7 +1,7 @@
 div :class => "deploying" do
-  h1 "Deploying"
+  h1 "部署（Deploying）"
   blockquote do
-    message "Before the next step, you could try deploying your app to Heroku!"
+    message "在繼續下一步之前，你可以考慮把程式上傳到 Heroku！"
     link 'deploying_to_heroku'
   end
 end

sites/zh-tw/intro-to-rails/allow_people_to_vote.step

@@ -1,11 +1,11 @@
 goals {
-  message "Now we're going to add a button people can click to cast a vote."
+  message "現在我們要來加一個按鈕，讓大家可以按下去就投票加分。"
 }
 
 steps {
 
-  step "Add a new controller action for voting" do
-    message "Edit `app/controllers/topics_controller.rb` to add a method like this:"
+  step "加一個新的 controller action 來投票加分" do
+    message "編輯 `app/controllers/topics_controller.rb` 加一個 method，像這樣："
 
     source_code :ruby, <<-RUBY
       def upvote
@@ -16,19 +16,19 @@ steps {
     RUBY
 
     message <<-MARKDOWN
-      * `@topic = Topic.find(params[:id])` finds the topic in the database with that id and stores it in the variable `@topic`.
-      * `@topic.votes.create` creates a new vote for the current topic and saves it in the database.
-      * `redirect_to(topics_path)` tells the browser to go back to topics_path (the topics list).
+      * `@topic = Topic.find(params[:id])` 從資料庫裡面用 id 找到 topic 然後存進 `@topic` 變數裡面。
+      * `@topic.votes.create` 給目前這篇 topic 新增一筆投票記錄，然後存進資料庫裡面。
+      * `redirect_to(topics_path)` 跟瀏覽器說要回到 topics_path（topics 的列表）。
     MARKDOWN
   end
 
-  step "Add a new route for voting" do
-    message "Open `config/routes.rb` and find the section that looks like this:"
+  step "給投票加分操作加一個 route" do
+    message "打開 `config/routes.rb` 然後找這個："
     source_code :ruby, <<-RUBY
       resources :topics
     RUBY
 
-    message "Replace that line so it looks like this:"
+    message "取代之，讓它長得像這樣："
     source_code :ruby, <<-RUBY
       resources :topics do
         member do
@@ -38,7 +38,7 @@ steps {
     RUBY
 
     message <<-MARKDOWN
-      Verify that route route was added successfully by checking the output of `rake routes` or [http://localhost:3000/rails/info](http://localhost:3000/rails/info). You should see a line that looks like this:
+      現在來檢查 route 有成功加入，方法是看一下 `rake routes` 的輸出結果，或是打開 [http://localhost:3000/rails/info](http://localhost:3000/rails/info)。你應該會看到有一行長得像這樣：
 
       ```
             Prefix Verb   URI Pattern                  Controller#Action
@@ -47,9 +47,9 @@ steps {
     MARKDOWN
   end
 
-  step "Add the button to the view" do
+  step "在 view 裡面加一個按鈕" do
 
-    message "Edit `app/views/topics/index.html.erb` so that the bottom loop looks like this:"
+    message "編輯 `app/views/topics/index.html.erb` 讓最下面的 loop（迴圈）程式碼長得像這樣："
 
     source_code :erb, <<-HTML
       <% @topics.each do |topic| %>
@@ -66,17 +66,17 @@ steps {
     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 text '+1'.
-      * `topic_upvote_path(topic)` creates the appropriate URL for the action we want to invoke. In this case, we want to upvote the current topic.
-        * `topic_upvote_path(topic)` would return `/topics/42/upvote` (if topic.id was 42)
-      * `method: :post` ensures we do the create action of CRUD, not the read action.
+      * `pluralize(topic.votes.count, "vote")` 會輸出票數，並且根據（英文的）單複數在後面加上 'vote' 或 'votes' 單字。
+      * `button_to '+1'` 加一個 HTML 的按鈕（button），裡面有字 '+1'。
+      * `topic_upvote_path(topic)` 產生我們要呼叫的 action 的對應 URL。以此例而言，我們要對目前的 topic 投票加分。
+        * `topic_upvote_path(topic)` 會回傳 `/topics/42/upvote`（如果 topic.id 是 42）。
+      * `method: :post` 確保我們使用了 CRUD 裡面的 create 操作，而非 read。
     MARKDOWN
   end
 
-  step "Confirm your changes in the browser" do
-    message "Go back to <http://localhost:3000/topics> and play."
-    message "Revel in the fact that you didn't have to restart the server to see these changes. Hawt, no?"
+  step "在瀏覽器裡面檢查修改成功" do
+    message "回到 <http://localhost:3000/topics> 然後隨便玩玩看。"
+    message "嗯，你發現了嗎，改程式不用重開 server 哦。酷吧？"
   end
 }
 

sites/zh-tw/intro-to-rails/clean_up_links_on_the_topics_list.step

@@ -1,41 +1,41 @@
 goals {
 
-  message "Our app is nearly done! The main topics listing page is pretty busy. There are a lot of links that aren't necessary."
+  message "我們的程式快要完成了！topics 列表頁看起來很冗。其實有一些連結是無用的。"
 
-  message "Let's clean up the topics list page by doing the following:"
+  message "來清理一下吧："
 
-  goal "Remove the 'show' link"
-  goal "Remove the 'edit' link"
-  goal "Change 'destroy' to 'delete'"
+  goal "拿掉 'show' 超連結。"
+  goal "拿掉 'edit' 超連結。"
+  goal "把 'destroy' 改成 'delete'。"
 }
 
 steps {
-  step "Remove the 'show' and 'edit' links" do
-    message "Open `app/views/topics/index.html.erb` and remove these two lines:"
+  step "拿掉 'show' 和 'edit' 超連結" do
+    message "打開 `app/views/topics/index.html.erb` 刪除這兩行："
     source_code :erb, <<-HTML
 <td><%= link_to 'Show', topic %></td>
 <td><%= link_to 'Edit', edit_topic_path(topic) %></td>
     HTML
   end
 
-  step "Change 'destroy' to 'delete'" do
+  step "把 'destroy' 改成 'delete'" do
 
-    message "Change the line with the word 'Destroy' to this:"
+    message "把有 'Destroy' 字樣的那一行修改成這樣："
     source_code :erb, "<td><%= link_to 'Delete', topic, method: :delete, data: { confirm: 'Are you sure?' } %></td>"
   end
 
-  step "Confirm your changes" do
+  step "確認修改成功" do
 
-    message "Now save your file and try reloading in your browser to see the changes."
+    message "存檔，然後重新整理瀏覽器，看看修改有沒有成功。"
   end
 }
 
 
 explanation {
   message <<-MARKDOWN
-  * The two links we removed were show and edit.  We did this because the title now links to the show page and from the show page you can reach the edit page.
+  * 我們拿掉的兩個超連結是 show 和 edit。這樣做是因為標題已經連到 show 頁面了，在 show 頁面裡面可以連到 edit 頁面。
 
-  * The second change we made was to make the link text 'Delete' instead of destroy.
+  * 第二個修改是把連結文字從 'Destroy' 改成 'Delete'。
   MARKDOWN
 }
 

sites/zh-tw/intro-to-rails/credits_and_next_steps.step

@@ -1,22 +1,23 @@
-message <<MARKDOWN
-Guess what?  _**You're done!!!**_ Congratulations, you just \"finished\" your first rails app!
+message <<-MARKDOWN
+你知道嗎？_**你做完了！！！**_ 賀！你剛「完成」了你的第一個 Rails 程式！
 
-(They're never _really_ ever finished... have fun tweaking it!)
+（嗯……其實沒有*真的*做完，你可以隨便改改看！）
 
-# Extra Credit
+# 加分題
 
-If you got all the way through Suggestotron with some time to spare, here's some extra stuff you can try:
+如果你完成了 Suggestotron 而還剩下一些時間，你可以試試看這些：
 
-* Add a downvote button that does the opposite of what the upvote button does
-* Sort topics by their number of votes
-* Add an 'about' page, linked from the bottom of the Suggestotron topics list. Link back to the Topics list from the About page so users don't get stranded.
-* If your class has a **lot** of time left over:
-  * Users should be allowed to vote only once: give votes a user_id and allow a user to have voted on each topic only once. But wait, what is a 'user' in our system? Get a volunteer to introduce everyone to [Devise](https://github.com/plataformatec/devise), a simple way to add authentication to a Rails application.
+* 加一個「扣分」按鈕，做的事跟加分按鈕相反。
+* 根據投票分數排序 topics。
+* 加一個 'about' 頁面，從 topics 列表的最下面連過去。然後從 About 頁面連回 Topics 列表，這樣使用者才不會卡住。
+* 如果你這次上課剩下**很多**時間，可以試試看：
+  * 限制使用者只能投票一次：在投票記錄加一個 user_id 然後限制每個使用者對每一篇 topic 都只能投票一次。不過首先要定義什麼是「使用者（user）」。你可以請助教來跟大家講一下什麼是 [Devise](https://github.com/plataformatec/devise)，它可以很輕易就在 Rails 程式裡面加入使用者認證系統。
   * Users should be able to give a post a 'negative' vote instead of a positive one. How might you represent that in this system?
+    （[譯註]：似乎跟第一題重複）
 
 MARKDOWN
 
-h1 "Authors"
+h1 "作者群"
 
 ul do
   li "Sarah Allen"
@@ -27,13 +28,13 @@ ul do
   li "...and many, many others"
 end
 
-h1 "What next?"
+h1 "現在往哪裡去？"
 
 ul do
-  li "Probably time for the closing presentation." 
+  li "大概是工作坊的結束時間了。" 
   li "After that, start a project, tutorial, and come back again!"
   li do 
-    span "All our favorite resources can be found on the RailsBridge site: " 
+    span "我們喜歡的學習資源都在 RailsBridge 網站上面可以找到：" 
     a "http://railsbridge.org/learn/resources", href: "http://railsbridge.org/learn/resources"
   end
 end

sites/zh-tw/intro-to-rails/deploying_to_heroku.step

@@ -1,30 +1,30 @@
 h2 do
-  span "If you haven't yet deployed to heroku, start at "
-  a 'First-time setup', href: '#first-time'
+  span "如果你從來沒有把程式 deploy 到 Heroku 過，請看"
+  a '第一次 deploy 的方法', href: '#first-time'
   span ". Otherwise, start at "
-  a 'Every time', href: '#every-time'
+  a 'deploy 新版程式的方法', href: '#every-time'
   span "."
 end
 
 a name: 'first-time'
-situation "First-time setup" do
-  step "Create a heroku application" do
+situation "第一次 deploy 的方法" do
+  step "開新 Heroku 應用程式" do
     console "heroku create"
-    message "`heroku create` registers a new application on heroku's system. You should see some output including your new app's URL."
+    message "`heroku create` 會在 Heroku 的系統裡面註冊新的應用程式。跑完之後你應該會看到輸出裡面告訴你新的應用程式的 URL。"
   end
 
-  step "Edit the Gemfile" do
-    important "Each application has its own `Gemfile`. Be sure you're opening the one inside your app's folder."
+  step "修改 Gemfile" do
+    important "每個 Rails 程式都有他自己的 `Gemfile`。請確定你開的是你的 Rails 程式的 Gemfile。"
 
-    message "Heroku will run our application slightly differently than our development computer does, which requires us to make a small change to our `Gemfile`."
+    message "Heroku 執行我們程式的方法跟我們在本地開發環境執行的方法有點不同，所以我們要改一下 `Gemfile`。"
 
-    message "Open the file called `Gemfile` in Sublime Text, or your preferred editor, and find the line containing:"
+    message "在編輯器打開 `Gemfile`，找這一行："
 
     source_code :ruby, <<-RUBY
 gem 'sqlite3'
     RUBY
 
-    message "**Remove that line** and replace it with:"
+    message "**刪除那一行**，改成這樣："
 
     source_code :ruby, <<-RUBY
 group :development, :test do
@@ -38,74 +38,78 @@ end
     RUBY
   end
 
-  step "Apply the Gemfile changes" do
+  step "套用 Gemfile 的異動" do
     console "bundle install --without production"
-    message "Every time the Gemfile changes, you need to run ``bundle install`` for the changes to be processed. The processed version of the changes is stored in another file called ``Gemfile.lock``."
+    message "每當你改 Gemfile 的時候，你都要跑一次 ``bundle install``，這樣子異動才會被套用。套用之後的異動會被存在另一個檔案 ``Gemfile.lock``。"
   end
 
-  step "Commit the Gemfile changes" do
-    message "There are now changes to Gemfile and Gemfile.lock that need to be committed before we can push to heroku."
+  step "把 Gemfile 的異動 commit 進 git" do
+    message "現在 Gemfile 和 Gemfile.lock 修改過了，在上傳到 Heroku 之前，我們要把這些異動 commit 進 git。"
     console <<-SHELL
 git add .
-git commit -m "Changed Gemfile for heroku"
+git commit -m "改 Gemfile 來適應 heroku"
     SHELL
-    tip "There is a period after the word add in the first line."
+    tip "第一行指令的最後面有一個小數點符號。"
   end
 end
 
 a name: 'every-time'
-situation "Every time" do
-  step "Commit any pending changes to git" do
-    message "Heroku will only receive the files we've committed into our local git repository. So we need to make sure all changed files have been committed."
+situation "deploy 新版程式的方法" do
+  step "把所有異動都 commit 進 git" do
+    message "Heroku 只受理我們有 commit 進本地 git repo 的程式，所以要確定修改過的檔案都有 commit 進去了。"
     console "git status"
-    message "`git status` shows you any pending changes you've created. If it has no output, you're already ready to deploy! Otherwise..."
+    message "`git status` 顯示你還沒 commit 進 git 的異動。如果沒有輸出任何東西的話，那你可以 deploy 了！不然的話就要 commit 程式碼進去："
 
     console <<-SHELL
 git add .
 git commit -m "Some helpful message for your future self"
     SHELL
-    message "Your commit message should reference whatever your outstanding changes are: something like 'added votes to the topics index'."
+    message "Commit message 應該要可以描述你這次修改了什麼東西，像是：「把投票數加到 topics 列表頁」"
   end
 
-  step "Push changes to heroku" do
+  step "把異動 push（上傳）到 Heroku" do
     console "git push heroku master"
-    message "This takes all changes you've committed locally and pushes them to heroku."
+    message "這樣子會把本地所有已經 commit 進去的異動都 push 到 Heroku。"
   end
 
-  step "Run database migrations on Heroku" do
+  step "在 Heroku 跑資料庫的 migration" do
     console "heroku run rake db:migrate"
-    message "This tells Heroku to run your migrations on its database, like running rake db:migrate locally. Heroku's database is separate from the one on your computer, which means it needs to be updated every time you make changes to the structure of your database.  It also means that you'll not see any of the data you entered into the sqlite3 database on your computer."
+    message "這是叫 Heroku 在它的資料庫跑 migration，作用就像我們在本地跑 rake db:migrate。Heroku 的資料庫跟你電腦上的資料庫是分開的，也就是說每一次你更改了資料庫的結構，你都要在 Heroku 的資料庫更新一次。這也就是說在 Heroku 上面你不會看到你電腦上的 sqlite3 資料庫裡面的資料。"
   end
 
-  step "Visit your application" do
+  step "上網看你的程式" do
     console "heroku open"
-    message "This opens the new application in your browser."
+    message "會在瀏覽器打開你上傳到 Heroku 的程式。"
   end
 end
 
 explanation do
   message <<-MARKDOWN
-  First, we had to do some work to make Heroku happy with our application. This required updating the Gemfile and bundling.
-
-  * The Gemfile is a list of all the Ruby libraries your application needs.
-    What we've declared here is that we want to use the `sqlite3` library
-    while we're developing on our computer (the development group) but when
-    deploying to heroku (the production group) we want to use the `pg` library,
-    which is made for the type of database that heroku uses.
-
-  * Bundler is how Ruby projects keep track of the gems that they use. We told
-    bundler what we wanted to use in the `Gemfile`, now we need to make sure those
-    gems are installed. Since we don't have the type of database heroku does, we
-    skip the production gems. Don't worry though! Bundler still logs them so
-    Heroku will install them when they get your code.
+  首先，我們要讓 Heroku 跟我們的程式可以整合。這需要修改 Gemfile 和重跑 bundler。
+
+  * Gemfile 這個檔案列出了所有你的 Rails 程式所需要的 Ruby 程式庫（Library），稱為**「gem」**。
+    我們這裡宣告的是說，要在自己電腦的開發環境使用 `sqlite3` gem（寫在 development group 裡面），
+    但是在上傳到 Heroku（production group）的時候要使用 `pg` gem，這是專門設計給 Heroku 使用的資料庫。
+
+  * Bundler 是 Ruby 專案用來追蹤有使用哪些 gem 的工具。我們透過 `Gemfile` 跟 Bundler
+    說我們要什麼 gem，然後我們要確定這些 gem 都有安裝。因為我們目前電腦裡面沒有 Heroku 用的資料庫系統，
+    所以我們跳過不安裝 production 用的 gem。別擔心，Bundler 還是會幫我們記得，讓 Heroku 幫你安裝。
   MARKDOWN
 
-  message "You should be able to deploy your application any time it's in a good, working state. Your typical workflow will look like:"
+  message "你可以在任何你的程式沒問題、會動的時候 deploy。標準流程長得像這樣："
   img src: "img/workflow.png", alt: "workflow", style: "border: none"
   ol do
-    li { message "Add or change some code" }
-    li { message "Commit your changes (`git commit`)" }
-    li { message "(repeat)" }
+    li { message "改程式" }
+    li { message "把異動 commit 進 git（`git commit`）" }
+    li { message "（重複）" }
   end
-  message "Any time your changes are committed, you should feel free to `git push heroku master` and boom! Your changes are live!"
+  message "每當你把異動 commit 進 git 之後，你都可以執行 `git push heroku master`，然後新版本就上線了！"
 end
+
+
+
+
+
+
+
+