This page shows an evaluation of the project's documentation.
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
|
StatusTag |
|
|
A
|
StatusTag::Presenter#decider |
|
|
A
|
StatusTag::Presenter#options |
|
|
A
|
StatusTag::Presenter#choice |
|
|
A
|
StatusTag::Presenter#aspect |
|
| Show 1 more ... | ||
| Proper documentation present | ||
|---|---|---|
|
B
|
StatusTag::Choice#initialize |
|
|
B
|
StatusTag.status_tag_signature_for |
|
|
B
|
StatusTag::Presenter.ordered_choices |
|
|
B
|
StatusTag::Presenter.css_class |
|
|
B
|
StatusTag::Presenter#object= |
|
| Show 1 more ... | ||
| Please take a look | ||
|---|---|---|
| – |
This page is for pboling/status_tag and is part of a project called "Inch CI", showing documentation measurements provided by Inch.
Inch CI also provides a badge: 
(not counting low priority objects)
Sure! To get the badge for the project you are looking at, just click the badge next to the project name.
To register another project with Inch CI, just enter your username/repo on the homepage or sign in with GitHub!
No problemo! Learn how ...
Of course! Learn how ...
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.
