Five of the twelve things Google attaches to the name "ruby on rails" are navigational: documentation, github, wiki, download, creator. Google answers those with the official property, and it is right to. So this page is not competing with them. It is the map that nobody writes: which of the official-looking sources is current, which is a historical artefact, and which one to open for which kind of question. Every address below was opened on 21 September 2026, and what it did is what is reported here. The other seven questions are on the pillar, Ruby on Rails, answered.
Ruby on Rails documentation is two sites, not one
The official documentation lives at two addresses, and opening the wrong one is the single most common way a Rails question stays unanswered for an hour.
The Rails Guides are prose. Each guide takes one subject, Active Record queries or Action Mailer or the asset pipeline, and walks it from nothing to working, with the code you would actually write. The index is grouped by where you are: Start Here, Models, Views, Controllers, then Digging Deeper and Going to Production. Guides are what you want when the question has the shape "how do I do X in Rails", and they are the reason the framework can be picked up at all without a course. If you are weighing that, Is Ruby on Rails hard to learn takes the question properly.
The API documentation is generated from the source. It is organised by class rather than by subject: every public method of Active Record, Active Model, Action Pack, Action View, Action Mailer, Action Mailbox, Active Job, Action Cable, Active Storage, Action Text and Active Support, with its arguments, its options and its return value. That is what you want when you already know the method and need to know what it accepts, and it is the wrong door for "how does caching work".
Both sites document Rails 8.1.3.1 as of today, and both are versioned, which matters more than it sounds. The guides carry a selector running from Edge down to 2.3, so guides.rubyonrails.org/v7.1/index.html is the 7.1 edition of the same page. The API does the same at api.rubyonrails.org/v7.1/, and the unreleased main branch is documented at edgeguides.rubyonrails.org and edgeapi.rubyonrails.org. A guide that flatly contradicts your application is usually not wrong, it is pinned to a version you do not run, and the fix is the selector rather than a second search.
Reading the Rails source on GitHub
The Ruby on Rails GitHub repository is github.com/rails/rails, MIT licensed, default branch main. What you find at the top level is one directory per framework: activerecord, actionpack, actionview, activesupport, actionmailer, actionmailbox, activejob, actioncable, activestorage, actiontext, activemodel, plus railties, which is the part that turns those into an application. Knowing that layout is most of knowing where to look, because a Rails method belongs to exactly one of those directories.
Reading the source is a realistic thing to do here, which is not true of every framework. Rails is Ruby, not a compiled artefact, so the code the documentation describes is the code you can open, and the API documentation makes the trip for you: each documented method carries a source link to its exact line on GitHub, pinned to the commit the docs were built from. Following one lands you in activerecord/lib/active_record/relation.rb at the line that implements the method you were reading about.
The same code is already on your disk. Rails arrives as gems, so bundle open activerecord opens the installed copy of that framework in your editor, at the version your Gemfile.lock actually resolved. When behaviour and documentation disagree, that copy is the tiebreaker, because it is the one your application is running.
Reading a framework is a different exercise from reading an application built on it, and the second one teaches more at the start. A Ruby on Rails example application walks one of those.
What became of the Ruby on Rails wiki
The wiki people search for is gone, and gone in the strong sense rather than the neglected sense. wiki.rubyonrails.org does not resolve: a DNS lookup on 21 September 2026 returns NXDOMAIN, meaning the hostname no longer exists at all, so there is nothing to load and no redirect to follow. The wiki tab on the rails/rails repository is closed too, and github.com/rails/rails/wiki answers with a redirect back to the repository front page.
What the official record shows is that there were at least two of them. A post on the Rails blog dated 10 February 2009, The State of the Wiki by Mike Gunderloy, announces a relaunched wiki and describes its predecessor as having "gone from being a comfortable spot to find out a few things to a cluttered mess over the years". When and why the hostname itself was finally retired is not something this page could establish from a primary source, so it is not claimed here.
Two practical consequences. First, most people typing "ruby on rails wiki" today are looking for an encyclopedia entry rather than a community wiki, and the thing they land on is the English Wikipedia article, which is a reasonable place for history and a bad place for how-to. Second, the role a wiki used to play is now the guides', which are versioned and reviewed in a way a wiki never was. A framework whose community wiki fell off the internet is also the kind of fact that makes people ask whether anybody still uses Ruby on Rails, and that question deserves its own answer rather than an inference from a dead hostname.
Ruby on Rails download is not a download
Rails is a gem, which is why this search exists and why it has no satisfying answer. There is no installer, no archive, no versioned zip file, and rubyonrails.org/download returns a 404 because the page it implies was never the shape of the thing.
What the official installation guide actually tells you to do is install Ruby first, using the mise version manager on both macOS and Linux, and then run one command:
gem install rails
rails new myapp
cd myapp
bin/rails server
The gem that command fetches is rails on RubyGems, at 8.1.3.1 released on 29 July 2026, requiring Ruby 3.2.0 or newer. Worth noticing what the install does not ask for: the guide never tells you to install Node or a JavaScript runtime, which is a real change from the Rails of a few years ago and one of the things at stake in Ruby on Rails vs JavaScript.
The second half of the answer is that you rarely install Rails again after the first time. Each application pins its own Rails version in its Gemfile, and bundle install resolves that version for that application, so two projects on one machine happily run two different Rails releases. The globally installed gem exists mostly so that rails new has something to run.
Who created Ruby on Rails
David Heinemeier Hansson created Ruby on Rails, and the official Rails Foundation page for 37signals is the place that says so plainly: 37signals "is the birthplace of Rails, which was started in 2003 to build Basecamp", and Hansson is described there as 37signals co-founder and CTO, creator of Ruby on Rails, and chairman of the foundation. Basecamp is the project management product the framework was extracted from, and 37signals is the company that built it.
Rails 1.0 was announced on the Rails blog on 13 December 2005. The first public release came earlier, in 2004, and the month is left unstated here because the sources consulted for this page do not agree on it.
Which source to open for which question
One mapping, worth keeping: a question about how something works goes to the guides; a question about what a method takes or returns goes to the API documentation; a question about what Rails genuinely does, as opposed to what it says it does, goes to the source or to the copy of it already installed on your machine; a question about installing goes to the installation guide rather than to any page with the word download on it; and a question about history or people goes to the Wikipedia article and the foundation site, neither of which will teach you Rails.
Five of the twelve things Google attaches to the name "ruby on rails" are navigational: documentation, github, wiki, download, creator. Google answers those with the official property, and it is right to. So this page is not competing with them. It is the map that nobody writes: which of the official-looking sources is current, which is a historical artefact, and which one to open for which kind of question. Every address below was opened on 21 September 2026, and what it did is what is reported here. The other seven questions are on the pillar, Ruby on Rails, answered.
Ruby on Rails documentation is two sites, not one
The official documentation lives at two addresses, and opening the wrong one is the single most common way a Rails question stays unanswered for an hour.
The Rails Guides are prose. Each guide takes one subject, Active Record queries or Action Mailer or the asset pipeline, and walks it from nothing to working, with the code you would actually write. The index is grouped by where you are: Start Here, Models, Views, Controllers, then Digging Deeper and Going to Production. Guides are what you want when the question has the shape "how do I do X in Rails", and they are the reason the framework can be picked up at all without a course. If you are weighing that, Is Ruby on Rails hard to learn takes the question properly.
The API documentation is generated from the source. It is organised by class rather than by subject: every public method of Active Record, Active Model, Action Pack, Action View, Action Mailer, Action Mailbox, Active Job, Action Cable, Active Storage, Action Text and Active Support, with its arguments, its options and its return value. That is what you want when you already know the method and need to know what it accepts, and it is the wrong door for "how does caching work".
Both sites document Rails 8.1.3.1 as of today, and both are versioned, which matters more than it sounds. The guides carry a selector running from Edge down to 2.3, so
guides.rubyonrails.org/v7.1/index.htmlis the 7.1 edition of the same page. The API does the same atapi.rubyonrails.org/v7.1/, and the unreleased main branch is documented at edgeguides.rubyonrails.org and edgeapi.rubyonrails.org. A guide that flatly contradicts your application is usually not wrong, it is pinned to a version you do not run, and the fix is the selector rather than a second search.Reading the Rails source on GitHub
The Ruby on Rails GitHub repository is github.com/rails/rails, MIT licensed, default branch
main. What you find at the top level is one directory per framework:activerecord,actionpack,actionview,activesupport,actionmailer,actionmailbox,activejob,actioncable,activestorage,actiontext,activemodel, plusrailties, which is the part that turns those into an application. Knowing that layout is most of knowing where to look, because a Rails method belongs to exactly one of those directories.Reading the source is a realistic thing to do here, which is not true of every framework. Rails is Ruby, not a compiled artefact, so the code the documentation describes is the code you can open, and the API documentation makes the trip for you: each documented method carries a source link to its exact line on GitHub, pinned to the commit the docs were built from. Following one lands you in
activerecord/lib/active_record/relation.rbat the line that implements the method you were reading about.The same code is already on your disk. Rails arrives as gems, so
bundle open activerecordopens the installed copy of that framework in your editor, at the version your Gemfile.lock actually resolved. When behaviour and documentation disagree, that copy is the tiebreaker, because it is the one your application is running.Reading a framework is a different exercise from reading an application built on it, and the second one teaches more at the start. A Ruby on Rails example application walks one of those.
What became of the Ruby on Rails wiki
The wiki people search for is gone, and gone in the strong sense rather than the neglected sense.
wiki.rubyonrails.orgdoes not resolve: a DNS lookup on 21 September 2026 returns NXDOMAIN, meaning the hostname no longer exists at all, so there is nothing to load and no redirect to follow. The wiki tab on the rails/rails repository is closed too, andgithub.com/rails/rails/wikianswers with a redirect back to the repository front page.What the official record shows is that there were at least two of them. A post on the Rails blog dated 10 February 2009, The State of the Wiki by Mike Gunderloy, announces a relaunched wiki and describes its predecessor as having "gone from being a comfortable spot to find out a few things to a cluttered mess over the years". When and why the hostname itself was finally retired is not something this page could establish from a primary source, so it is not claimed here.
Two practical consequences. First, most people typing "ruby on rails wiki" today are looking for an encyclopedia entry rather than a community wiki, and the thing they land on is the English Wikipedia article, which is a reasonable place for history and a bad place for how-to. Second, the role a wiki used to play is now the guides', which are versioned and reviewed in a way a wiki never was. A framework whose community wiki fell off the internet is also the kind of fact that makes people ask whether anybody still uses Ruby on Rails, and that question deserves its own answer rather than an inference from a dead hostname.
Ruby on Rails download is not a download
Rails is a gem, which is why this search exists and why it has no satisfying answer. There is no installer, no archive, no versioned zip file, and
rubyonrails.org/downloadreturns a 404 because the page it implies was never the shape of the thing.What the official installation guide actually tells you to do is install Ruby first, using the mise version manager on both macOS and Linux, and then run one command:
The gem that command fetches is rails on RubyGems, at 8.1.3.1 released on 29 July 2026, requiring Ruby 3.2.0 or newer. Worth noticing what the install does not ask for: the guide never tells you to install Node or a JavaScript runtime, which is a real change from the Rails of a few years ago and one of the things at stake in Ruby on Rails vs JavaScript.
The second half of the answer is that you rarely install Rails again after the first time. Each application pins its own Rails version in its Gemfile, and
bundle installresolves that version for that application, so two projects on one machine happily run two different Rails releases. The globally installed gem exists mostly so thatrails newhas something to run.Who created Ruby on Rails
David Heinemeier Hansson created Ruby on Rails, and the official Rails Foundation page for 37signals is the place that says so plainly: 37signals "is the birthplace of Rails, which was started in 2003 to build Basecamp", and Hansson is described there as 37signals co-founder and CTO, creator of Ruby on Rails, and chairman of the foundation. Basecamp is the project management product the framework was extracted from, and 37signals is the company that built it.
Rails 1.0 was announced on the Rails blog on 13 December 2005. The first public release came earlier, in 2004, and the month is left unstated here because the sources consulted for this page do not agree on it.
Which source to open for which question
One mapping, worth keeping: a question about how something works goes to the guides; a question about what a method takes or returns goes to the API documentation; a question about what Rails genuinely does, as opposed to what it says it does, goes to the source or to the copy of it already installed on your machine; a question about installing goes to the installation guide rather than to any page with the word download on it; and a question about history or people goes to the Wikipedia article and the foundation site, neither of which will teach you Rails.