Unclear how to contribute to documentation about bigtuna

[michalbugno]

Hi, there is no doc repo, instead there is bigtuna.appelier.com where we try to write about usage. If you thing we should document parts of the code, let us know. We decided not to, as it is pretty standard rails app, but we can reconsider.

[dbalatero]

I think you'd be better served by moving the documentation to a README.markdown file in the Github repo, so any features added can be documented by the creator.

That said... I'd like to document the GitHub secure token a little clearer. For some reason, it wasn't clear to me up front that I should just generate a token myself. I thought GitHub had added a secure token feature that I should be looking for on the Admin interface.

[dbalatero]

(or if you want to keep a fancy doc website, open-source the full content of it in a separate repo)

[michalbugno]

This is actually a very good idea, we're going to create a public repo for the webpage itself.

[michalbugno]

We created a repo with site's source. It's a simple jekyll--driven static site.

Repo: https://github.com/appelier/bigtuna-webpage
Jekyll: https://github.com/mojombo/jekyll