# Ruby on Rails Guides Guidelines¶ ↑

This guide documents guidelines for writing Ruby on Rails Guides. This guide follows itself in a graceful loop, serving itself as an example.

After reading this guide, you will know:

- About the conventions to be used in Rails documentation.

- How to generate guides locally.

## Markdown¶ ↑

Guides are written in GitHub Flavored Markdown. There is comprehensive documentation for Markdown, as well as a cheatsheet.

## Prologue¶ ↑

Each guide should start with motivational text at the top (that's the little introduction in the blue area). The prologue should tell the reader what the guide is about, and what they will learn. As an example, see the Routing Guide.

## Headings¶ ↑

The title of every guide uses an `h1` heading; guide sections use `h2` headings; subsections use `h3` headings; etc. Note that the generated HTML output will use heading tags starting with `<h2>`.

    Guide Title
    ===========

    Section
    -------

    ### Sub Section

When writing headings, capitalize all words except for prepositions, conjunctions, internal articles, and forms of the verb “to be”:

    #### Middleware Stack is an Array
    #### When are Objects Saved?

Use the same inline formatting as regular text:

    ##### The `:content_type` Option

## API Documentation Guidelines¶ ↑

The guides and the API should be coherent and consistent where appropriate. In particular, these sections of the API Documentation Guidelines also apply to the guides:

- Wording

- English

- Example Code

- Filenames

- Fonts

## HTML Guides¶ ↑

Before generating the guides, make sure that you have the latest version of Bundler installed on your system. As of this writing, you must install Bundler 1.3.5 on your device.

To install the latest version of Bundler, run `gem install bundler`.

### Generation¶ ↑

To generate all the guides, just `cd` into the `guides` directory, run `bundle install`, and execute:

    bundle exec rake guides:generate

or

    bundle exec rake guides:generate:html

To process `my_guide.md` and nothing else use the `ONLY` environment variable:

    touch my_guide.md
    bundle exec rake guides:generate ONLY=my_guide

By default, guides that have not been modified are not processed, so `ONLY` is rarely needed in practice.

To force processing all the guides, pass `ALL=1`.

It is also recommended that you work with `WARNINGS=1`. This detects duplicate IDs and warns about broken internal links.

If you want to generate guides in a language other than English, you can keep them in a separate directory under `source` (eg. `source/es`) and use the `GUIDES_LANGUAGE` environment variable:

    bundle exec rake guides:generate GUIDES_LANGUAGE=es

If you want to see all the environment variables you can use to configure the generation script just run:

    rake

### Validation¶ ↑

Please validate the generated HTML with:

    bundle exec rake guides:validate

Particularly, titles get an ID generated from their content and this often leads to duplicates. Please set `WARNINGS=1` when generating guides to detect them. The warning messages suggest a solution.

## Kindle Guides¶ ↑

### Generation¶ ↑

To generate guides for the Kindle, use the following rake task:

    bundle exec rake guides:generate:kindle