Build a contribution guide

[arnab]

Since we'll need help from other members to prepare pages like the events/gallery etc.

I can think of the following ways folks would like to (or can) contribute:

• Github PR: contributor needs to be sufficiently savvy with setting up git/GH/Ruby/Jekyll. Markdown is the easy part.
• Fork and use Github's Markdown editor on github.com: Basically, fork the repo, then use Github.com on the forked personal repo to add (example) or edit (example) pages. Then the contributor can create PRs as the first step to have the changes merged into the main repo. We will need to include more detailed help for this kind of contribution, since the jekyll rake tasks to create pages/posts won't be available - and the user will need to add the YAML front matter manually.

@hrj - thoughts?

[hrj]

Well, I think most contributors will be contributing only once in a blue moon, and typically they wouldn't be aware of Git, etc. I expect most of them to just email us an article either in plain text or markdown, and we (the admins) can then add it to the website, either as a PR or, for minor edits, by directly pushing the changes.

For those rare and brave contributors that want to edit directly, we should probably go with option 2 (using Github's editor). They need not even create the PR. They can just point us to a URL and we can pull ourselves.

Option 1 is only suitable for those who are already familiar with Git and website development stacks. For these users, we need not write a guide, because they will be able to pick up by themselves.