Write documentation with your code, to keep them in sync, ideal for public API docs.

This document was generated using DoubleDoc from doc/readme.md, and the source of this project is a great source for how to use DoubleDoc.

Write documentation in markdown right in source code files by double commenting it:

class User < ActiveRecord::Base
  ## ```js
  ## {
  ##   "id":   1,
  ##   "name": "Mick Staugaard"
  ## }
  ## ```
  def as_json
    # this comment will not be included in the documentation
    # as it only has a single # character
    super(only: [:id, :name])
  end
end

class UsersController < ApplicationController
  ## ### Getting a User
  ## `GET /users/{id}.json`
  ##
  ## #### Format
  ## @import app/models/user.rb
  def show
    render json: User.find(params[:id])
  end
end

Then write a markdown document about User API:

## Users
Access users by using our REST API, blah blah blah...

@import app/controllers/users_controller.rb

And DoubleDoc will generate this markdown document:

## Users
Access users in by using our REST API, blah blah blah...

### Getting a User
`GET /users/{id}.json`

#### Format
```js
{
  "id":   1,
  "name": "Mick Staugaard"
}
```

Generate documentation by telling DoubleDoc what the input files are, and where the output should go. In the example, double_doc is picked to avoid conflicts with the doc rake task in rails.

require 'double_doc'

DoubleDoc::Task.new(
  :double_doc,
  sources:          'doc/source/*.md',
  md_destination:   'doc/generated',
  html_destination: 'site'
)

The available options are:

require 'double_doc'

DoubleDoc::Task.new(:double_doc, sources: 'doc/README.md', md_destination: '.')

Then run rake double_doc, which will generate a readme.md in the root of the project.

If a gh-pages branch exists, run rake doc:publish to generate html documentation and push it to your github pages.

• Tested on ruby 3.0+
• Does not work on jruby because of its dependency on redcarpet.

After merging your changes:

1. Create a PR with a version bump and updated changelog.
2. After that PR gets merged, create a new tag (by running gem_push=no rake release or via Github releases).
3. This will trigger the publishing workflow—approve it in Github Actions).

• Support for directory structures
• Documentation for the Guard
• Add support for extracting documentation from JavaScript files

Copyright © 2012 Mick Staugaard

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS,” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.