-
-
Notifications
You must be signed in to change notification settings - Fork 277
Rails Guides Conventions
Each guide should start with motivational text at the top, telling readers what they’ll learn. ( Example – Routing Guide )
Communicate to the reader the current way of doing things, both explicitly and implicitly. Use the recommended idioms in edge (which is the version we are documenting), reorder sections to emphasize favored approaches if needed, etc. The documentation should be a model for best practices and canonical, modern Rails usage.
Try to make your examples fit the boxes in the design, wrap comments, long method calls, just shorten stuff, etc. as needed.
The proper name of Rails components has spaces in between: “Active Record”. Please write them like that. There’s lack of unanimity in books, but we checked it with David.
The title of every guide uses h2
, guide sections use h3
, subsections h4
, etc.
Capitalize all words except for internal articles, prepositions, conjuctions, and forms of the verb to be:
h5. Middleware Stack is an Array h5. When are Objects Saved?
Use same typography as in regular text:
h3. Brief Note About +Test::Unit+ h6. The +:content_type+ Option
For the sake of coherence, in Rails Guides we follow the same typographic conventions as the API documentation:
Fixed-width font for method names, literals like nil
, false
, true
, self
, symbols, and method parameters.
Validations such as `validates_uniqueness_of` are one way in which models can enforce data integrity. The `:dependent` option on associations allows models to automatically destroy child objects when the parent is destroyed.
When “true” and “false” are English words rather than Ruby keywords use regular font for them:
If you set the +:accessible+ option to true, then mass assignment is allowed for this association.
Fixed-width font as well for constants, in particular for class and module names.
A migration is a subclass of +ActiveRecord::Migration+ that implements two class methods: +up+ (perform the required transformations) and +down+ (revert them).
To get started make sure +Base.perform_caching+ is set to true for your environment.
Fixed-width font also for filenames:
For example +20080906120000_create_products.rb+ should define +CreateProducts+ and +20080906120001_add_details_to_products.rb+ should define +AddDetailsToProducts+.
Guides are written in Textile. There’s comprehensive documentation here and a cheatsheet for markup here.
To generate all the guides just cd into the railties
directory and execute
- generates the HTML of all guides
rake generate_guides
To process my_guide.textile
and nothing else use the ONLY
environment variable:
- generates the HTML of “my_guide.textile”
rake generate_guides ONLY=my_guide