njonsson/cape
Dynamically generates Capistrano recipes for Rake tasks. – Read the documentation
This page shows an evaluation of the documentation of njonsson/cape.
Each class, module, method, etc. is given a grade based on how complete the docs are.
The bar above shows the distribution of these grades.
| Seems really good | ||
|---|---|---|
|
A
|
Cape::RecipeDefinition#cd |
|
|
A
|
#Cape |
|
|
A
|
Cape::Rake#expire_cache! |
|
|
A
|
Cape::DSL#method_missing |
|
|
A
|
Cape |
|
| Show 25 more ... | ||
|
A
|
Cape::Capistrano#define_rake_wrapper |
|
|
A
|
Cape::DSL#remote_rake_executable= |
|
|
A
|
Cape::DSL#local_rake_executable= |
|
|
A
|
Cape::RecipeDefinition#rename |
|
|
A
|
Cape::Rake#remote_executable= |
|
|
A
|
Cape::DSL#mirror_rake_tasks |
|
|
A
|
Cape::Capistrano#initialize |
|
|
A
|
Cape::RecipeDefinition#env |
|
|
A
|
Cape::DSL#each_rake_task |
|
|
A
|
Cape::RecipeDefinition |
|
|
A
|
Cape::Rake#initialize |
|
|
A
|
Cape::Capistrano |
|
|
A
|
Cape::Rake#== |
|
|
A
|
Cape::Rake |
|
|
A
|
Cape::DSL |
|
|
A
|
Cape::Capistrano#rake= |
|
|
A
|
Cape::Capistrano#rake |
|
|
A
|
Cape::DSL#remote_rake_executable |
|
|
A
|
Cape::DSL#local_rake_executable |
|
|
A
|
Cape::RecipeDefinition#options |
|
|
A
|
Cape::Rake#remote_executable |
|
|
A
|
Cape::Rake#local_executable= |
|
|
A
|
Cape::Rake#local_executable |
|
|
A
|
Cape::Rake#each_task |
|
|
A
|
Cape::DSL#rake |
|
| Proper documentation present | ||
|---|---|---|
| – |
| Needs work | ||
|---|---|---|
| – |
| Undocumented | ||
|---|---|---|
| – |
Let's raise the visibility of documentation in Ruby!
This page is for njonsson/cape and is part of a project called "Inch Pages", showing documentation measurements provided by Inch.
Inch Pages also provides a badge: 
(not counting low priority objects)
Can I have my own badges?
What is the goal of this?
I really think that posting badges for documentation in READMEs will benefit you (because people can see that your project is well documented) and our community in general by improving the visibility of documentation.
Let's start a discussion, let's raise the visibility of documentation, let's talk.
Suggestions, feedback, critique: Hit me up on Twitter or via issue.
nch Pages