10 |
63 |
64 |
11 |
13 | Code of Conduct
12 |
14 |
62 | 15 | As contributors and maintainers of this project, and in the interest of 16 | fostering an open and welcoming community, we pledge to respect all people 17 | who contribute through reporting issues, posting feature requests, updating 18 | documentation, submitting pull requests or patches, and other activities. 19 |
20 | 21 |22 | We are committed to making participation in this project a harassment-free 23 | experience for everyone, regardless of level of experience, gender, gender 24 | identity and expression, sexual orientation, disability, personal appearance, 25 | body size, race, ethnicity, age, religion, or nationality. 26 |
27 | 28 |29 | Examples of unacceptable behavior by participants include: 30 |
31 | 32 |-
33 |
- The use of sexualized language or imagery 34 |
- Personal attacks 35 |
- Trolling or insulting/derogatory comments 36 |
- Public or private harassment 37 |
- Publishing other's private information, such as physical or electronic addresses, without explicit permission 38 |
- Other unethical or unprofessional conduct. 39 |
42 | The Rails core team have the right and responsibility to remove, edit, or 43 | reject comments, commits, code, wiki edits, issues, and other contributions 44 | that are not aligned to this Code of Conduct. 45 |
46 | 47 |48 | We commit to fairly and consistently applying these principles to every aspect 49 | of managing this project. Project maintainers who do not follow or enforce the 50 | Code of Conduct may be permanently removed from the project team. 51 |
52 | 53 |54 | This code of conduct applies both within project spaces and in public spaces 55 | when an individual is representing the project or its community. 56 |
57 | 58 |59 | This Code of Conduct is adapted from the Contributor Covenant, version 1.2.0. 60 |
61 |
65 |
76 |
77 |
66 |
68 | Reporting Issues
67 |
69 |
75 | 70 | Instances of abusive, harassing, or otherwise unacceptable behavior should be 71 | reported by sending an email to conduct@rubyonrails.org. 72 | We are here to help. 73 |
74 |
78 |
87 |
--------------------------------------------------------------------------------
/core/alumni/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Core Alumni"
3 | header: "The core alumni"
4 | subheader_1: "Retired members of the core team who are no longer"
5 | subheader_2: "active in the day-to-day improvement of the framework."
6 | subheader_3: "We thank you dearly for your service over the years."
7 | ---
8 |
79 |
81 | Revisions
80 |
82 |
86 | 83 | For a history of updates and revisions to this policy, see the page history. 84 |
85 |
9 |
10 |
23 |
24 |
11 | 
12 |
13 |
12 |
14 |
22 | 15 | Yehuda Katz is a member of the Ember.js and 16 | jQuery Core Teams; during the daytime, he works at Tilde. 17 | Yehuda is the co-author of the best-selling jQuery in Action, Rails 3 in Action, 18 | and is a contributor to Ruby in Practice. He blogs at yehudakatz.com 19 | and can be found on Twitter as @wycats. 20 |
21 |
25 |
38 |
39 |
26 | 
27 |
28 |
27 |
29 |
37 | 30 | Jon Leighton is Tech Director at Loco2. 31 | During his time on the core team he did a bunch of work on Active Record and created the 32 | Spring preloader. These days he spends lots 33 | of time rock climbing. You can follow 34 | @jonleighton. 35 |
36 |
40 |
49 |
50 |
41 | 
42 |
43 |
42 |
44 |
48 | 45 | Josh Peek (joshp) has been working with almost all parts of Rails. A lot of work spent on performance and thread safety for Action Pack. Josh works at GitHub. 46 |
47 |
51 |
60 |
61 |
52 | 
53 |
54 |
53 |
55 |
59 | 56 | Carl Lerche is a Platform Architect at Strobe, where he runs a top-notch product engineering team and hacks on Strobe Platform. He’s been programming for as long as he can remember, and focused on Ruby development since 2005. He is a member of the Ruby on Rails Core Team and speaker at numerous industry conferences and events. He lives in downtown San Francisco and has a fondness for quality Belgian Beers... and pie. Follow him on Twitter at @carllerche. 57 |
58 |
62 |
72 |
73 |
63 | 
64 |
65 |
64 |
66 |
71 | 67 | Pratik Naik (lifo) stumbled upon Rails back in 2006 while in search 68 | for a better web framework after 2 painful years with perl/mod_perl. He hasn’t looked back since then. Currently located in London, he is an employee of Basecamp and maintains a personal blog at http://m.onkey.org. 69 |
70 |
74 |
88 |
89 |
75 | 
76 |
77 |
76 |
78 |
87 | 79 | Jamis Buck (minam) is a repentant Java programmer who never really enjoyed Java, but who finally found web-programming joy in Rails. 80 | He is an avid Ruby programmer, having contributed several packages to the community (including Net::SSH, 81 | Net::SFTP, Syntax, 82 | sqlite-ruby, sqlite3-ruby, 83 | SwitchTower and others). 84 | He lives with his wife Tarasine and four children in Idaho. 85 |
86 |
90 |
103 |
104 |
91 | 
92 |
93 |
92 |
94 |
102 | 95 | Marcel Molina Jr. (noradio) is a language enthusiast 96 | who went from being a literature major to a programmer. In his transition from 97 | natural language to machine language he found Ruby an elegant balance of 98 | dynamic, pragmatic and “humane”. And then came along Rails… Marcel works at 99 | twitter and tumblelogs at Projectionist. 100 |
101 |
105 |
117 |
118 |
106 | 
107 |
108 |
107 |
109 |
116 | 110 | Nicholas Seckar (ulysses) is a student and software engineer living in Toronto, Canada. 111 | Nicholas has been contributing to Ruby and Rails since Fall 2004, with numerous bug fixes and new features such as Routing. 112 | He has been a developer on Measure Map since August 2005. He is currently completing his undergraduate degree 113 | at the University of Toronto, while also working for Google in their Toronto engineering department. 114 |
115 |
119 |
128 |
129 |
120 | 
121 |
122 |
121 |
123 |
127 | 124 | Florian Weber (csshsh) began using Rails in early 2004. Since then he’s played an integral role in several Rails-based projects. He developed the CMS and webshop for bellybutton.de, and later worked on Odeo. In Spring 2006 he began working on Twitter as lead developer. At the moment, he is living in Berlin, Germany and working as a software developer. 125 |
126 |
130 |
141 |
142 |
131 | 
132 |
133 |
132 |
134 |
140 | 135 | Sam Stephenson (sam-) is a fan of dynamic languages who found Ruby just six months before Rails’ first release. In February of 2005, 136 | he released the Prototype JavaScript library, which provides the foundation for Ajax support in Rails. Sam lives in Chicago, 137 | works for Basecamp, and tumblelogs on Projectionist. 138 |
139 |
143 |
154 |
155 |
144 | 
145 |
146 |
145 |
147 |
153 | 148 | Scott Barron (htonl) was set to swear off computers forever and become a plumber when Rails was released. 149 | He immediately found salvation in the warm embrace of Ruby and has never looked back. He currently practices 150 | Rails by working for EdgeCase. 151 |
152 |
156 |
165 |
166 |
157 | 
158 |
159 |
158 |
160 |
164 | 161 | Thomas Fuchs (madrobby) is a Web and JavaScript guru from Vienna, Austria. He is the author of script.aculo.us, a cross-browser JavaScript User Interface framework and he keeps busy as a core team member of the Prototype JavaScript framework, used by thousands of websites. He’s available for hire as a consultant for rich web user interfaces and JavaScript. 162 |
163 |
167 |
181 |
182 |
168 | 
169 |
170 |
169 |
171 |
180 | 172 | Tobias Lütke (xal) encountered Rails while struggling to find technology for his new company. 173 | Once found, he quickly ported the bits and pieces of his code over to Ruby which later became 174 | the first rails based e-commerce store “Snowdevil”. Tobi is a partner at JadedPixel and is 175 | frantically working on Shopify which is the continuation of the Snowdevil code base. 176 | Over time, Tobi released many open source projects such as Typo, Hieraki, 177 | and Liquid. 178 |
179 |
183 |
196 |
--------------------------------------------------------------------------------
/core/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Core"
3 | header: "The core team"
4 | subheader_1: "These are the top producers that were given the keys to the"
5 | subheader_2: "source repository after months or even years of loyal service."
6 | subheader_3: "They are presented in order of acceptance to the team."
7 | ---
8 |
184 | 
185 |
186 |
185 |
187 |
195 | 188 | Rick Olson (technoweenie) blames Ruby on Rails for 189 | destroying his ASP.Net career. He’s been using Rails actively since 2005 and is now working 190 | at Github. 191 | He’s also released several open source projects, such as Mephisto, Beast, along 192 | with numerous plugins. 193 |
194 |
9 |
10 |
26 |
27 |
11 | 
12 |
13 |
12 |
14 |
25 | 15 | David Heinemeier Hansson extracted Ruby on Rails from his 16 | work on Basecamp. He released the 17 | framework as open source in July of 2004, but didn’t share the commit rights 18 | until February of 2005. He’s infamous for his ruthless delegation, which is 19 | often executed as a request to “Please Do Investigate”. He’s a partner at 20 | Basecamp, his personal page is 21 | heinemeierhansson.com, 22 | and you can follow him on Twitter @dhh. 23 |
24 |
28 |
41 |
42 |
29 | 
30 |
31 |
30 |
32 |
40 | 33 | Jeremy Daer is a programmer at Basecamp 34 | hailing from Pasadena, California. 35 | Hot on the heels of DHH, he has been the most active contributor to Rails. He’s knee deep 36 | in pretty much all aspects of the framework and one of the top batters against new, 37 | incoming tickets. You can follow him on Twitter @bitsweat. 38 |
39 |
43 |
56 |
57 |
44 | 
45 |
46 |
45 |
47 |
55 | 48 | Michael Koziarski is a software consultant 49 | based in Wellington, New Zealand. After a successful stint as an enterprise Java 50 | developer, he switched to rails shortly after the first public release. He’s a 51 | contributor to The Rails Way and 52 | maintains a personal blog. 53 |
54 |
58 |
72 |
73 |
59 | 
60 |
61 |
60 |
62 |
71 | 63 | José Valim is the lead-developer and co-founder of Plataformatec. 64 | He started working with Rails in late 2006 and began contributing actively after 65 | his Google Summer of Code project in 2009. He’s frequently flying between Brazil 66 | and Poland, some say that it is his “eureka” time to code and bring new 67 | open-source projects to life. Check for 68 | yourself what he’s up to on his company’s blog. 69 |
70 |
74 |
88 |
89 |
75 | 
76 |
77 |
76 |
78 |
87 | 79 | Santiago Pastorino is the co-founder & CTO of 80 | WyeWorks. He started 81 | working with Ruby and Rails in the middle of 2008 after years of Java development. 82 | He is always trying to work as much as he can on OSS and to write on 83 | his company’s blog. Follow him on Twitter at 84 | @spastorino. 85 |
86 |
90 |
105 |
106 |
91 | 
92 |
93 |
92 |
94 |
104 | 95 | By day, Aaron Patterson (tenderlove) is a mild mannered programmer for 96 | Red Hat whose Ruby code 97 | is almost as good looking as him. By night, he dons his Pink Warrior suit which gives him 98 | the power to contribute to many Open Source projects such as nokogiri, 99 | Ruby, and Rails. If you have seen someone kissing Matz or DHH at a conference, 100 | it was probably him. You can find him on twitter, 101 | or read his blog. 102 |
103 |
107 |
121 |
122 |
108 | 
109 |
110 |
109 |
111 |
120 | 112 | Xavier Noria is an everlasting student and father of the most wonderful girl, 113 | as the picture to the left clearly demonstrates QED. An independent 114 | Ruby on Rails consultant from Barcelona, Xavier has worked with Rails since 2005. He wrote 115 | Rails Contributors and has been a regular contributor 116 | for years. Honored to have been presented a Ruby Hero Award. 117 | Xavier is @fxn on Twitter. 118 |
119 |
123 |
138 |
139 |
124 | 
125 |
126 |
125 |
127 |
137 | 128 | Rafael França is a member of Shopify's 129 | development team. He has worked full time with Rails since 2010 and has been contributing 130 | to the framework since the beginning of 2012. As a result of being passionate with OSS, 131 | he performs a key role in maintaining 132 | Simple Form) and also contributes 133 | to many other projects. Follow him on Twitter, 134 | on Github. 135 |
136 |
140 |
152 |
153 |
141 | 
142 |
143 |
142 |
144 |
151 | 145 | Andrew White is the CTO of Unboxed Consulting, 146 | London’s premier Ruby on Rails development team and specialists in Agile & Lean Startup techniques. He has 147 | been contributing to Rails since 2007 and has been producing open source software since 1997. You can follow 148 | him on Twitter and GitHub. 149 |
150 |
154 |
166 |
167 |
155 | 
156 |
157 |
156 |
158 |
165 | 159 | Guillermo Iguaran began using Ruby in 2008 and has been working 160 | with Rails since 2009. He started contributing to Rails framework and open-source 161 | world in 2011. Guillermo is from Colombia and right now he’s working as Software Engineer at Ride, 162 | and completing his Computer Sciences master’s degree. You can follow him on Twitter or 163 | Github. 164 |
168 |
183 |
184 |
169 | 
170 |
171 |
170 |
172 |
182 | 173 | Carlos Antonio is a software developer at You Need A Budget (YNAB). 174 | He started working with Ruby and Rails in late 2007, and since then he has become an 175 | Open Source lover, contributing to many different projects, and maintaining libraries like 176 | Simple Form 177 | and Devise. 178 | His motto is Hacking Beautiful Code. 179 | You can follow him on Twitter, 180 | or check his Github.
181 |
185 |
197 |
198 |
186 | 
187 |
188 |
187 |
189 |
196 | 190 | Yves Senn is a software developer at 4teamwork from Bern, Switzerland. 191 | Working with Java he started experimenting with Rails in 2008 and began contributing in 2012. 192 | He loves to hack on Open Source projects and is organizing local meetups. 193 | Yves is @senny on GitHub and you can follow him on Twitter. 194 |
195 |
199 |
212 |
213 |
200 | 
201 |
202 |
201 |
203 |
211 | 204 | Godfrey Chan is a staff engineer at Tilde based in Portland, Oregon. 205 | He began contributing to Rails in 2012. In addition to his code contributions, he enjoys connecting with others in the 206 | community through speaking at conferences, 207 | volunteering for RailsBridge and sending newsletters. 208 | You can follow him on Twitter or Github. 209 |
210 |
214 |
220 |
--------------------------------------------------------------------------------
/deploy/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Deploy"
3 | header: "Deploying Ruby on Rails is easy"
4 | subheader_1: "Taking your Rails application live has never been easier."
5 | subheader_2: "Thanks to the rise of Passenger aka mod_rails,"
6 | subheader_3: "launching is now almost as easy as developing."
7 | ---
8 |
215 |
219 | 216 | Rails core members who are no longer active in the day-to-day stuff have been immortalized as core alumni. 217 |
218 |
9 |
10 |
20 |
21 |
11 | Passenger
12 |
13 | Passenger
aka mod_rails
12 |
14 |
19 |
15 | 
16 | The easiest deployment setup for Rails is Phusion Passenger aka mod_rails. It’s a module for nginx and Apache that automatically manages the back end. Just setup, launch, and enjoy.
17 |
22 |
32 |
33 |
23 |
25 |
31 | Proxy setups
24 |
28 | If you need more fine-grained control over your deployment setup, the common option is to use a front-end server like nginx and Apache combined with a proxy relay like
34 |
44 |
45 |
35 |
37 |
43 | JRuby on Rails
36 |
40 |
46 |
56 |
57 |
47 | Automate with
48 |
49 | Automate with
Capistrano
48 |
50 |
55 |
51 | 
52 | Capistrano brings deployment automation to Rails whether you’re working with a single server or on a cluster of dozens. It was extracted from the Basecamp tool chain (like Rails) by core alumni Jamis Buck.
53 |
58 |
67 |
--------------------------------------------------------------------------------
/documentation/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Documentation"
3 | header: "Learn all about Ruby on Rails"
4 | subheader_1: "We have everything you need to become an expert with Rails,"
5 | subheader_2: "including books, tutorials, manuals, and lots of"
6 | subheader_3: "open-source examples."
7 | ---
8 |
59 |
61 | Hosting
60 |
62 |
66 | 63 | While Rails hosting is now common place, there’s a handful of dedicated Rails hosting companies that have been around for a long time and supporting the community: Heroku, Rails Machine, Brightbox, and Engine Yard. If you’re just looking for a VPS, we recommend Rackspace (who gracefully donated slices for us to run Rails infrastructure on) or Linode. 64 |
65 |
9 |
10 |
20 |
21 |
11 |
13 | Guides
12 |
14 |
19 | 15 | If you’re just getting started or want to learn about Rails in general, check 16 | the Rails Guides. 17 |
18 |
22 |
31 |
32 |
23 |
25 | APIs
24 |
26 |
29 |
30 |
33 |
54 |
55 |
34 |
36 | Books
35 |
37 |
53 | 38 | Agile Web 40 | Development with Rails will teach you all you need to know about Ruby and Rails 4 to build 41 | killer web applications. For more advanced material, Rails core member José Valim has written 42 | Crafting Rails 4 Applications. 43 |
44 |
45 | 
47 | 
48 |
50 | See all the other Ruby on Rails books at Amazon. 51 |
52 |
56 |
68 |
--------------------------------------------------------------------------------
/download/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Download"
3 | header: "Get Ruby on Rails in no time"
4 | subheader_1: "Rails is low on dependencies and prides itself on shipping with"
5 | subheader_2: "most everything you need in the box. To get started, just install"
6 | subheader_3: "Ruby, the language, and RubyGems, the package manager."
7 | ---
8 |
57 | Talking
58 |
59 | Talking
foxes?
58 |
60 |
67 |
61 | 
62 | why’s (poignant) guide to Ruby
63 | is unlike any other guide to programming you have ever read. It features talking foxes,
64 | bizarre sidebars, and more crazy humor than most people can handle without loud chuckles.
65 |
9 |
10 |
29 |
30 |
11 |
13 | Ruby
12 |
14 |
28 |
15 | 
16 | We recommend Ruby 2.2 or newer for use with Rails.
17 | Rails requires Ruby 1.9.3 or newer.
18 |
20 | Source: Compile it yourself
21 | Windows installer: Ruby, popular extensions, editor
22 | OS X 10.5+: Included with developer tools
(then do gem update rails)
23 |
25 | We recommend managing your Ruby installation through rbenv. It’s an easy way to run multiple versions for different applications and update when a new release is made. 26 |
27 |
31 |
44 |
45 |
32 |
34 | Rails
33 |
35 |
43 | 36 | With Ruby installed, you can install all of Rails and its dependencies through RubyGems on the command line: 37 |
38 |gem install rails40 | New versions of Rails can be installed the same way. 41 |
42 |
46 |
61 |
62 |
47 |
49 | Make your application
48 |
50 |
60 | 51 | Create your application skeleton and start the server: 52 |
53 |rails new path/to/your/new/application
54 | cd path/to/your/new/application
55 | rails server57 | You’re running Ruby on Rails! Follow the instructions on http://localhost:3000. 58 |
59 |
63 |
74 |
--------------------------------------------------------------------------------
/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/favicon.ico
--------------------------------------------------------------------------------
/images/applications/bcx.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/applications/bcx.gif
--------------------------------------------------------------------------------
/images/applications/github.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/applications/github.jpg
--------------------------------------------------------------------------------
/images/applications/shopify.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/applications/shopify.jpg
--------------------------------------------------------------------------------
/images/applications/twitter.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/applications/twitter.jpg
--------------------------------------------------------------------------------
/images/basecamp.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/basecamp.png
--------------------------------------------------------------------------------
/images/herobackground.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/herobackground.gif
--------------------------------------------------------------------------------
/images/pages/core/aaron.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/aaron.png
--------------------------------------------------------------------------------
/images/pages/core/alumni/florian.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/florian.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/jamis.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/jamis.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/marcel_molina.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/marcel_molina.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/nicholas.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/nicholas.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/rick.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/rick.png
--------------------------------------------------------------------------------
/images/pages/core/alumni/sam.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/sam.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/scott.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/scott.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/thomas_fuchs.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/thomas_fuchs.jpg
--------------------------------------------------------------------------------
/images/pages/core/alumni/tobi.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/alumni/tobi.jpg
--------------------------------------------------------------------------------
/images/pages/core/andrew-white.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/andrew-white.jpg
--------------------------------------------------------------------------------
/images/pages/core/carl.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/carl.jpg
--------------------------------------------------------------------------------
/images/pages/core/carlos-antonio.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/carlos-antonio.jpg
--------------------------------------------------------------------------------
/images/pages/core/david.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/david.jpg
--------------------------------------------------------------------------------
/images/pages/core/godfrey.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/godfrey.jpg
--------------------------------------------------------------------------------
/images/pages/core/guillermo-iguaran.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/guillermo-iguaran.jpg
--------------------------------------------------------------------------------
/images/pages/core/jeremy.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/jeremy.jpg
--------------------------------------------------------------------------------
/images/pages/core/jonleighton.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/jonleighton.jpg
--------------------------------------------------------------------------------
/images/pages/core/jose.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/jose.png
--------------------------------------------------------------------------------
/images/pages/core/koz.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/koz.jpg
--------------------------------------------------------------------------------
/images/pages/core/pic1218916611.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/pic1218916611.jpg
--------------------------------------------------------------------------------
/images/pages/core/pratik.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/pratik.jpg
--------------------------------------------------------------------------------
/images/pages/core/rafaelfranca.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/rafaelfranca.jpg
--------------------------------------------------------------------------------
/images/pages/core/santiago.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/santiago.jpg
--------------------------------------------------------------------------------
/images/pages/core/senny.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/senny.png
--------------------------------------------------------------------------------
/images/pages/core/xavier.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/xavier.png
--------------------------------------------------------------------------------
/images/pages/core/yehuda.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/core/yehuda.jpg
--------------------------------------------------------------------------------
/images/pages/deploy/capistrano.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/deploy/capistrano.jpg
--------------------------------------------------------------------------------
/images/pages/deploy/duke.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/deploy/duke.jpg
--------------------------------------------------------------------------------
/images/pages/deploy/mongrel.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/deploy/mongrel.jpg
--------------------------------------------------------------------------------
/images/pages/deploy/passenger.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/deploy/passenger.png
--------------------------------------------------------------------------------
/images/pages/documentation/awdr4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/documentation/awdr4.png
--------------------------------------------------------------------------------
/images/pages/documentation/chunkybacon.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/documentation/chunkybacon.gif
--------------------------------------------------------------------------------
/images/pages/documentation/cra-mini.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/documentation/cra-mini.png
--------------------------------------------------------------------------------
/images/pages/download/ruby.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/download/ruby.png
--------------------------------------------------------------------------------
/images/pages/overview/download42.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/overview/download42.png
--------------------------------------------------------------------------------
/images/pages/overview/participate.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/overview/participate.gif
--------------------------------------------------------------------------------
/images/pages/overview/screencasts2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/overview/screencasts2.png
--------------------------------------------------------------------------------
/images/pages/screencasts/Rails_for_Zombies-2.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/screencasts/Rails_for_Zombies-2.jpg
--------------------------------------------------------------------------------
/images/pages/screencasts/rails4_zombie_outlaws.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/screencasts/rails4_zombie_outlaws.jpg
--------------------------------------------------------------------------------
/images/pages/screencasts/railscasts.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/pages/screencasts/railscasts.png
--------------------------------------------------------------------------------
/images/rails.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/rails.png
--------------------------------------------------------------------------------
/images/rss.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/rss.png
--------------------------------------------------------------------------------
/images/topbluefade.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rails/homepage-2011/a30bbf1dad65632df5cea85b26670ceaad8790ba/images/topbluefade.gif
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | header: "Web development that doesn’t hurt"
3 | subheader_1: "Ruby on Rails® is an open-source web framework that’s optimized"
4 | subheader_2: "for programmer happiness and sustainable productivity. It lets you"
5 | subheader_3: "write beautiful code by favoring convention over configuration."
6 | ---
7 |
64 |
66 | Editors
65 |
67 |
73 | 68 | TextMate on OS X has long been the favored Rails editor, but the classic editors are still going strong. 69 | See VIM for Rails and Emacs for Rails. 70 | For a full-on IDE, check out JetBrains RubyMine. 71 |
72 |
8 |
38 |
9 |
13 | 10 | Rails 4.2.0 has been released! 11 |
12 |
14 |
36 |
37 |
15 |
20 |
25 |
30 |
35 |
39 |
89 |
107 | 40 | “Ruby on Rails is a breakthrough in lowering the barriers of entry to programming.45 | 52 | 58 | 64 | 71 | 77 | 83 | 87 | 88 |
41 | Powerful web applications that formerly might have taken weeks or months
42 | to develop can be produced in a matter of days.” 43 | – Tim O’Reilly, Founder of O’Reilly Media 44 |
108 |
150 |
--------------------------------------------------------------------------------
/quotes/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Quotes"
3 | header: "Smart people saying nice things"
4 | subheader_1: "Ego-inflation galore."
5 | subheader_2: "This is where we collect quotes from smart, famous,"
6 | subheader_3: "and/or funny people saying nice things about Rails."
7 | ---
8 |
109 |
136 |
137 |
110 | Who is already
111 |
112 | Who is already
on Rails?
111 |
113 |
135 | Tens of thousands of Rails applications are already live. People are using Rails in the tiniest part-time operations to the biggest companies.
114 | 134 |
138 |
149 |
139 | Who is
140 |
141 | Who is
behind it?
140 |
142 |
148 | 143 | Rails was created in 2003 by David Heinemeier Hansson 144 | and has since been extended by the Rails core team and 145 | more than 4,000 contributors. 146 |
147 |9 | “Rails is the most well thought-out web development framework I’ve ever used.15 |
10 | And that’s in a decade of doing web applications for a living. I’ve built my
11 | own frameworks, helped develop the Servlet API, and have created more than
12 | a few web servers from scratch. Nobody has done it like this before.” 13 | – James Duncan Davidson, Creator of Tomcat and Ant 14 |
16 | “Ruby on Rails is a breakthrough in lowering the barriers of entry to programming.21 |
17 | Powerful web applications that formerly might have taken weeks or months
18 | to develop can be produced in a matter of days.” 19 | – Tim O’Reilly, Founder of O’Reilly Media 20 |
22 | “It is impossible not to notice Ruby on Rails. It has had a huge effect both in27 |
23 | and outside the Ruby community... Rails has become a standard to which even
24 | well-established tools are comparing themselves to.” 25 | – Martin Fowler, Author of Refactoring, PoEAA, XP Explained 26 |
28 | “What sets this framework apart from all of the others is the preference for33 |
29 | convention over configuration making applications easier
30 | to develop and understand.” 31 | – Sam Ruby, ASF board of directors 32 |
34 | “Before Ruby on Rails, web programming required a lot of verbiage, steps and time.40 |
35 | Now, web designers and software engineers can develop a website
36 | much faster and more simply, enabling them to be more productive
37 | and effective in their work.” 38 | – Bruce Perens, Open Source Luminary 39 |
41 | “After researching the market, Ruby on Rails stood out as the best choice.46 |
42 | We have been very happy with that decision. We will continue
43 | building on Rails and consider it a key business advantage.” 44 | – Evan Williams, Creator of Blogger and ODEO 45 |
47 | “Ruby on Rails is astounding. Using it is like watching a kung-fu movie,52 |
48 | where a dozen bad-ass frameworks prepare to beat up the little newcomer
49 | only to be handed their asses in a variety of imaginative ways.” 50 | – Nathan Torkington, O’Reilly Program Chair for OSCON 51 |
53 | “Rails is the killer app for Ruby.” 54 | – Yukihiro Matsumoto, Creator of Ruby 55 |56 | -------------------------------------------------------------------------------- /robots.txt: -------------------------------------------------------------------------------- 1 | User-agent: * 2 | Disallow: 3 | Sitemap: http://rubyonrails.org/sitemap.xml 4 | -------------------------------------------------------------------------------- /screencasts/index.html: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Screencasts" 3 | header: "Show, don’t tell: Seeing is believing" 4 | subheader_1: "Lean back and enjoy the shows, but be careful: Going back to your" 5 | subheader_2: "former treadmill after being exposed to these movies can prove" 6 | subheader_3: "exceedingly painful. Don’t say we didn’t try to warn you." 7 | --- 8 |
9 |
10 |
15 |
31 |
32 |
11 |
12 | 
13 |
14 |
13 |
14 |
16 |
30 | Learning Rails the Zombie Way
17 |18 | If you’re new to Rails and want to give it a try, then head over to 19 | RailsForZombies.org. Rails for Zombies is 20 | a free online course that provides you five labs, each with a short video followed 21 | by a series of exercises where you get to code Rails immediately in your browser. 22 |
23 |24 | If you’re interested in the history of Rails, we also still have the screencasts 25 | made for Ruby on 26 | Rails 2, Ruby on 27 | Rails 0.5 and for Ruby on Rails 1.0. 28 |
29 |
33 |
38 |
52 |
53 |
34 |
35 | 
36 |
37 |
36 |
37 |
39 |
51 | Rails 4: Zombie Outlaws
40 |41 | If you’re looking to get your hands dirty with the newest version of Rails, the 42 | Rails 4: Zombie Outlaw Videos 43 | will give you a taste of the new features and improved syntax. Gregg Pollack and 44 | Carlos Souza walk you through what you need to know to start building Rails 4 apps today. 45 |
46 |47 | Also checkout the Ruby5 48 | Podcast for keeping up to date with the latest libraries and news from the Rails world. 49 |
50 |
54 |
59 |
69 |
--------------------------------------------------------------------------------
/security/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Security Policy"
3 | header: "Security policy"
4 | subheader_1: "Rails takes web security very seriously."
5 | subheader_2: "If you found a vulnerability in Ruby on Rails, follow"
6 | subheader_3: "these steps to safely report the issue to the core team."
7 | ---
8 |
55 |
56 | 
57 |
58 |
57 |
58 |
60 |
68 | More free screencasts from Railscasts.com
61 |62 | If the screencast above got you interested in learning more by video, you can 63 | find a treasure trove of great content at Railscasts.com. 64 | It’s all about short, sweet videos that show you how to use various features of Rails 65 | and they’re done by the same fantastic Ryan Bates that did the video above. 66 |
67 |
9 |
10 |
68 |
69 |
11 |
13 | Supported versions
12 |
14 |
67 | 15 | Support of the Rails framework is divided into four groups: New features, bug fixes, 16 | security issues, and severe security issues. They are handled as follows: 17 |
18 | 19 |New Features
20 |21 | New Features are only added to the master branch and will not be made available in point releases. 22 |
23 | 24 |Bug fixes
25 |26 | Only the latest release series will receive bug fixes. When enough bugs are fixed and 27 | its deemed worthy to release a new gem, this is the branch it happens from. 28 |
29 | 30 |-
31 |
- Current release series: 4.2.x 32 |
Security issues:
35 |36 | The current release series and the next most recent one will receive patches 37 | and new versions in case of a security issue. 38 |
39 | 40 |-
41 |
- Current release series: 4.2.x 42 |
- Next most recent release series: 4.1.x 43 |
Severe security issues:
46 |47 | For severe security issues we will provide new versions as above, and 48 | also the last major release series will receive patches and new versions. 49 | The classification of the security issue is judged by the core team. 50 |
51 | 52 |-
53 |
- Current release series: 4.2.x 54 |
- Next most recent release series: 4.1.x 55 |
- Last major release series: 3.2.x 56 |
Unsupported Release Series
59 |60 | When a release series is no longer supported, it’s your own responsibility 61 | to deal with bugs and security issues. We may provide back-ports of the 62 | fixes and publish them to git, however there will be no new versions 63 | released. If you are not comfortable maintaining your own versions, you 64 | should upgrade to a supported version. 65 |
66 |
70 |
109 |
110 |
71 |
73 | Reporting a bug
72 |
74 |
108 | 75 | All security bugs in rails should be reported through our 76 | bounty program page at HackerOne. This will 77 | deliver a message to a subset of the core team 78 | who handle security issues. Your report will be acknowledged within 24 hours, and you’ll 79 | receive a more detailed response to your email within 48 hours indicating the next 80 | steps in handling your report. 81 |
82 | 83 |84 | After the initial reply to your report the security team will 85 | endeavor to keep you informed of the progress being made towards a fix and full 86 | announcement. These updates will be sent at least every five days, 87 | in reality this is more likely to be every 24-48 hours. 88 |
89 | 90 |91 | If you have not received a reply to your email within 48 hours, or have not heard 92 | from the security team for the past five days there are a few steps you can take: 93 |
94 | 95 |-
96 |
- Send an email to the security reports list (security@rubyonrails.org) 97 |
- Contact the current security coordinator (Michael Koziarski) directly 98 |
- Contact the back-up contact (Jeremy Kemper) directly. 99 |
- Email the rails core list or ask in #rails-contrib 100 |
103 | Please note, the rails core list and #rails-contrib are public areas. When escalating 104 | to that address please do not discuss your issue, simply say that you’re trying to get 105 | a hold of someone from the security team. 106 |
107 |
111 |
161 |
162 |
112 |
114 | Disclosure Policy
113 |
115 |
160 | Ruby on Rails has a 5 step disclosure policy.
116 | 117 |-
118 |
- 119 | Security report received and is assigned a primary handler. 120 | This person will coordinate the fix and release process. 121 | 122 |
- 123 | Problem is confirmed and, a list of all affected versions is determined. 124 | Code is audited to find any potential similar problems. 125 | 126 |
- 127 | Fixes are prepared for all releases which are still supported. 128 | These fixes are not committed to the public 129 | repository but rather held locally pending the announcement. 130 | 131 |
- 132 | A suggested embargo date for this vulnerability is chosen and 133 | distros@openwall 134 | is notified. This notification will include patches for all versions 135 | still under support and a contact address for packagers who need 136 | advice back-porting patches to older versions. 137 | 138 |
- 139 | On the embargo date, the rails security mailing list 140 | is sent a copy of the announcement. The changes are pushed to the public repository 141 | and new gems released to rubygems. At least 6 hours after the mailing list is notified, 142 | a copy of the advisory will be published on Riding Rails 143 | 144 |
147 | Typically the embargo date will be set 72 hours from the time 148 | distros@openwall 149 | is first notified, however this may vary depending on the severity of the bug 150 | or difficulty in applying a fix. 151 |
152 | 153 |154 | This process can take some time, especially when coordination is required with 155 | maintainers of other projects. Every effort will be made to handle the bug in 156 | as timely a manner as possible, however it’s important that we follow the release 157 | process above to ensure that the disclosure is handled in a consistent manner. 158 |
159 |
163 |
187 |
188 |
164 |
166 | Receiving Security Updates
165 |
167 |
186 | 168 | The best way to receive all the security announcements is to subscribe to the 169 | rails security 170 | mailing list. The mailing list is very low traffic, and 171 | it receives the public notifications the moment the embargo is lifted. If you 172 | produce packages of Ruby on Rails and require prior notification of vulnerabilities, 173 | you should be subscribed to 174 | distros@openwall. 175 |
176 | 177 |178 | No one outside the core team, the initial reporter or 179 | distros@openwall 180 | will be notified 181 | prior to the lifting of the embargo. We regret that we cannot make exceptions to 182 | this policy for high traffic or important sites, as any disclosure beyond the 183 | minimum required to coordinate a fix could cause an early leak of the vulnerability. 184 |
185 |
189 |
199 |
--------------------------------------------------------------------------------
/styles.css:
--------------------------------------------------------------------------------
1 | /* TYPOGRAPHY */
2 | body {font-family: Georgia, serif}
3 | header {font-family: "expressway", sans-serif}
4 | code {font-family: Courier New, Courier, mono}
5 | #announce, .smaller p, footer, ul, ol {font-family: Verdana, Lucida Grande, Arial, Helvetica, sans-serif}
6 | h1 {font-size: 38px}
7 | h2 {font-size: 28px}
8 | h3 {font-size: 22px}
9 | h4 {font-size: 21px}
10 | .small h2 {font-size: 20px}
11 | h5, p, blockquote {font-size: 18px}
12 | code, pre code, .small blockquote {font-size: 16px}
13 | .small p, cite {font-size: 14px}
14 | .footnote {font-size: 12px}
15 | nav, footer p, #announce {font-size: 11px}
16 | .smaller p {font-size: 10px}
17 | @media (max-width: 767px) {h1 {font-size: 31px}}
18 | @media (max-width: 767px) {h4 {font-size: 18px}}
19 | h1, h5, code, nav {font-weight: bold}
20 | h2, h3 {font-weight: normal}
21 | h1 {line-height: 30px}
22 | h4, h3 {line-height: 24px}
23 | body, footer p {line-height: 18px}
24 | h5, p, blockquote {line-height: 140%}
25 | h2 {line-height: 120%}
26 | .col-sm-4 {text-align: right}
27 | footer, blockquote, #menu {text-align: center}
28 | @media (max-width:767px) {h2, h5, .col-sm-4 {text-align: center}}
29 | a {text-decoration: underline}
30 | a:focus, a:hover {text-decoration: none}
31 |
32 | /* BACKGROUNDS */
33 | body {background-image: url(images/topbluefade.gif); background-repeat: repeat-x}
34 | .slivers {background-image: url(images/herobackground.gif)}
35 | @media (min-width: 768px) {header.container {background-image: url(images/rails.png); background-repeat: no-repeat; background-position: 22px 0px}}
36 |
37 | /* COLORS */
38 | a {color: #369}
39 | a:hover, a:focus {background-color: #f4dda6}
40 | mark {background-color: #ffc}
41 | footer {color: #666}
42 | #menu a, code, pre, footer a {color: #000}
43 | #menu a:focus, #menu a:hover {color: #fff; background-color: #333}
44 | .navbar-default, code, pre {background-color: transparent}
45 | .navbar {border-color: transparent}
46 | h4 {color: #999}
47 | .framed img, .col-sm-4 img {background-color: #fff; border-color: #ccc}
48 | h5 {color: #900}
49 | cite {color: #a69e8a}
50 | #announce {background-color: #981a21}
51 | #announce a, .inverted a:hover, .inverted a:focus {color: #fff}
52 | .slivers {border-top-color: #f6e69f; border-bottom-color: #f6e69f}
53 | .slivers a {color: #000}
54 | .inverted a:hover, .inverted a:focus {background-color: #000}
55 | #slideshow cite, #slideshow a {color: #464242}
56 |
57 | /* BORDERS */
58 | #menu.in {border-bottom-style: solid}
59 | #menu:not(.in) li:not(:last-child) {border-right-style: solid}
60 | .framed img, .col-sm-4 img {border-style: solid}
61 | .slivers {border-top-style: solid; border-bottom-style: solid}
62 |
63 | /* LAYOUTS */
64 | cite {display: block}
65 | @media (min-width: 768px) {.navbar .navbar-nav {display: inline-block; float: none}}
66 | @media (min-width: 768px) {.navbar-brand {display: none}}
67 |
68 | /* WIDTHS */
69 | img.screencast {width: 198px}
70 | img.biopic {width: 158px; margin-right: 12px}
71 | @media (min-width:992px) {.container {width: 750px}}
72 | @media (min-width:992px) {.slivers .container {width: 792px}}
73 | #menu:not(.in) li {padding-left: 5px; padding-right: 5px}
74 | #menu:not(.in) li:not(:last-child) {border-right-width: 1px}
75 | #menu a , mark, code, pre {padding-left: 0; padding-right: 0}
76 | @media (min-width: 768px) {header.container {padding-left: 115px}}
77 | h2, .col-sm-8 p, h5, ul, ol {margin-right: 10px}
78 | pre {border-left: 0; border-right: 0; margin-left: 35px}
79 | @media (max-width: 767px) {pre {margin-left: 10px}}
80 | .framed img {padding-left: 1px; padding-right: 1px; border-left-width: 1px; border-right-width: 1px}
81 | .col-sm-4 img {padding-left: 2px; padding-right: 2px; border-left-width: 2px; border-right-width: 2px}
82 | .col-sm-4 a {margin-right: 2px}
83 | .col-sm-8 .framed, .col-sm-8 p, h5, ul, ol {margin-left: 10px}
84 | .col-sm-6 .framed {margin-left: 0px}
85 | .col-sm-6 .framed img {margin-bottom: 4px}
86 | blockquote {border-left-width: 0}
87 |
88 | /* HEIGHTS */
89 | img.screencast {height: 158px}
90 | img.biopic {height: 180px; margin-bottom: 10px}
91 | .navbar-brand img {height: 34px}
92 | #menu li {margin-top: 10px; margin-bottom: 13px}
93 | #menu a, mark, pre, blockquote {padding-top: 0; padding-bottom: 0}
94 | .navbar-brand {padding-top: 8px}
95 | #menu.in {border-bottom-width: 1px}
96 | header {margin-top: 27px; margin-bottom: 32px}
97 | h1, h2, h5 {margin-top: 0}
98 | h2, article {margin-bottom: 20px}
99 | .col-sm-8 p {margin-bottom: 25px}
100 | h1 {margin-bottom: 12px}
101 | h4, h5, #announce {margin-bottom: 0px}
102 | pre {border-top: 0; border-bottom: 0}
103 | pre, blockquote {margin-bottom: 25px}
104 | footer {padding-bottom: 44px}
105 | footer p {margin-bottom: 12px; margin-top: 12px}
106 | #sponsored_by {margin-bottom: 17px; margin-top: 17px}
107 | #sponsored_by img {vertical-align: -7px}
108 | .framed img {padding-top: 1px; padding-bottom: 1px; border-top-width: 1px; border-bottom-width: 1px}
109 | .col-sm-4 img {padding-top: 2px; padding-bottom: 2px}
110 | .col-sm-4 img, .slivers {border-top-width: 2px; border-bottom-width: 2px}
111 | ul, ol {margin-bottom: 14px}
112 | cite {margin-top: 2px}
113 | #announce {padding-top: 4px; padding-bottom: 4px}
114 | h3 {margin-top: 10px}
115 | .slivers p {margin-top: 8px; margin-bottom: 27px}
116 | .slivers {margin-bottom: 16px}
117 | #slideshow blockquote {height: 87px}
118 | @media (max-width: 767px) {#slideshow blockquote {height: 200px}}
119 | #slideshow {margin-bottom: 21px}
120 |
--------------------------------------------------------------------------------
190 |
192 | Comments on this Policy
191 |
193 |
198 | 194 | If you have any suggestions to improve this policy, please send an email to 195 | security@rubyonrails.org. 196 |
197 |