Make the README into API docs

[gnarf]

I asked @kswedberg in IRC today to take a look at the readme here and help me add some prose/better documentation for these signatures. Currently it is pretty hard to actually learn about everything color can do since the language in the readme isn't very easy.

[raphamorim]

@gnarf can I proceed with this issue?
What do you think about create a api.jquerycolor.com using jquery-wp-content?

[gnarf]

I feel like this might be overkill... the API is pretty tiny, but we need
better documentation and examples... maybe a jsdoc generated gh-pages
branch?
On Jun 24, 2016 18:38, "Raphael Amorim" notifications@github.com wrote:

@gnarf https://github.com/gnarf can I proceed with this issue?
What do you think about create a api.jquerycolor.com using
jquery-wp-content https://github.com/jquery/jquery-wp-content?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#57 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAhh6wDK139jdUmvA4TQ_BQqol4TX2gyks5qPFxegaJpZM4AlYEk
.

[raphamorim]

For me okay,
Could you create a gh-page branch on repo? (I don't have permissions to do that hehe)

[leobalter]

@raphamorim you can use a /docs folder in the master branch to publish the api as a gh-pages. This is the same approach we're using for QUnit. It's good as it publishes the api docs in sync with the current master version.

[raphamorim]

Okay, I'll work on it.